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 IT08825 Status: Geschlossen

TRANSACTION MANGER REMAINS WAITING FOR XA_ROLLBACK AFTER ABEND ON Z/OS

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
This situation might happen when distributed transaction take 
place DB2 z/OS server(resource manager - RM) reports ABEND. 
DB2Connect server is configured in the connection path with 
connection concentrator enabled to handle TM using 
mufti-transport model like Tuxedo. 
DB2 z/OS ABEND causes connection reroute between DB2Connect 
Server and DB2 Z/OS. Transaction is marked for rollback only. TM 
sends xa_end and xa_rollback to rollback the transaction. XA_END 
receives XA_RBOTHER and XA_ROLLBACK request hang on DB2Connect 
Server. 
 
For example when Tuxedo Transaction Manager is configured on DB2 
Connect Server and application abnormal ends on z/OS. 
In the Tuxedo logs the information regarding ABEND, xa_end = 104 
and hang on xa_rollback can be found. 
 
Apply the APAR on client.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2Connect Server                                            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to 10.5.7.                                           * 
****************************************************************
Local-Fix:
Lösung
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
11.05.2015
20.01.2016
20.01.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList