home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC94589 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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.
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in DB2 UDB Version 10.1 FixPack 4.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC95736 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
01.08.2013
09.06.2014
09.06.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.4 FixList