home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC98528 Status: Geschlossen

POSSIBLE HIGH CPU USAGE OF FUNCTION STMMPCFINDSIMVAR UNDER VERY HIGH
WORKLOAD

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 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
verfügbare FixPacks:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 Version 10.5 Fix Pack 4.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
31.12.2013
06.11.2014
06.11.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList