DB2 - Problem description
Problem IC95371 | Status: Closed |
XAER_NOTA RETURNED BY DB2 CONNECT SERVER WHEN TM TRIES TO PREPAR E/COMMIT/ROLLBACK A TRANSACTION IN DISTRIBUTED ENVIRONMENT. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
Under certain conditions, an XAER_NOTA error could be raised if we have an XA transaction manager that uses dual/multiple transport model (For example:TM like TUXEDO, MQ) and a DB2 Connect using the concentrator feature being used as a gateway to a DB2 to zOS server. At the start of a new transaction, DB2 XA concentrator associates a worker agent with a particular XA transaction( single XID). All the work associated with the transaction or XID is performed by the same agent. At the transaction boundary (xa_prepare(read only), xa_commit/xa_rollback), the agent is returned back to the pool. In this APAR situation, agent is not returned to the pool at the transaction boundary. Later when TM used the same connection to commit the transaction by sending xa_prepare (or xa_commit (optimized call) or xa_rollback ), DB2 Connect server used the wrong agent, instead of attaching to agent associated the XID, same agent was used to server the another XID, to process XA request. The incorrect processing resulted XAER_NOTA. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 10.5 Fix Pack 1 or newer fix pack * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
Problem First Fixed in DB2 Version 10.5 Fix Pack 1 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 27.08.2013 03.10.2013 03.10.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |