Performing two-phase commit transactions

You can use the two-phase commit capability of a federated system to update data for one or more data sources in a single transaction.

Two-phase commit for federated transactions
A federated system can use two-phase commit for transactions that access one or more data sources. Two-phase commit uses the industry standard X/Open XA protocol to coordinate the processing of distributed unit of work transactions.
Enabling two-phase commit for federated transactions
To use federated two-phase commit for specific data sources, you must enable the associated federated servers. The enablement process involves preparing the federated server and modifying the data source server definition.
Data source requirements and configuration for federated two-phase commit transactions
Before enabling federated two-phase commit for a data source, you must ensure it is a supported data source.
Recovering from federated two-phase commit problems
A federated system can recover from problems during two-phase commit with automatic resynchronization or manual recovery of indoubt transactions.
Troubleshooting federated two-phase commit issues
Troubleshooting federated two-phase commit issues is often specific to the data source that is causing the issue.
Federated two-phase commit performance
Data sources that are configured for two-phase commit transactions incur a performance penalty when you compare them to data sources that are configured for one-phase commit transactions.

Parent topic: Managing transactions in a federated system