ORA-00001: Unique Constraint Error On Auxiliary Table Due To Asset_Version Mismatch Occurs When Editing CA Asset
(Doc ID 2224615.1)
Last updated on FEBRUARY 05, 2019
Applies to:
Oracle Commerce Merchandising - Version 11.0 and laterInformation in this document applies to any platform.
Symptoms
When attempting to edit an asset on the CA server, a failure occurs and the logs report a ORA-00001: unique constraint error. A ConcurrentCheckoutException also tends to appear. For example:
This error is seen from an auxiliary or multi table for the asset being checked out; in this example dcs_category_sites. A check of this table shows that it has an extra entry that refers to an asset_version not present for the same asset in the primary table (dcs_category in this example). This would be the new asset_version that it attempted to create previously; typically one larger than the current latest asset version in the primary table.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |