-
1. Re: oracle can not persist BLOB in JMS_MESSAGES table
genman Nov 12, 2004 10:04 PM (in response to schambers)
Oracle seems to think that 4k is enough for you pure 100% Java people. You can either use MySQL or Postgres, or pay $$$ for a third-party driver. -
2. Re: oracle can not persist BLOB in JMS_MESSAGES table
ckmod Dec 3, 2004 10:29 AM (in response to schambers)I am experiencing the same problem with oracle 8.0.6 and jdbc driver version 9.0.1.4: I cannot store blobs larger than 4KB...:-(
-
3. Re: oracle can not persist BLOB in JMS_MESSAGES table
m0nstermind Dec 6, 2004 7:44 AM (in response to schambers)This is because Oracle JDBC driver is not JDBC conformant. Or they want to teach us all how to live. They believe, that using statement.setInputStream(), like jdbc2.PersistenceManager does, is not efficient enough to use, so they limited it to 4kb (actually this is because they passing BLOB as a RAW datatype, because for smaller lengths it is more efficient to include it in row data, which is limited since beginning of time in Oracle to 4k). For larger lengths they force us to use their non standard and crappy oracle.sql.BLOB extension.
So i just written my own patched version of jdbc2.PersistenceManager to use this Oracle's BLOBs extension, which is available here:
http://core.swdfactory.com/~oleg/jbossmq-orapm.zip
Please keep in mind - it works only with oracle database using Oracle JDBC drivers, developed by Oracle.
You can use this freely, but on your own risk. 8-) -
4. Re: oracle can not persist BLOB in JMS_MESSAGES table
luc.texier Dec 6, 2004 7:55 AM (in response to schambers)You should switch to OCI, this is the only way as far as I know.
The other option, recommend by the Hibernate community is to drop Oracle drivers altogether and use those from
DataDirect
http://www.datadirect.com/products/jdbc/matrix/jdbcpublic.htm
or InetSoftware
http://www.inetsoftware.de/English/produkte/JDBC_Overview/oracle.htm -
5. Re: oracle can not persist BLOB in JMS_MESSAGES table
mgruener Mar 18, 2005 3:23 PM (in response to schambers)I had a similar problem to this and it was fixed by upgrading ojdbc14.jar to version 10.1.0.3.0. I did not have to switch to oci. Thin now works for me.