Failed attempt to commit distributed transaction using heterogeneous commit
The database server can fail to commit a distributed transaction
while it is using the heterogeneous protocol for one or more of the
following reasons:
- Communication error
- Site failure
- Gateway failure
- Other unknown error
When such a failure occurs, the coordinator returns the
following message:
-441 Possible inconsistent data at the target DBMS name due to
an aborted commit.
After the database server sends this message, it rolls back all update sites that are participating in the transaction, with the possible exception of the work done at the site of the gateway participant. The gateway participant might have committed its updates if the failure occurred after the gateway participant processed the commit message. If the gateway participant committed the updates, you must manually roll back these updates.