DB2 - Problem description
Problem IC77796 | Status: Closed |
DB2 APPLICATION SNAPSHOTS INCORRECTLY REPORT THE STATEMENT AS STILL EXECUTING | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
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. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All * **************************************************************** * PROBLEM DESCRIPTION: * * See Problem Description above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 9.7 Fix Pack 5. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
First fixed in Version 9.7 Fix Pack 5. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 28.07.2011 08.12.2011 08.12.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.5 |