DB2 FOR LUW / DB2FORLUW / A10 - DB2

A lock wait situation may occur after successful collection of 
asynchronous statistics via JITS (just in time statistics). 
 
Asynchronous statistics collection will update the statistics 
cache as well as the catalog tables, for which an internal 
catalog cache is held in exclusive mode. 
The JITS deamon may not release this lock after a non successful 
return during commit of the catalog changes. 
By still holding the internal catalog cache in exclusive mode 
other agents will be blocked when they attempt to look up 
information from the database  catalog. 
 
 
Snapshots (application/lock snapshot)  will show the db2acd 
process in UOW Waiting but holding an internal catalog cache 
log: 
 
 Application name            = db2acd 
 Application status          = UOW Waiting 
 Object Type                 = Internal Catalog Cache Lock 
 
 
In the optstats log file one will see a warning like following: 
 
2014-08-11-14.51.21.240570+120 I2637247E537          LEVEL: 
Warning 
PID     : 5435                 TID : 140251444623104 PROC : 
db2acd 0 
INSTANCE: aaaaaa               NODE : 000            DB   : bbb 
APPID   : *LOCAL.db2glp.140811114452 
HOSTNAME: myhost 
FUNCTION: DB2 UDB, Automatic Table Maintenance, 
JitsDaemon::runstats, probe:70 
MESSAGE : SQL10007N  Message "99999" could not be retrieved. 
Reason code: "4". 
DATA #1 : String, 45 bytes 
AutoStats: Non zero code from Runstats commit 
DATA #2 : String, 10 bytes 
RTS Daemon

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 FixPack 5                               * 
****************************************************************

To Avoid the lock wait scenario customer can try the workaround 
by setting following registry variable 
 
db2set DB2_ATM_CMD_LINE_ARGS="-low-priority-update-systables"

First fixed in DB2 V10.1 FixPack 5

not known / see Local fix

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

05.09.2014
16.07.2015
16.07.2015