|
Problem IC96031
|
Status: Closed |
SYSTEM APPLICATIONS INVOLVED IN A LOCKING EVENT ONLY SHOW UP AS PARTIAL EVENTS. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
When a system application that makes use of the catalog scan
interface is involved in a locking event (deadlock, lock wait or
lock timeout), the locking event will only be processed as a
"partial event". This is due to an issue with the current
activity that is setup - the participant_no used for them is
zero rather than the correct value. This results in a mismatch
in participant numbers when evmon_format_ue_to_xml is
determining if an event is complete.
This means the customer won't be able to properly debug locking
events involving system applications. This includes
db2lused and db2reorg. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Anybody using the LOCKING event monitor. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 10.5 Fix Pack 3. Also, drop the *
* registered XML schema object associated with the tables *
* produced by EVMON_FORMAT_UE_TO_TABLES for the locking event *
* monitor by using the following command: DROP XSROBJECT *
* EVMON_LOCKING_SCHEMA_SQL10050. This schema object will be *
* reregistered the next time EVMON_FORMAT_UE_TO_TABLES is run *
* against the locking event monitor. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 10.5 Fix Pack 3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 17.09.2013
27.02.2014
27.02.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.3
|
 |
| 10.5.0.3
|
|
