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

HEALTH_CONT_HI TABLE FUNCTION LOOPS CAUSING DB2FMP HIGH CPU USAGE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When having a large number of tablespaces (> 500), the execution 
of the table function HEALTH_CONT_HI() may loop and cause 
db2fmp to consume high cpu (close to 100%). 
. 
Please note that health monitor is currently limited to monitor 
up to 500 tablespaces as documented in the following technote: 
. 
http://www-01.ibm.com/support/docview.wss?&uid=swg21398397 
. 
The fix does not lift the limitation. Instead, it will 
ensure that the table function runs successfully without 
looping, but will truncate the resultset to 500 tablespaces, as 
with other tablespace related health monitor data.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Problem Description: Invocation of HEALTH_CONT_HI()          * 
* TABLEFUNCTION hangs and causes DB2FMP HIGH CPU USAGE         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* The fix does not lift the health monitor restriction         * 
* tomonitor 500 tablespaces max. So, the recommendation is     * 
* toavoid using health monitor for tablespace usage            * 
* monitoring.To limit the impact health_cont_hi() on databases * 
* havingmore than 500 tablespaces, upgrade to product V9.7 Fix * 
* Pack2.                                                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 V9.7 Fix Pack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.09.2009
31.05.2010
31.05.2010
Problem solved at the following versions (IBM BugInfos)
9.7.,
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList