Hi there,
I have been struggling with this for some hours now. I am not 100% sure, but
it appears that Oracle databases/jdbc drivers have a bug with relation to
Blobs - or that Blobs have a serious size limitation in an Oracle database.
I have seen hints to this while searching the www, but I can't be sure. I am
just certain I am doing as prescribed by PreparedStatement...
For example if a set a binary stream like this (as I think one is supposed
to do):
stmt.setBinaryStream( 1, is, length );
then it only works if the length is quite small - if it's "big" then it
won't work. Is there a bug in Oracle, or am I missing some vital point?
(Maybe blobs can only be up to 4k or so - I don't know).
Thanks for any pointers,
Peter
Ryan Stewart - 04 Mar 2004 23:06 GMT
> Hi there,
>
[quoted text clipped - 15 lines]
> Thanks for any pointers,
> Peter
I've worked with someone who hit this same problem. I'm sorry I can't give
you a lot of detail, but I believe it was a bug in the Oracle JDBC drivers
that incorrectly limited the size of BLOBs. I *can* tell you that it's
possible to get around the, but again, I don't know specifics. Just keep
looking because it can be done.
Marek Lange - 05 Mar 2004 15:33 GMT
>>(Maybe blobs can only be up to 4k or so - I don't know).
> I've worked with someone who hit this same problem. I'm sorry I can't give
> you a lot of detail, but I believe it was a bug in the Oracle JDBC drivers
> that incorrectly limited the size of BLOBs. I *can* tell you that it's
> possible to get around the, but again, I don't know specifics. Just keep
> looking because it can be done.
I think you can use "LONG RAW" as datatype for a workaround.
-marek