| Latest versions | fixlist |
| 11.1.0.7 |
 |
| 10.5.0.9 |
|
| 10.1.0.6 |
|
| 9.8.0.5 |
|
| 9.7.0.11 |
|
| 9.5.0.10 |
|
| 9.1.0.12 |
|
| Have problems? - contact us. | |
| Register for free |
|
| Contact form |
|
DB2 - Problem description
| Problem IT08439 | Status: Closed |
DB2SAP: DB2 PRIVATE MEMORY LEAK IN SAPTOOLS.MEMORY_TABLE | |
| product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problem description: | |
It could happen that DB2 calls OPEN...FETCH...CLOSE for the same
input many times. Memory gets allocated during OPEN(n calls
possible), but only freed on FINAL (1 call).
The memory leak occurs in a db2 agent's private heap, which can
be monitored with MON_GET_MEMORY_POOL, eg.
db2 "select MEMORY_POOL_TYPE, APPLICATION_HANDLE, EDU_ID,
MEMORY_POOL_USED from
table(MON_GET_MEMORY_POOL('PRIVATE',null,null)) where
MEMORY_POOL_TYPE='PRIVATE' order by MEMORY_POOL_USED desc"
db2pd -memblocks pid=<db2sysc pid> will show the leak is coming
from file 1416116631 LOC 531 (line of code may vary somewhat),
eg :
>db2pd -memblocks pid=12345 top
PoolID PoolName TotalSize(Bytes) TotalCount LOC File
0 81788604 545254 531
1416116631
... | |
| Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * all SAP customers. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade. * **************************************************************** | |
| Local Fix: | |
| Solution | |
| Workaround | |
not known / see Local fix | |
| Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 21.04.2015 25.08.2015 20.06.2016 |
| Problem solved at the following versions (IBM BugInfos) | |
| Problem solved according to the fixlist(s) of the following version(s) | |
| 10.5.0.6 |
|
| 10.5.0.7 |
|