'ORA-00001: unique constraint violated' Signalled When Saving an ODI Object After Importing ODI 11g Work Repository
Last updated on FEBRUARY 08, 2017
Applies to:Oracle Data Integrator - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
After migrating into a new work repository. After the migration some of the mappings cannot be saved after any additional changes have been made to them, throwing error:
- Created new work repository.
- Exported using smart export from the old one.
- Imported into new one.
- The client crashed due to the java heap ran out during import once.
- After adjusting settings in config file it ran ok (seemingly).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms