DB2 - Problem description
Problem IC96007 | Status: Closed |
SYSTEM APPLICATIONS INVOLVED IN A LOCKING EVENT ONLY SHOW UP AS PARTIAL EVENTS. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - 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 9.7 Fix Pack 9. 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_SQL09070. 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 9.7 Fix Pack 9 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 9.7 Fix Pack 9 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC96030 IC96031 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 17.09.2013 16.12.2013 16.12.2013 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP9 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.9 | |
9.7.0.9 |