EclipseLink: SQLIntegrityConstraintViolationException: ORA-00001
(Doc ID 2187141.1)
Last updated on AUGUST 27, 2020
Applies to:Oracle TopLink - Version 188.8.131.52.0 to 184.108.40.206.0 [Release Oracle11g to 12c]
Information in this document applies to any platform.
There is a problem with a transaction using EclipseLink 2.3.1.
The application begins a transaction that could be rolled back.
After that, a new transaction is started and the application tries to persist an object ‘Employee’, but an error is produced.
The error shows that It is trying to create an object that already exists in the database, and it is not of the type that the application wants to create:
As seen above, Eclipselink is trying to create an “Employee” object and because this object is already into the DB the exception is thrown.
EclipseLink 2.3.1 + TopLink 220.127.116.11.0
[ shipped with WLS 10.3.6 ]
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document