My Oracle Support Banner

ORA-14900 And ORA-1 (SYS.LTXID_TRANS$PK) Using Transaction Guard Application Continuity With XA Transactions. (Doc ID 2877376.1)

Last updated on JULY 20, 2024

Applies to:

Oracle Database - Enterprise Edition - Version 19.1.0.0.0 and later
Oracle SOA Suite - Version 12.2.1.4.0 to 12.2.1.4.0 [Release 12c]
Information in this document applies to any platform.

Symptoms

Seeing below errors in db alert log whenever dealing with distributed XA transactions for a RAC database configured with Transaction Guard (TG) Application Continuity (AC) services:

 

2022-01-25T16:13:25.723863+08:00
Error 14900 trapped in 2PC on transaction 10.30.11690859. Cleaning up.
Error stack returned to user:
ORA-14900: The logical transaction ID is no longer valid.

2022-01-25T16:13:30.433778+08:00
Auto-tuning: Starting background process GTX4
Starting background process GTX4
2022-01-25T16:13:30.510824+08:00
GTX4 started with pid=300, OS id=23134568
2022-01-25T16:13:30.900524+08:00
Error 14900 trapped in 2PC on transaction 65.0.2825836. Cleaning up.

Usually the application side session will experience following errors as well:

ORA-02054: transaction 2.7.11246 in-doubt
ORA-00604: error occurred at recursive SQL level 1
ORA-00001: unique constraint (SYS.LTXID_TRANS$PK) violated

 



Changes

 Implemented RAC TG Application Continuity while having Oracle XA transactions in place. For example, when using Weblogic with XA enabled data-source.

 

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.