DB2 FOR LUW / DB2FORLUW / 970 - DB2

When WLM UOW total time threshold is defined, it is expected 
that current transaction will be terminated  as soon as 
threshold time limit is reached. Agent working for the 
application is responsible for checking if any of WLM threshold 
limits are violated by the application. 
 
However if coordinator agent for the application is waiting for 
a new request to arrive from the fron-tend client, it is not 
checking if UOW total time threshold limit is reached. 
Therefore, in some cases, when we have "lazy client application" 
it may be possible for a single transaction to last longer then 
WLM limit defined. 
 
To reproduce: 
 
1. Create threshold: 
 
CREATE THRESHOLD UOW1min FOR DATABASE ACTIVITIES 
   ENFORCEMENT DATABASE 
   WHEN UOWTOTALTIME > 1 MINUTE STOP EXECUTION; 
 
ALTER THRESHOLD UOW1MIN ENABLE ; 
 
2. Perform some activity and leave transaction open: 
 
$ db2 connect to sample 
$ db2 +c "create table t1 (c1 integer)" 
$ db2 +c "insert into t1 values (1)" 
 
$ sleep 180 
 
Leave this tx open - do not run any other db2 commands from this 
window. 
 
3. From a different window, check if transaction is still open, 
after 3 minutes: 
 
$ db2 "select count(*) from t1 with UR" 
 
You should see the data you inserted, rollback hasn't been done.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All WLM users                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2 WLM may not terminate transaction on UOW total time      * 
* threshold violation if application is waiting for response   * 
* from the client.                                             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to the Fix pack containing the Fix once the   * 
* FIX is available.                                            * 
****************************************************************

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
 

Problem to be addressed: 9.7 Fixpack 6 and later.

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IC84401 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

24.08.2011
05.06.2012
05.06.2012

9.7.FP6