My Oracle Support Banner

"Alter Table Enable Novalidate Foreign Key Constraint" Gets ORA-00054. (Doc ID 1271688.1)

Last updated on FEBRUARY 15, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
***Checked for relevance on 07-Dec-2016***

Symptoms

After migrating from Oracle 10.2 to Oracle 11.2, a problem occurs when attempting to re-enable foreign keys on a table that was loaded.
On a fact table we disable the constraints, then load the table, then enable the constraints with the NOVALIDATE option.
Now it gets an ORA-00054 because "ENABLE NOVALIDATE constraint" needs a lock on the referenced tables (but these are currently locked by other load processes).

Changes

After upgrade from 10g to 11g

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.