#11 dbms_output

closed
nobody
None
5
2014-08-26
2008-05-27
Anonymous
No

Enbbling Dbms_output and executing any sql statemnet (also "select 1 from dual") raises an "ORA-02005: implicit (-1) length not valid for this bind or define datatype"

My settings in SQL Toools / Session / Dbms_Output size is 1000000 (unlimited is not checked)

In SQL Tools / PlusPlus Settings / unlimited DBMS_OUTPUT size is not checked

Using SQLTools (not ++) all works fine

Server tested: Oracle 10.2.0.1
on Oracle 9.2.0.4 all works fine

Discussion

  • randolf_geist
    randolf_geist
    2008-05-29

    Logged In: YES
    user_id=2028028
    Originator: NO

    Unfortunately can't reproduce in environments available to me.

    Could you please provide the Oracle OCI client version that you are using?

    Best way to do this is to use a tool like "Process Explorer" from Sysinternals and check the version of the OCI.DLL that is loaded by SQLTools.exe.

    Please check for all three cases: SQLTools++ -> 10.2.0.1, SQLTools++->9.2.0.4, SQLTools -> 10.2.0.1

    Reason: There is a known Oracle client bug 3471389 mentioned on Oracle Metalink that causes this error message.

    Thanks in advance.

    Regards,
    Randolf

     
  • Logged In: NO

    This are the results:
    sqltools++ -> ora 10.2.0.1 = OCI.DLL 10.01.0000.0002 (30/05/2006 16:36)
    sqltools++ -> ora 9.2.0.4 = OCI.DLL 10.01.0000.0002 (30/05/2006 16:36)
    sqltools -> ora 10.2.0.1 = OCI.DLL 10.01.0000.0002 (30/05/2006 16:36)

    Cheers Tommaso

     
  • randolf_geist
    randolf_geist
    2008-07-04

    Logged In: YES
    user_id=2028028
    Originator: NO

    According to your OCI.DLL you seem to use a quite outdated Oracle Client Version 10.1.0.2... Could you install a different client release, like the current 11.1, and then re-try?

    The simplest way to do this is using the Instant Client which does not require an installation, but you've to be careful regarding your TNSNAMES.ORA in that case (requires may be to set the TNS_ADMIM environment variable).

    SQLTools++ attempts to use the maximum 10g DBMS_OUTPUT linesize of 32767 if 10g server and client is used, that is probably the reason why you get the error only when using SQLTools++ connecting to a 10g database with your 10g client.

    SQLTools uses only a linesize of 255 which was the limit before 10g.

    I'm quite confident that using a more recent client should fix the issue.

    Regards,
    Randolf

     
  • randolf_geist
    randolf_geist
    2008-07-13

    • status: open --> closed