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 IT04156 Status: Geschlossen

APPLICATION PERFORMING LOCK ESCALATION CANNOT BE FORCED

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
An application that is holding a large number of locks may take 
a long time to complete lock escalation.  As a result, other 
applications may experience lock waits, timeouts, deadlocks. 
Lock escalation is not interruptable, and as a result, the 
system may appear to be hanging.  Currently, the only options 
are to forcibly bring down DB2, or wait until the lock 
escalation completes. 
 
This APAR will add an enhancement to allow the lock escalation 
process to be interrupted, so that an agent that is in lock 
escalation can be forced.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to the latest fix pack.                              * 
****************************************************************
Local-Fix:
Lösung
Problem is first fixed in DB2 UDB Version 10.1 fix pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
03.09.2014
13.07.2015
13.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList