DB2 FOR LUW / DB2FORLUW / 970 - DB2

Deadlock cycle can happens when: 
One agent performs DDL on an object which the ANONYMOUS BLOCK 
depends on. 
This results in the agent getting a lock on  a SYSPLANDEP row 
and then getting the package lock while 
invalidating the package. 
 
The 2nd agent performs Cache space management, while ejecting 
the ANONYMOUS block package, 
It first acquires the package lock exclusively then attempt to 
remove the row in SYSPLAN DEP. 
 
In a timing window it is clear how the deadlock cycle can be 
completed.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fixpack 9                         * 
****************************************************************

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
 

First Fixed in V9.7 Fixpack 9

not known / see Local fix

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

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

10.10.2013
16.12.2013
16.12.2013

9.7.FP9