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

USING EXTERNAL PLUG IN FOR ALERTS WILL CAUSE MEMORY LEAK IN THE HEALTH
INDICATOR

product:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problem description:
The Health Monitor will leak memory if running a customized 
external plugin for publishing alerts.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Memory leak in Health monitor ( db2acd) if an external       * 
* customized plugin library for alerts being used              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V9.5 FP8 or later if using a plugin customized    * 
* library for Health Monitor Alerts                            * 
****************************************************************
Local Fix:
Avoid using a customized plugin for alerts
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
First fixed in Db2 V9.5 FP8
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC73213 IC73214 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.12.2010
27.06.2011
27.06.2011
Problem solved at the following versions (IBM BugInfos)
9.5.FP8
Problem solved according to the fixlist(s) of the following version(s)
9.5.0.8 FixList