suche 36x36
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 IT32126 Status: Closed

MEMORY LEAK IN FMP PROCESS WHEN KEEPFENCED IS NO

product:
DB2 FOR LUW / DB2FORLUW / B50 - DB2
Problem description:
When KEEPFENCED is set to NO, there might be memory leak in fmp
process.

Output of command "db2pd -memblock pid= sort" shows
File 252546453 LOC 672(can be vary on different Db2 versions)
used a lot of memory:

All memory blocks in Private memory set for process 28639648

Memory blocks sorted by size:
PoolID     PoolName   TotalSize(Bytes)     TotalCount LOC   File

0                     224748800            175585     672
252546453
0                     7042520              176063     638
1602215076
...


To reproduce the memory leak:

$ db2pd -memblock pid= sort

All memory blocks in Private memory set for process 25559196

Memory blocks sorted by size:
PoolID     PoolName   TotalSize(Bytes)     TotalCount LOC   File
0                     977920               764        672
252546453
...

$ db2 "select * from sysibmadm.snapappl" > /dev/null

$ db2pd -memblock pid= sort

All memory blocks in Private memory set for process 25559196

Memory blocks sorted by size:
PoolID     PoolName   TotalSize(Bytes)     TotalCount LOC   File
0                     979200               765        672
252546453
...
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* all                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 v11.5.4.0 or higher                           *
****************************************************************
Local Fix:
Set dbm cfg KEEPFENCED to yes, then restart the Db2 server.
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT32125 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.03.2020
30.06.2020
30.06.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)