Restricting XA transaction in RAC to one node
Hi Experts,
the OGG in production server was having frequent abends due to missing records and failure for subsequent updates/deletes for past few months…and they were forced to resync every fortnight.
After checking the redo logs understand that the record was present but skipped by extract as it was a XA transaction (global transaction) spanned across one or more nodes in their RAC system which the current version Oracle GoldenGate do not support. They had tried to configure their services so that to direct the service to run only on one node but still failed with same issue.
My client is now in the process of configure their environment so to avoid transaction getting branched out and now going to adopt the following measures.
a. XA transactions must be submitted against a singleton database service (a database service configured to only run on one node at a time)
b. The singleton service must have Distributed Transaction Processing (DTP) enabled
c. The ClusterWideGlobal_Transactions database parameter must be set to FALSE
Please validate this solution and also correct if this not fix the problem also steps to avoid XA’s getting branched out to more than one node in their environment.
Thanks & Regards,
Antony