DB2 FOR LUW / DB2FORLUW / 910 - DB2

Every time a drop DGTT (Declared Global Temporary Table) is run 
within an application, DB2 creates a new environment entry for 
this statement in the cache. All new statements that are coming 
in have to traverse through the list of environments, holding a 
latch, making everybody else wait. 
 
The following is one such latch that waits: 
 
SQLO_LT_sqlra_anchor_stmt__latch - the package cache dynamic SQL 
anchor latch.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 V9.1 users (FP9 and below)                           * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Every time a drop DGTT (Declared Global Temporary Table) is  * 
* run within an application, DB2 creates a new environment     * 
* entry for this statement in the cache. All new statements    * 
* that are coming in have to traverse through the list of      * 
* environments, holding a latch, making everybody else wait.   * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Use local fix or upgrade to DB2 V9.1 FP10 to avail fix for   * 
* this APAR.                                                   * 
****************************************************************

i) db2set DB2_APM_PERFORMANCE=1 
ii) Turn off statement monitor 
iii) db2 flush package cache dynamic

DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
 DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
 DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows
 

APAR first fixed in DB2 V9.1 Fp10

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC71954 IC71955 IC72253 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

15.10.2010
13.06.2011
13.06.2011

9.1.FP10