DB2 CONNECT / DB2CONNCT / A10 - DB2

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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* The APAR can only be hit if DB2 zOS don't allow to reuse the * 
* resources at the transaction transaction.                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 Fix Pack 3 or newer fix pack             * 
****************************************************************

Problem First Fixed in DB2 Version 10.1 Fix Pack 3

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

05.07.2013
03.10.2013
03.10.2013