IBM Support

IT32125: MEMORY LEAK IN FMP PROCESS WHEN KEEPFENCED IS NO

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When KEEPFENCED is set to NO, there might be memory leak in fmp
    process.
    
    Output of command "db2pd -memblock pid=<fmp 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=<fmp 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=<fmp 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
    ...
    

Local fix

  • Set dbm cfg KEEPFENCED to yes, then restart the Db2 server.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * n/a                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 for LUW V11.1 Mod4 Fixpack6 or later.         *
    ****************************************************************
    

Problem conclusion

  • This problem is firstly fixed on V11.1 Mod4 Fixpack6.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT32125

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    B10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-03-10

  • Closed date

    2021-03-21

  • Last modified date

    2021-03-21

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    IT32126

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPGG","label":"Db2 for Linux, UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.1"}]

Document Information

Modified date:
22 March 2021