home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC94589 Status: Closed

XA_COMMIT() RETURNED XAER_RMFAIL(-7) WITH PURESCALE ENVIRONMENT DURING XA
TRANSACTION RECOVERY, WHEN USING AFFINITIES.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
This problem can only happen when using affinities. 
 
When CICSAS process with an active connection to DB2 purescale 
member is killed abruptly after it does an xa_prepare and before 
it does an xa_commit also the entire TXSeries region (TM) is 
brought down forcibly. 
During region restart, CICSAS attempts to performs a recovery by 
doing a xa_open again and xa_recover and re-prepare the pending 
logical unit of works to do COMMIT. 
 
However, the DB2 commit(xa_commit) failed(XAER_RMFAIL) resulting 
in TXSeries process hang.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Purescale environment.                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 10.4 fixpack 4.                   * 
****************************************************************
Local Fix:
switch to WLB(Work Load Balancing) instead of affinities.
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 10.1 FixPack 4.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC95736 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.08.2013
09.06.2014
09.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList