Re: Help with JDBC trace.
Date: Tue, 8 Sep 2009 18:03:11 +0200
JDBC is not my area, but is it not interesting that CharLength is one higher than InteralTypeMaxLength? I'd have thought the limit would be 32K (32768), but rather it seems to be limited to slightly less. Type 1 would probably be varchar2, which I think is what a bind of type 1 is.
But then again, the problem may be something completely different that someone more used to JDBC traces will be able to address.
On Tue, Sep 8, 2009 at 4:47 PM, Fred Tilly<ftilly_at_btinternet.com> wrote:
> 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_at_19616c7, statement=oracle.jdbc.driver.T4CCallableStatement_at_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