IBM Support

IT28311: BSUH MEMORY LEAK WHEN CONNECTING TO FORMER HADR PRIMARY WHICH HAS BEEN DEACTIVATED DUE TO TAKEOVER BY FORCE

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

  • The BSU heap might leak when connecting former HADR primary
    which has been deactivated due to TAKEOVER BY FORCE.
    The following steps ilustrates how the leak happns, and how to
    monitor that.
    
    1. Setup HADR pair.
    
    2. Do takeover HADR by force (at standby)
    $ db2 takeover hadr on db <dbname> by force
    
    3. Connect to former primary.
    $ db2 connect to <dbname>
    // it fails with SQL1776N rc=6 as expected.
    
    We can see the following memory block(s) increases by the
    connect requests in the former primary instance.
    
    $ db2pd -memblock sort 71
    PoolID  PoolName   TotalSize(Bytes)  TotalCount LOC  File
    71      bsuh         5640608          167       44   2986298199
    

Local fix

  • Please recover the former primary database to prevent allocating
    the memory.
    For example, activate the former primary as new standby like as
    below;
    $ db2 start hadr on db <dbname> as standby
    
    Please restart the instance to free up the leaking memory in
    former primary instance.
    For example:
    db2stop force
    db2start
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * all                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Db2 11.1.4.6 or higher                            *
    ****************************************************************
    

Problem conclusion

  • Upgrade to Db2 11.1.4.6 or higher
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT28311

  • 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

    2019-03-06

  • Closed date

    2021-03-31

  • Last modified date

    2021-03-31

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

  • 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

[{"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:
01 April 2021