DB2 - Problem description
Problem IT02992 | Status: Closed |
PRIVATE MEMORY LEAK IN PERSISTENT PRIVATE MEMORY POOL WHEN COMPILING FEDERATED QUERIES | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
When using Federated server there is a memory leak when the statements are compiled. The command 'db2pd -dbptnmem' will show high instance memory usage from the 'PRIVATE' consumer The MON_GET_MEMORY_POOL routine will show high memory usage from the PERSISTENT_PRIVATE memory pool. This, along with the usage of federated server, is enough to identify the problem. db2 "select * from table(mon_get_memory_pool('PRIVATE',null,null)) More detailed information pointing to the problem can be seen when running the following command: db2pd -memblocks private sort pid=[db2sysc pid] > db2pd_membPRIVATESort.out will show large memory usage in the following areas: All memory blocks in Private set. Address DataAddress PoolID PoolName BlkAge Size(Bytes) I LOC File Total set size: 0 bytes Memory blocks sorted by size: PoolID PoolName TotalSize(Bytes) TotalCount LOC File 0 60226016 752652 451 2074526459 0 14784439 1240354 1874 2093195612 0 8388608 16 9153 3922823597 The LOC column may differ for each Fix Pack level. The problem was introduced in DB2 10.5. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * All Federated Server users * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 LUW 10.5 Fix Pack 5 * **************************************************************** | |
Local Fix: | |
n/a | |
Solution | |
First fixed in DB2 LUW 10.5 Fix Pack 5 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 07.07.2014 13.03.2015 25.07.2016 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.5 |