IBM Support

IC77056: OFFLINE ADD NODE AND NORMAL DB2START FAIL DUE TO DEADLATCH DURING INSTANCE STARTUP

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • During instance startup on a partition, a deadlatch may occur
    while initiializing the DBMS memory set. In rare circumstances,
    additional memory may need to be allocated while trying to set
    up the memory set which leads to a deadlatch situation. This is
    due to an internal accounting error when estimating the initial
    size of a memory heap. If the deadlatch occurs then db2start
    will timeout or hang.
    
    A db2trc taken during db2start would look like this if the issue
    occurs:
    
    11541          0.986140292   DB2StartMain data [probe 375]
    11542          0.986141042   | SqloMemController::initialize
    entry
    11543          0.986141941   | SqloMemController::initialize
    exit
    11544          0.986143324   | sqloRegisterMemorySetWithPMC
    entry
    11545          0.986145712   | |
    SqloMemController::registerConsumer entry
    11546          0.986147470   | | | sqlogmblkEx entry
    11547          0.986150005   | | | |
    SMemBasePool::getNewChunkSubgroup entry
    11548          0.986153271   | | | | | sqlo_xlatch::getConflict
    entry
    11549          0.986206322   | | | | | sqlo_xlatch::getConflict
    mbt [Marker:PD_LATCH_TRACE_WAIT_STARTING ]
    13835        306.975846427   | | | | | | sqleKillNode entry
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * DPF                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See above.                                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Please upgrade to DB2 9.7 FP5 or later                       *
    ****************************************************************
    

Problem conclusion

  • Deadlatch situation is resolved by properly estimating size of
    internal memory heap. The problem is first fixed in DB2 9.7 FP5.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC77056

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-06-18

  • Closed date

    2011-12-16

  • Last modified date

    2011-12-16

  • 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

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC77056

Modified date: 16 December 2011