|
Problem IC86520
|
Status: Closed |
HEALTH MONITOR ACTIVITIES AND AUTOMATIC MAINTENANCE MAY FAIL DUE TO MEMORY LEAK/EXHAUSTION |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
On instances with volatile databases (frequently
deactivating/activating), and with health monitoring and/or
automatic maintenance enabled, a memory leak may occur in the
memory segment supporting health monitor and automatic
maintenance activities. The memory segment is a relatively
small fixed size, so the concern is not the amount of memory
consumed, but that these activities will start failing once the
memory insides the segment becomes exhausted (it is being
managed/assigned internally by DB2).
A variety of symptoms may occur, such as tables statistics not
being updated, which can negatively affect optimizer
plans/performance. The following db2diag.log entry is an
indication that the memory inside the segment is exhausted:
2011-08-19-14.18.41.245798+330 I29615875A490 LEVEL: Severe
PID : 1126558 TID : 772 PROC : db2acd
0
INSTANCE: db2inst1 NODE : 000
EDUID : 772 EDUNAME: db2acd 0
FUNCTION: DB2 UDB, Health Monitor, hmonTreeResizeRequest,
probe:10
MESSAGE : The health monitor shared memory segment is full.
Current size
100663296, free 36800
DATA #1 : Hexdump, 4 bytes
0x0000000110518DB0 : 0000 0000
.... |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* systems with health monitor or automatic maintenance enabled *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* upgrade to DB2 Version 9.7 Fix Pack 8 *
**************************************************************** |
| Local Fix: |
If possible, explicitly activate databases. This prevents the
memory leak by avoiding volatility in the metadata maintained by
health monitoring and automatic maintenance activities, and may
generally improve performance. |
| available fix packs: |
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem first fixed in DB2 Version 9.7 Fix Pack 8 |
| Workaround |
see local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC86534
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.09.2012
11.07.2013
11.07.2013 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP8
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.8
|
 |
