ORA-01483 when inserting two blobs and a date using the OracleManagedDataClientDriver
Description
Environment
Activity
Frédéric Delaporte August 1, 2017 at 4:42 PM
Testing without the workaround, the test still succeeds. But another test starts failing: BinaryBlobTypeFixture.ReadWriteZeroLen. So this code will likely stay in place.
Frédéric Delaporte July 31, 2017 at 4:09 PM
The ODP bug is said to be fixed and released since june 2015. Maybe this workaround should now be removed from NHibernate managed driver code.
cremor January 13, 2015 at 9:39 AM
This is actually a bug in the Oracle managed client itself, see here:
https://community.oracle.com/thread/3640248
https://support.oracle.com/epmos/faces/BugDisplay?id=20206306
The workaround implemented with the pull request only fixes the case of BLOBs. CLOBs still throw the same error.
They can be fixed with the same method - setting the OracleDbType to Clob - but I don't think it is a good idea to do this for all strings.
Oskar Berggren July 26, 2014 at 11:58 PM
PR merged in 264ca9238dd529aac2c395096ac6fe374723cb7b.
Alex Zaytsev June 20, 2014 at 5:56 AM
, could you please merge it before doing the release (If it will not be merged by then)?
Create a table with 3 columns, two blobs and one date.
Try to insert a record in it using the managed driver.
You will get a ORA-01483.
How to fix:
Set the "OracleDbType.Blob" on both parameters in the same way we do it with RefCursor or XmlType.