| Neueste Versionen | FixList |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Haben Sie Probleme? - Kontaktieren Sie uns. | |
| Kostenlos registrieren |
|
| Kontaktformular |
|
DB2 - Problembeschreibung
| Problem IT03126 | Status: Geschlossen |
APPLICATION PERFORMING LOCK ESCALATION CANNOT BE FORCED | |
| Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - 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 * **************************************************************** * PROBLEM DESCRIPTION: * * This change will allow applications performing lock * * escalation to be interrupted. * **************************************************************** * RECOMMENDATION: * * Upgrade to the latest fix pack. * **************************************************************** | |
| Local-Fix: | |
| Lösung | |
Problem is first fixed in DB2 UDB version 9.7 fix pack 10. | |
| Workaround | |
keiner bekannt / siehe Local-Fix | |
| Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 11.07.2014 10.11.2014 10.11.2014 |
| Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7.FP10 | |
| Problem behoben lt. FixList in der Version | |
| 9.7.0.10 |
|