DB2 - Problem description
Problem IT08106 | Status: Closed |
Contention on SQLP_LTRN_CHAIN__ENTRY_LATCH after lock escalation is interrupted degrades performance | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
Interrupting a lock escalation may result in a latch not being released, which in turn may cause subsequent latch contention, resulting in performance degradation. The problem can occur on version 9.7 fix pack 10 or version 10.5 fix pack 5 or 6 only. Version 10.1 is not affected. Analysis of the performance problem will show a latch wait on the SQLP_LTRN_CHAIN__entry_latch. The latch may or may not have an owner, and the owner may or may not be the same transaction that is requesting the latch. Waiting on latch type: (SQLO_LT_SQLP_LTRN_CHAIN__entry_latch) - Address: (7000001c2638260), Line: 106, File: sqlplsc.C | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to the latest fix pack. * **************************************************************** | |
Local Fix: | |
Try to avoid lock escalation or interrupting a lock escalation. | |
Solution | |
Problem is first fixed in DB2 UDB version 10.5 fix pack 7. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 02.04.2015 20.01.2016 20.01.2016 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.7 |