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

MONITOR NOT CAPTURING UNIT OF WORK RECORD WHEN COMMIT IS CHAINED FROM JCC

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
The unit of work event monitor in DB2 does not properly record a 
unit of work record when executing a commit that is chained at 
the DRDA level. This behaviour was observed when executing 
queries using a JCC client. Note that the metrics collected for 
the aforementioned unit of work do not get lost, rather they are 
amalgamated into the record generated at the next unchained unit 
of work boundary.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Any users of DB2 LUW utilizing the unit of work event        * 
* monitor may be affected.                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* The unit of work event monitor in DB2 does not properly      * 
* record a unit of work record when executing a unit of work   * 
* boundary (commit or rollback) that is chained at  the DRDA   * 
* level. This behaviour was observed when executing queries    * 
* using a JCC client. Note that the metrics collected for the  * 
* aforementioned unit of work do not get lost, rather they are * 
* amalgamated into the record generated at the next unchained  * 
* unit of work boundary.                                       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Recommendation is to upgrade to 9.7.2 if the customer is     * 
* encountering problems with missing unit of work records when * 
* using the unit of work event monitor.                        * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
Fix has been delivered to 9.7.2 (DB2 9.7 Fixpack 2). With this 
fix, the unit of work event monitor in DB2 will now properly 
record a unit of work record at all unit of work boundaries, 
including those cases where the commit or rollback request was 
chained at the DRDA level.
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC66432 IC66473 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
17.02.2010
13.05.2010
13.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.2,
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList