Oracle ORA-24816 inserting and updating data for entities containg LOB attributes

Description

Inserting or updating an entity with LOB results in the following error from oracle:

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.

Environment

None

Activity

Show:
Brett Meyer
October 23, 2013, 2:26 AM

, I'm not sure what you mean. See https://github.com/hibernate/hibernate-orm/commits/4.2/hibernate-core/src/main/java/org/hibernate/persister/entity/AbstractEntityPersister.java. The commit is there. 4.1.8 and 4.3.0.Beta1 were the first releases to get the fix – all others following still have it...

Olivier Sambourg
December 29, 2015, 10:29 AM

It seems that Envers is not taking the fix into account: inserts in audit table are still using alphabetical order, thus triggerring the same ORA-24816 error.

Benoit Dupont
March 24, 2016, 10:18 AM

I updated the test case with the hibernate version to 4.3.10.Final (with Oracle db 11.2.0.4.0), and it does not solve the issue.

Can you reopen the issue please ? Or should I create a new one ?

Benoit Dupont
August 19, 2016, 7:43 AM

I forgot the annotation @Lob on the field, works fine now !

Markus
August 24, 2016, 5:09 AM

This does not work with dynamic @Filters because their parameters will always be bound last.

Fixed

Assignee

Brett Meyer

Reporter

ClayC

Fix versions

Labels

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Components

Affects versions

Priority

Critical
Configure