My Oracle Support Banner

Setting the Commit Outcome to False and Failover Type to None in an XA Transaction. (Doc ID 2970953.1)

Last updated on AUGUST 30, 2023

Applies to:

JDBC - Version 19.3 and later
Information in this document applies to any platform.

Goal

1) What practical impact will be had by setting the commit outcome to false and failover type to none? This disables Transaction Guard and Application Continuity. But what does that mean for a production system on RAC? 

2) According to this document, "Using JDBC XA driver with Application Continuity is not supported with XA". Also, "XA transactions are not supported by Transaction Guard so setting COMMIT_OUTCOME=FALSE will disable Transaction Guard."

/*
From 12.2 onwards Transaction Guard will support below way:

Transaction Guard with XA Transactions

Starting with Oracle Database 12.2 Release, Transaction Guard supports XA transactions to determine the outcome of one-phase transactions. Transaction Guard supports local transactions and XA transactions that use TMONEPHASE during the commit operation. When the application issues an XA transaction that uses TMTWOPHASE, the Transaction Guard disables itself for that transaction and automatically re-enables it to prepare itself for the next transaction. This allows Transaction Guard to support the following XA transactions:
  Local transactions that use auto-commit

  Local transactions that use an explicit commit

  XA transactions that commit with TMONEPHASE flag

*/

If using RDBMS 19.17, is the second part of the above update applicable (XA Transaction is supported in a limited way)?
 

Solution

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
Goal
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.