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 IC91307 Status: Closed

TRANSACTIONS THAT PERFORM IMPLICIT REBINDS CAN CAUSE LOCK WAITS TO OTHER
CONNECTIONS DUE TO CATALOG CACHE AND CATALOG LOCKS

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Transactions in which an implicit rebind occurs can hold on 
certain catalog cache and catalog locks used to retrieve catalog 
information necessary for the compilation of the static SQL in 
the implicit rebind.   Rather than release these shared locks 
when the compilation has completed, the locks are held after the 
rebind has completed and will not be released until the 
transaction commits.   If another connection is attempting 
certain operations (such as detach processing) that requires any 
of these locks be held exclusively, that connection will wait 
(unnecessarily). 
This would be most typically noticed as a LOCK WAIT (and/or 
timeout) on an INTERNAL CATALOG CACHE lock type - where the 
transaction holding the lock holds the lock in share mode and 
the lock waiter is waiting to acquire the lock exclusively. 
The lock holder can be deduced to have done an implicit internal 
rebind by virtue of the fact that it holds one or more INTERNAL 
P locks in exclusive mode.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* static SQL                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to Version 10.1 fixpack 3 or later.                  * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Fixed in Version 10.1 fixpack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.04.2013
01.10.2013
01.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList