Meaningless Drivel is fun!*
The moose likes JDBC and the fly likes Large Binary Objects Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of Android Security Essentials Live Lessons this week in the Android forum!
JavaRanch » Java Forums » Databases » JDBC
Bookmark "Large Binary Objects" Watch "Large Binary Objects" New topic

Large Binary Objects

Praveen Dharmavaram
Ranch Hand

Joined: Nov 05, 2002
Posts: 59
I was using the following code to call the stored procedure. one of the parameters of the stored procedures accepts BINARY data. The BINARY data could go upto 145290 Bytes. This was working fine in WAS 3.5.7 where i was using the JDBC 1.0 Connection pooling. But as i migrated to WAS 5.0.2 I have been forced to use JDBC 2.0 and port my application to J2EE 1.3. I can no longer pass the BINARY data. I tried registering the parameters as VARBINARY, LONGVARBINARY, BLOB and CLOB to acheive the desired result.
When i use VARBINARY or LONGVARBINARY, i get a CLI0102E Invalid Conversion.SQLSTATE=07006 .
When i use BLOB or CLOB, i get an CLI0613E Program Type out of range.SQLSTATE=S1003.
Can some one please help me out.
Joe Ess

Joined: Oct 29, 2001
Posts: 8839

Other relevant information regarding Praveen's problem can be found in this thread

"blabbing like a narcissistic fool with a superiority complex" ~ N.A.
[How To Ask Questions On JavaRanch]
Praveen Dharmavaram
Ranch Hand

Joined: Nov 05, 2002
Posts: 59
Thanks Joe..That was me who posted the same question earlier. As was in the post i did not get it resolved with the IBM support. I am curious to know if anyone else is facing the same problem.
It is sorta covered in the JavaRanch Style Guide.
subject: Large Binary Objects
Similar Threads
Blob and Clob in iBatis
BLOB data type
Awkward Memory Issues
type mapping ( image, longvarbinary)