DB2 - Problem description
Problem IC88239 | Status: Closed |
MEMORY LEAK IN APPLICATION SHARED HEAP INSERTING INTO PARTITIONED MDC TABLES | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
When performing multiple inserts within a unit of work into partitioned MDC tables, a small amount of memory may be leaked in the Application Shared Heap (inside the Application Memory set). This memory usage accumulates until the database deactivates, and may result in performance degradation or other out-of-memory related errors. The Application Shared Heap can be monitored using : - database snapshot (look for the "Applications Shared Heap" memory pool entry) - db2pd -db <database> -mempools (look for the row with a PoolName of appshrh ) - on DB2 version 9.7 Fix Pack 5 and higher, use the MON_GET_MEMORY_POOL routine filtering on MEMORY_POOL_TYPE='APPL_SHARED' The leaking memory can be identified using the following: db2pd -db <database> -memblocks appctl | grep 1560397958 ( use "-memblocks appl 20" on version 9.7 Fix Pack 4 and higher ) If a large number of rows similar to the following are seen, this APAR likely applies: 0x070000003003FFC8 20 appshrh 59 1 0 1497 1560397958 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 version 10.1.0.3. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
The problem is first fixed in DB2 version 10.1.0.3. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 14.11.2012 01.10.2013 01.10.2013 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.3 | |
10.1.0.3 |