DB2 FOR LUW / DB2FORLUW / A10 - DB2

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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Anybody using the LOCKING event monitor.                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.1 Fix Pack 4.  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_SQL10010.   This schema object will be  * 
* reregistered the next time EVMON_FORMAT_UE_TO_TABLES is run  * 
* against the locking event monitor.                           * 
****************************************************************

DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

Problem was first fixed in Version 10.1 Fix Pack 4

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

17.09.2013
02.06.2014
02.06.2014