home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC74395 Status: Closed

THROUGHPUT DECREASE AND CPU USAGE INCREASE WHEN STATEMENT MONITOR SWITCH ON

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
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.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* statement monitor switch on                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* performance decrease with statement monitor on.   CPU kernel * 
* increase                                                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* move to DB2 for LUW version v9.5 fxpack 8                    * 
****************************************************************
Local Fix:
turn off statement montoring.
available fix packs:
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Fixed in DB2 for LUW version v9.5 fxpack 8
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.02.2011
05.07.2011
05.07.2011
Problem solved at the following versions (IBM BugInfos)
9.5.
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.8 FixList