My Oracle Support Banner

ORA-2049 reported on Distributed Txn affecting 2 Tables with a Foreign Key Relationship in a RAC environment (Doc ID 1379206.1)

Last updated on MARCH 11, 2019

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 11.1 to 12.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.


ORA-2049 can be observed when there are modifications to two or more tables in a distributed
transactions where :

- there is a foreign key relationship between the tables and under the circumstances of this particular issue :
  - there was an insert into tableA on node 1 ; table A has a pk
  - there was an insert into tableB on node 2 in the same txn ; tableB has a foreign key reference to the
    primary key in tableA
- a locking situation is observed where a branch may appear to be blocking waiting on event :
  'enq: TX - row lock contention'

One of the sessions may be blocked trying to lock an index block with an execution stack context as
follows :


kdiexi() - indicates index access and we are unable to perform the operation on the index ;
ksliwat() - indicates a waiting situation


Clusterwide global transactions are now being used.


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

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