in reply to Oracle DBI CLOB Issue: fetch Column TRUNCATED

Can't answer part 1, but on part 2, I believe the following note would apply since you are using DBI version 1.34:

LOB Locator Methods The following driver-specific methods let you manipulate "LOB Locators +". LOB locators can be selected from tables directly, if the ora_auto +_lob attribute is false, or returned via PL/SQL procedure calls. (If using a DBI version earlier than 1.36 they must be called via the +func() method. Note that methods called via func() don't honour Raise +Error etc, and so it's important to check $dbh->err after each call. +It's recommended that you upgrade to DBI 1.38 or later.)

Scott

Note You may want to look into the really old version of DBD::Oracle (1.06 versus current version 1.17) as possibly part of your issue with part 1, the changelogs between 1.06 and 1.17 have references to the LOB stuff you are using.

Replies are listed 'Best First'.
Re^2: Oracle DBI CLOB Issue: fetch Column TRUNCATED
by DaytonaGreg (Initiate) on Apr 09, 2006 at 21:50 UTC
    Scott,

    Thanks. You may be right. I was just reviewing the CHANGE LOG (something I have never really done). I see the following for DBD::Oracle:

    =head1 Changes in DBD::Oracle 1.07 5th June 2001
    ....
    Fixed error in 'LOB value truncated' error thanks to Paul Walmsley.
    ....

    So they have apparently corrected some things dealing with LOB truncation. I did not realize how old this DBD::Oracle module apparently is. This may or may not be the solution but I suspect since I am doing some rather straight-forward calls, the versions I have probably cannot support it.
    I will review versions of DBD::Oracle and DBI and look to upgrade before banging my head against this anymore.

    THANKS!

      Instead of '$dbh->{LongReadLen} = 512 * 1024' you can use $dbh->LongReadLen(512 * 1024). This may work for older version