|
Problem IC66473
|
Status: Closed |
MONITOR NOT CAPTURING UNIT OF WORK RECORD WHEN COMMIT IS CHAINED FROM JCC |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* 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.8.3 or higher if the *
* customer is *
* encountering problems with missing unit of work records when *
* using the unit of work event monitor. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
|
| Solution |
Fix has been delivered to 9.8.3 (DB2 9.8 Fixpack 3). 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 |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 18.02.2010
21.12.2010
21.12.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.3,
9.8.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.8.0.3
|
 |
