Identify and Eliminate Referential Constraints to Prevent ORA-02049 Errors
Last updated on JANUARY 05, 2017
Applies to:Oracle ATG Web Commerce - Version 2006.3 and later
Information in this document applies to any platform.
An error similar to this:
These can be caused by insufficient indices against all tables.
You need to discover all tables that have a referential constraint against them (ie. they have a foreign reference) and verify that they have sufficient indexing. Databases work by creating internal share locks when working with referential constraints when there is no index on the foreign key that references another tables primary key. If there is no such index on these tables, then operations such as insert, delete or update on the parent's primary key will cause frequent waits on the systems internally acquired share locks on those tables. Although the specific index may not be required, it is good practice to ensure all these indices are created.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms