Re: BLOBs over xxx bytes truncated to null?!

On Mon, 24 Sep 2001 12:00:19 -0400, "Luis Sanchez" <luiss_at_attglobal.net> wrote:

>I'm running some code (JDBC actually) which stores some data in a BLOB. This
>code has worked well for two years against DB2 databases on different
>flavors of Windows, AIX, and Linux.
>
>Attempts to run it against an Oracle Database have proved frustrating. When
>I commit a transaction, if the size of the data going into a BLOB in the
>database is greater than "about" 1792 bytes, the value is committed as a
>NULL. As long as the size of the data is less than about 1792 it will
>correctly commit the data.
>
>Any hint? tips? I'm not an Oracle DBA and based on all the configuration
>work I had to do to get my code to run as far as it did, I'm suspecting I've
>not set something up correctly.
>
>

I had similar problems with CLOBs, but that was because I was using setString() to write... which was wrong. The Oracle client driver requires you to use BLOB and CLOB objects when writing... I ended up using PreparedStatement.setCharacterStream().

hth Received on Mon Sep 24 2001 - 12:32:48 CDT