DB2 FOR LUW / DB2FORLUW / 970 - DB2

If connections are persistent, under certain conditions of 
querying  for LOB data, you may find a memory leak in 
application heap. 
 
To isolate this issue, you may monitor with monitoring tools 
such as MON_GET_MEMORY_SET which will show high levels of 
"Application" memory set, and 
MON_GET_MEMORY_POOL which will show a high/growing level of 
memory usage within specific "Application" heap memory pools. 
 
After isolating to Application heap being the cause of growth, 
you may isolate to a specific block which is leaking using the 
db2pd below: 
 
db2pd -db <dbname> -memblocks top 
 
Top memory consumers in Appl memory set: 
PoolID     PoolName   TotalSize(Bytes)     %Bytes TotalCount 
%Count  LOC    File 
1               apph          353395680            8.48 
11043615    0.18       4199   925998910 
1               apph          352491840            8.46 
11015370    0.18       4199   925998910 
 
You will see high number of allocations from 925998910 block. 
 
As the connection stays persistent, the above block allocations 
will keep growing in number.

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 Version 9.7 Fixpack 10 and below                         * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 9.7 Fixpack 11                        * 
****************************************************************

Fixed in DB2 Version 9.7 Fixpack 11

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

26.03.2015
28.10.2015
28.10.2015

9.7.FP11