DB2 FOR LUW / DB2FORLUW / A10 - DB2

Db2 increments the lock timeout value without the 
actual timeout occurs, There will be no SQL0911N error in the 
db2diag.log but querying db2 "select lock_timeouts from 
sysibmadm.snapdb" will show different results. 
 
1- First, create the SAMPLE database 
db2sampl 
 
2-Create a dummy table 
db2 connect to sample 
db2 "create table test (col1 char(1))" 
 
3-Change and verify your config. 
db2 "update db cfg using MON_LOCKWAIT HISTORY immediate" 
db2 "update db cfg for sample using LOCKTIMEOUT 60" 
 
db2 "get db cfg" 
 
 Lock timeout (sec)                        (LOCKTIMEOUT) = 60 
 Lock wait events                         (MON_LOCKWAIT) = 
HISTORY 
 Lock wait event threshold               (MON_LW_THRESH) = 
5000000 
 
 
4-Create the event monitor and start it. 
db2 "create event monitor mylockmon for locking write to 
unformatted event table autostart" 
db2 set event monitor mylockmon state 1 
 
5-Check the current value for lock_timeouts 
db2 "select lock_timeouts from sysibmadm.snapdb" 
 
 
6-SESSION A, create the lock situation 
db2 +c lock table test in exclusive mode 
 
 
7-SESSION B, create the lockwait situation 
db2 connect to sample 
db2 "select count(*) from test" 
 
 
8-Wait more then MON_LW_THRESH value (+5 sec) 
 
9-SESSION A, commit 
db2 commit 
 
10-Check the current value for lock_timeouts. The number should 
be increased by 1. 
db2 "select lock_timeouts from sysibmadm.snapdb"

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See problem description                                      * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to v10.1 fixpack 5                                   * 
****************************************************************

Use MON_GET_WORKLOAD routine

First fixed in v10.1 fixpack 5

not known / see Local fix

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

03.04.2014
30.11.2015
30.11.2015