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 IC91295 Status: Closed

POSSIBLE HIGH CPU USAGE OF FUNCTION STMMPCFINDSIMVAR UNDER VERY HIGH
WORKLOAD

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
Under specific very high workload situations, function 
stmmPCfindSimVar can consume a large amount of CPU time. 
 
Configuration settings to trigger this behavior: 
* STMM enabled or disabled 
* PCKCACHESZ set to AUTOMATIC 
 
This APAR will help to reduce CPU usage of function 
stmmPCfindSimVar.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 4.                      * 
****************************************************************
Local Fix:
* Set PCKCACHESZ to a fixed value 
* Make similar SQL statements look different by adding comments 
to the statment text at the end
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 Version 10.1 Fix Pack 4.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC98528 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
03.04.2013
23.06.2014
23.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList