| Neueste Versionen | 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 |
|
| Haben Sie Probleme? - Kontaktieren Sie uns. | |
| Kostenlos registrieren |
|
| Kontaktformular |
|
DB2 - Problembeschreibung
| Problem IT08439 | Status: Geschlossen |
DB2SAP: DB2 PRIVATE MEMORY LEAK IN SAPTOOLS.MEMORY_TABLE | |
| Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
| Problembeschreibung: | |
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-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * all SAP customers. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade. * **************************************************************** | |
| Local-Fix: | |
| Lösung | |
| Workaround | |
keiner bekannt / siehe Local-Fix | |
| Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 21.04.2015 25.08.2015 20.06.2016 |
| Problem behoben ab folgender Versionen (IBM BugInfos) | |
| Problem behoben lt. FixList in der Version | |
| 10.5.0.6 |
|
| 10.5.0.7 |
|