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

Last updated on FEBRUARY 08, 2017

Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 11.2.0.1 - Release: 10.2 to 11.2
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

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms