| Latest versions | 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 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IT04156 | Status: Closed |
APPLICATION PERFORMING LOCK ESCALATION CANNOT BE FORCED | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
| Problem description: | |
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 Summary: | |
**************************************************************** * USERS AFFECTED: * * All users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to the latest fix pack. * **************************************************************** | |
| Local Fix: | |
| Solution | |
Problem is first fixed in DB2 UDB Version 10.1 fix pack 5. | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 03.09.2014 13.07.2015 13.07.2015 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.1.0.5 |
|