DB2 FOR LUW / DB2FORLUW / A50 - DB2

While XA applications are running on a 3 members pureScale and 
send kill -9 to one of member's db2sysc may cause xa_commit 
receiving XAER_RMFAIL unexpectedly. 
It should return XAER_RETRY instead of XAER_RMFAIL in this case. 
This is only XA return code problem and no side effect to any 
transaction. 
By the XA Standard it is Transaction Manager's responsibility to 
get the list of indoubt transaction and retry XA operations 
until they are successful to complete the transaction. TM able 
to commit the transaction, by issuing XA_OPEN + XA_COMMIT, 
repeated the steps a few times and eventually successfully able 
to commit the transaction.

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 UDB Version 10.5                                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 11.1 GA or later.                         * 
****************************************************************

DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows
 DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
 Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
 

keiner bekannt / siehe Local-Fix

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

25.10.2015
14.02.2017
14.02.2017