Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT08059 Status: Closed

CONTENTION ON SQLP_LTRN_CHAIN__ENTRY_LATCH AFTER LOCK ESCALATION IS
INTERRUPTED DEGRADES PERFORMANCE

product:
DB2 FOR LUW / DB2FORLUW / 970 - 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                                                          * 
**************************************************************** 
* 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 9.7 fix pack 11
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
31.03.2015
06.10.2015
06.10.2015
Problem solved at the following versions (IBM BugInfos)
9.7.FP11
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.11 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.