What version of Oracle and what version of the driver are you using. I had a similar problem with Oracel 9i and the problem was fixed by using the 10g driver which is backwards compatible. So you might want to try the latest driver for 11g
I'm not sure what is the version (I will find out about that tomorrow during business hours... I'm using a node from our QA department)...
The problem is related to the Insert with Select.. and the Blob is on the Select clause... It looks like Oracle don't support binding blob values on a Select? (which is kind of weird though).
For now (I mean... for CR2).. I'm ignoring duplicate keys on the storeMessage method.. I will look for a way to change it before GA.
Thanks a lot...
Ps: I will update the thread when I have discovered the versions...
Just for the record.. I'm really disappointed with the Oracle driver.
This is a very basic feature IMO, I have found lots of references and complains on the internet about this and they don't seem to care about it.
I will just avoid binding BLOBS on Select clauses on Oracle, as I don't want to deal with support cases on this later. The consequence will be an "if Oracle" on the code.
I would be able to simply use insert and ignore for duplicate keys.. but Postgres would invalidate the transaction on those cases, throwing this message:
"25P02, current transaction is aborted, commands ignored"