Help with JDBC trace.

From: Fred Tilly <ftilly@xxxxxxxxxxxxxx>
To: oracle-l@xxxxxxxxxxxxx
Date: Tue, 8 Sep 2009 14:47:05 +0000 (GMT)

All,

Looking through a JDBC trace file I see the following SEVERE message, does 
anyone know what it means.

08-Sep-2009 14:47:38 oracle.jdbc.driver.OracleCallableStatement 
registerOutParameter
INFO: OracleCallableStatement.registerOutParameter(paramIndex=2, sqlType=12, 
scale=0, maxLength=-1)
08-Sep-2009 14:47:38 oracle.jdbc.driver.T4CCallableStatement allocateAccessor
SEVERE: oracle.jdbc.driver.T4CCallableStatement.allocateAccessors:return: 
oracle.jdbc.driver.T4CVarcharAccessor@19616c7, 
statement=oracle.jdbc.driver.T4CCallableStatement@b166b5, outBind=true, 
internalType=1, internalTypeMaxLength=32512, isStream=false, formOfUse=1, 
internalOtype=null, externalType=12, internalTypeName=null, columnName=null, 
describeType=0, describeMaxLength=0, nullable=false, precision=0, scale=0, 
flags=0, contflag=0, total_elems=0, describeOtype=null, describeTypeName=null, 
rowSpaceByte=null, rowSpaceChar=null, rowSpaceIndicator=null, columnIndex=0, 
lengthIndex=0, indicatorIndex=0, byteLength=0, charLength=32513

Thanks

Fred

--
http://www.freelists.org/webpage/oracle-l

Follow-Ups:

Re: Help with JDBC trace.
From: Mathias Magnusson

Help with JDBC trace.

Other related posts: