IBM Support

IT18427: DB2 might leak private memory if locators are used to access thedata (e.g. to fetch LOBs)

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DB2 server might leak PRIVATE memory if applications connected
    to database are using locators to access the data (e.g. to fetch
    LOBs)
    
    As the result, one will observe an increase in PRIVATE memory
    usage
    in MON_GET_MEMORY_POOL or in db2pd output:
    $ db2pd -dbptnmem
    
    Leaking allocation will be tracked as ones coming from file ID
    2904145706 and line of code (LOC) ~1551 (LOC might differ
    between fix packs) in the output from:
    $ db2pd -memblocks private pid=<pid_of_db2sysc>
    e.g:
    Address            . PoolID  .  Size(Bytes  I LOC   File
    0x00007FA6E731B068 . 0       .  2960        1 1551  2904145706
    0x00007FA6E731BC28 . 0       .  2960        1 1551  2904145706
    0x00007FA6E731C7E8 . 0       .  2960        1 1551  2904145706
    0x00007FA6E731D3A8 . 0       .  2960        1 1551  2904145706
    ...
    
    NOTE: running
    $ db2pd -memblocks private
    will commit all private memory that DB2 has allocated, which
    might result in paging if memory is overcommited - please run it
    with caution or with supervision of DB2 support.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 11.1 Mod 2 Fix Pack 2 or higher               *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 11.1 Mod 2 Fix Pack 2
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT18427

  • 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

    2016-12-15

  • Closed date

    2017-06-23

  • Last modified date

    2017-06-23

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

    IT18324

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

[{"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","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
29 June 2020