DB2 - Problembeschreibung
Problem IT28248 | Status: Geschlossen |
CLEANING UP OF EDU CAUSES PRIVATE MEMORY TO LEAK (WINDOWS PLATFORM ONLY) | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problembeschreibung: | |
This issue is specific to Db2 running under Windows operating system only and with version 11.1 mod 4 fix pack 4. When a EDU is released from serving an application it will leak a private memory block. Depending on the configuration and number of connections coming in/out the leak might grow rather quickly. The type of blocks leaked will be visible in a "db2fodc -memory" output file "db2pd.memblocks.private". In this file, the persist pool of the private memory will be the main consumer with a large count of blocks: ... Total size for persist pool: 7673057192 bytes (PoolID: 86, SecondID: 0, PoolAddr: 0x000001504C280498) Total size for Private memory set: 7673668136 bytes All memory consumers in Private memory set: PoolAddr PoolID PoolName SecondID TotalSize(Bytes) %Bytes TotalCount %Count LOC File 0x000001504C280498 86 persist 0 7663597408 99.87 216388 99.43 476 4284367586 0x000001504C280498 86 persist 0 6549088 0.09 52 0.02 196 1235720678 0x000001504C280498 86 persist 0 1159264 0.02 490 0.23 244 4283993058 0x000001504C280498 86 persist 0 786432 0.01 6 0.00 5176 745254192 ... | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Db2 running on Windows environment only * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * upgrade to Db2 version 11.1 mod 4 fp5 * **************************************************************** | |
Local-Fix: | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Bug-Verfolgung | |
Vorgänger : Nachfolger : IT30794 IT31299 | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 28.02.2019 31.10.2019 31.10.2019 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version |