DB2 - Problem description
Problem IC67372 | Status: Closed |
DB2ACD (HEALTH MONITOR PROCESS) MAY MEMORY LEAK MSGALERTACTION OBJECTS IF AN ACTION SCRIPT XML CONFIGURATION IS USED | |
product: | |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 | |
Problem description: | |
The db2acd process (health monitor process) may leak memory (msgAlertObjects) if it is action script configured through xml configuration tool. This feature is only available for some special customers. Normal health monitor processing is not affected. Typical symptoms is an increase of private memory as seen in ps output (RSS column) or pmap output on platforms were this tool is available. The leak can increase memory size up to several Gigabyte. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * The db2acd process (health monitor process) may leakmemory * * (msgAlertObjects) if it is action scriptconfigured through * * xml configuration tool.This feature is only available for * * some specialcustomers. Normal health monitor processing is * * notaffected.Typical symptoms is an increase of private * * memory as seen inps output (RSS column) or pmap output on * * platforms werethis tool is available. The leak can increase * * memory size upto several Gigabyte. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 UDB Version 9.5 FixPak 6 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 UDB Version 9.5 FixPak 6 | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC67376 IC77521 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 24.03.2010 09.09.2010 09.09.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.5. | |
Problem solved according to the fixlist(s) of the following version(s) |