SQLIntegrityConstraintViolationException During Full Deployment Names Custom Table Constraint
Last updated on JANUARY 17, 2017
Applies to:Oracle Commerce Platform - Version 10.0 and later
Information in this document applies to any platform.
There are different row counts in corresponding tables when comparing CatA vs CatB Production schemas.
Logging from the BCC server shows that referential integrity errors interruped a cleanup of data on a target schema. The cleanup of tables is not apart of a deployment transaction, so the SQLException leaves the schema with some tables purged and other tables still holding data due to the aborted operation.
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