|
Problem IT07948
|
Status: Closed |
DB2 MEMORY LEAK IN APPLICATION HEAP WHEN QUERYING FOR LOB DATA USING PERSISTENT CONNECTIONS |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 Version 9.7 Fixpack 10 and below *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fixpack 11 *
**************************************************************** |
| Local Fix: |
|
| Solution |
Fixed in DB2 Version 9.7 Fixpack 11 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 26.03.2015
28.10.2015
28.10.2015 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP11
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.11
|
 |
