DB2 FOR LUW / DB2FORLUW / 970 - DB2

When the statement monitor switch is on and the statement gets 
an error during the execution - application snapshot incorrectly 
reports the statement as executing (ie statement stop timestamp 
is still blank). 
 
The statement execution may be stopped due to lock timeout or by 
a WLM threshold due to a threshold violation for example. 
 
The issue can be reproduced with following test case: 
 
 
1. Set locktimeout db config parameter to just one second. 
2. Run the query in the loop, with table locked and let it 
timeout on the lock repeatedly. 
3. Issue application snapshot from another window and look at 
the statement stop time.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fix Pack 5.                       * 
****************************************************************

DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

First fixed in Version 9.7 Fix Pack 5.

keiner bekannt / siehe Local-Fix

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

28.07.2011
08.12.2011
08.12.2011

9.7.FP5