[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-4635) Oracle ORA-24816 inserting and updating data for entities containg LOB attributes
[
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4635?page=c...
]
Jakub Hlavaty commented on HHH-4635:
------------------------------------
We also had this problem (hibernate 3.3.0, ojdbc5 11.1.0.7.0).
Our table had 2 clob columns and one varchar2 that caused the mentioned error.
We needed to stuff more data in that column anyway so we changed the varchar2 column type
to clob and that solved the issue for us.
It might not be the best sollution for everyone, but since we needed the change anyway, it
killed the proverbial 2 birds with one stone for us.
Oracle ORA-24816 inserting and updating data for entities containg
LOB attributes
---------------------------------------------------------------------------------
Key: HHH-4635
URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-4635
Project: Hibernate Core
Issue Type: Bug
Components: core
Affects Versions: 3.3.1
Reporter: Clay Atkins
Priority: Critical
Inserting or updating an entity with LOB results in the following error from oracle:
{noformat}
Caused by: java.sql.SQLException: ORA-24816: Expanded non LONG bind data supplied after
actual LONG or LOB column
{noformat}
Fairly confident that the ordering of the LOB attributes is not putting them at the end
of the insert or the update. Oracle requires all LOB columns to be the last in the
statement.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira