DB2 FOR LUW / DB2FORLUW / A50 - DB2

Locks acquired for the system catalog during compilation may not 
get released after compilation completes due to nested 
compilation. For example, driving re-validation upon an invalid 
object may trigger this symptom. In most cases, this would not 
cause any concern as the locks would get released at the end of 
the transaction. However, some side effects include longer lock 
waits and anonymous block deadlock. 
 
EDUID   : 3343                 EDUNAME: db2dlock (DBNAME) 
FUNCTION: DB2 UDB, base sys utilities, 
sqleCheckForceSuspendedConn, probe:280 
DATA #1 : String, 170 bytes 
Anonymous Block deadlock detected! 
Waiting application with appHandle 0-XXX will be rolled back. 
Suspended application with appHandle 0-XXX has deadlock state 
0x00000010.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V10.5 Fix Pack 7                                  * 
****************************************************************

not known / see Local fix

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

03.06.2015
28.01.2016
28.01.2016