|
Problem IT06120
|
Status: Closed |
DB2 SERVER MEMORY LEAK IN APPLICATION HEAP WHEN PROCESSING LOB DATA IN A DPF ENVIRONMENT |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
A small amount of memory is leaked in the application heap for
each row processed where LOB or Long Field data is sent between
partitions in a DPF (Database-partitioning feature) environment.
The leak occurs on the coordinator partition only, and is
released when the connection is terminated as the entire
application heap is freed. DB2 levels version 10.1 GA and 10.5
GA and higher are vulnerable.
Besides monitoring application heap memory pools for abnormal
usage with standard memory monitoring tools (eg.
MON_GET_MEMORY_POOL), the leak symptom can be matched by running
the following command.
db2pd -alldbs -memblocks appl 1 | grep 896367698
0x0A00020000052EA8 0x0A00020000052EC0 1 apph
508 24 1 2008 896367698
0x0A00020000052EE8 0x0A00020000052F00 1 apph
513 24 1 2008 896367698
0x0A00020000052F28 0x0A00020000052F40 1 apph
518 24 1 2008 896367698
0x0A00020000052F68 0x0A00020000052F80 1 apph
523 24 1 2008 896367698
...
If there are a large number of records where the 6th column is
"24" (meaning 24 bytes) and the last column is "896367698", this
is matching the symptoms of the leak in this APAR. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 systems using the DPF (multiple data partitions) feature *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 10.1 Fix Pack 5 *
**************************************************************** |
| Local Fix: |
force off applications with abnormally high application heap
memory usage to release leaked memory |
| Solution |
Problem first fixed in DB2 Version 10.1 Fix Pack 5 |
| Workaround |
see Local Fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.12.2014
30.07.2015
30.07.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
