My Oracle Support Banner

After Data-Guard failover Tuxedo doesn't rollback a XA transaction (Doc ID 1150205.1)

Last updated on NOVEMBER 07, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 11.2.0.1 [Release 10.2 to 11.2]
Oracle Database Cloud Schema 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
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.

Symptoms


After Data-Guard failover Tuxedo doesn't rollback a XA transaction if  MAXTRANTIME is set to 0.

Callflow :
xa_start + DML + xa_end
--> Failover to secondary Node
xa_prepare fails with XAER_RMFAIL <-- expected
xa_open fails with ORA-12514 as service isn't availablei yet on failover side <-- expected
--> Tuxedo marks this Tx as Rollback only

At this stage Tuxedo doesn't issue a ROLLBACK as it will wait for 68 years [ due to
MAXTRANTIME = 0 ], until the rollback will be issued.

Changes

Dataguard failover

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.