Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC92599 Status: Closed

PRIVATE MEMORY LEAK ON THE DB2 SERVER BY THE DB2PFCHR THREAD

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
db2sysc process will increase in memory consumption over time. 
 
db2 private memory leak is observed within the db2pfchr thread. 
db2pd -memset output will show the 
committed size keep increasing over time for the private memory 
set. 
 
db2 select MEMORY_POOL_TYPE, MEMORY_POOL_ID, APPLICATION_HANDLE, 
 
EDU_ID, MEMORY_POOL_USED, MEMORY_POOL_USED_HWM from 
 
table"(mon_get_memory_pool('PRIVATE',null,null))" 
 
will show the max private memory is consumed by the edu threads 
corresponding to the db2prefchr threads. 
 
e.g. 
MEMORY_POOL_TYPE                 MEMORY_POOL_ID 
APPLICATION_HANDLE   EDU_ID               MEMORY_POOL_USED 
MEMORY_POOL_USED_HWM 
-------------------------------- -------------------- 
-------------------- -------------------- -------------------- 
-------------------- 
PERSISTENT_PRIVATE                                 86 
-                    0             17956864             25427968 
PRIVATE                                            88 
-                 7455              8454144              8519680 
PRIVATE                                            88 
-                 7712              7864320              7864320 
PRIVATE                                            88 
-                 7969              6881280              6881280 
 
db2pd -memblocks pid=<db2sysc pid> will show the LOC as follows: 
Memory blocks sorted by size: 
 
PoolID     PoolName   TotalSize(Bytes)     TotalCount LOC   File 
 
0                     248320000            12125      1231 
1480119721 
 
The leak is due to incorrect memory deallocation by the 
db2prefchr thread.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* See Error Description                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 for Linux, UNIX, and Windows Fix * 
* Pack 3                                                       * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem first fixed in DB2 Version 10.1 for Linux, UNIX, and 
Windows Fix Pack 3
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC95365 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.05.2013
24.10.2013
24.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList