ORA-24798 WHEN XA RESUMES JOIN AN EXISTING TRANSACTION BRANCH
(Doc ID 1106793.1)
Last updated on APRIL 09, 2020
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 to 22.214.171.124 [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.
Add ***Checked for relevance on 09-Sept-2013***
The following note just applies to releases 126.96.36.199 onwards.
The following issue only appears on RAC installations with at least 2 nodes.
According to documentation your GLOBAL_TXN_PROCESSES is set to a value higher than 0 (1 is default) on all the instances of the RAC and your XA application does connect to database through a service which has not been defined as a DTP service.
The service that is being used by XA application is not a singleton service, so it does load balancing on connections.
Your XA application has created a transaction branch connected to database and then detached this branch. When a different Resource Manager or XA process tries to attach this transaction branch, it may fail with error:
ORA-24798: cannot resume the distributed transaction branch on another instance
There have not been errors on detaching the transaction branch.
The error will appear if the resource manager trying to resume/join the branched transaction is connected to a different instance as the resource manager that created the transaction.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!