home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC98073 Status: Closed

DEADLOCK MAY OCCUR SURROUNDING ANONYMOUS BLOCKS PACKAGES WHEN DB2ABC (APM
CACHE CLEANUP) AND DDL STATEMENT RUN CONCURRENTLY.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
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.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to versino 10.1 Fixpack 4                            * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in  version 10.1 fix pack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.12.2013
27.06.2014
27.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList