DB2 FOR LUW / DB2FORLUW / 970 - DB2

When a significant number of applications are executing a small 
number of statements, turning on statement monitoring may result 
in CPU spiking and reduced throughput as latch contention occurs 
in the dynamic SQL entries in the package cache. 
 
Stack dumps will show the sqlra_anchor_stmt as being the 
contentious latch.   Various calling stacks are possible and are 
not included here.

**************************************************************** 
* USERS AFFECTED:                                              * 
* statement monitor enabled                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* performance degradation with statement monitor enabled       * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* move to DB2 for LUW version 9.7, fixpack 4                   * 
****************************************************************

turn off statement montoring.

DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

fixed in DB2 for LUW version 9.7, fixpack 4

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC74395 
Nachfolger : 

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

17.01.2011
13.05.2011
13.05.2011

9.7.FP4