home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC91307 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* static SQL                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* upgrade to Version 10.1 fixpack 3 or later.                  * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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

Lösung
Fixed in Version 10.1 fixpack 3
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
03.04.2013
01.10.2013
01.10.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.3 FixList
10.1.0.3 FixList