DB2 FOR LUW / DB2FORLUW / A50 - DB2

When an application is compiling SQL and enters a locking event 
such as a lock wait or lock timeout and that event is captured 
by a locking event monitor, the resultant PARTICIPANT_ACTIVITY 
record can contain invalid values for the statement operation, 
statement first use time and statement last use time. 
 
For example, consider this snippet of output from db2evmonfmt: 
 
Current Activities of Participant No 1 
---------------------------------------- 
Activity ID : 0 
Uow ID : 1459 
Package Name : SYSSH200 
Package Schema : NULLID 
Package Version : 
Package Token : SYSLVL01 
Package Sectno : 4 
Reopt value : none 
Incremental Bind : no 
Eff isolation : RR 
Eff degree : 0 
Eff locktimeout : -2 
Stmt first use : 1969-12-31-19.00.00.000000 
Stmt last use : 1969-12-31-19.00.00.000000 
Stmt unicode : no 
Stmt query ID : 0 
Stmt nesting level : 0 
Stmt invocation ID : 0 
Stmt source ID : 0 
Stmt pkgcache ID : 0 
Stmt type : Dynamic 
Stmt operation : DDL, Set Constraints 
Stmt text : SELECT c1 from t1 
 
 
In this particular case: 
- the Activity ID is correctly zero because the activity hasn't 
started yet (the SQL is compiling) 
- the Stmt first use and Stmt last use timestamps are zeros, 
which get converted into 1969-12-31-19.00.00.000000 
- the Stmt operation is "DDL, Set Constraints" rather than 
"Statement not prepared"

**************************************************************** 
* 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 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.                           * 
****************************************************************

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
 

Problem was first fixed in Version 10.5 Fix Pack 3

keiner bekannt / siehe Local-Fix

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

19.07.2013
27.02.2014
27.02.2014