DB2 - Problem description
Problem IC71954 | Status: Closed |
PERFORMANCE DEGRADATION DUE TO A PACKAGE CACHE CONTENTION WHEN MANY DROP DGTT STATEMENTS ARE RUNNING SIMULTANEOUSLY | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
Each time when we drop DGTT )Declared Global Temporary Table) in application, we create a new environment entry for this statement in the cache. Every new statements that are coming in have to traverse through the list of environments, holding a latch, making everybody else to wait. SQLO_LT_sqlra_anchor_stmt__latch - the package cache dynamic SQL anchor latch is one of the latch waiters. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All DB2 users on V9.5 FP7 and below * **************************************************************** * PROBLEM DESCRIPTION: * * Each time when we drop DGTT )Declared Global Temporary * * Table) in application, we create a new environment entry for * * this statement in the cache. Every new statements that are * * coming in have to traverse through the list of environments, * * holding a latch, making everybody else to wait. * **************************************************************** * RECOMMENDATION: * * Please upgrade to DB2 V9.5 FP8 where this APAR is first * * fixed. * **************************************************************** | |
Local Fix: | |
(i) db2set DB2_APM_PERFORMANCE=1 (ii) Turn off statement monitor (iii) db2 flush package cache dynamic | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows | |
Solution | |
APAR first fixed in DB2 V9.5 FP8. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 15.10.2010 30.06.2011 30.06.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.5.FP8 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.5.0.8 |