IBM Support

IC77765: DB2STOP FORCE HANGING BECAUSE SOME ASYNC-EDUS (DB2PFCHR, DB2PCLNR) REMAIN ACTIVE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This problem happens if there has been an abnormal application
    connection failure caused for example by a memory allocation
    failure, where the database has been activated with all the
    async-EDUs up and running, but agent initialization fails. The
    problem is that there exists a small timing window where the
    failed agent can become the last agent connected to the
    database, and will be handling the database deactivation task.
    When that happens, due to the failed initialization the database
    will not be deactivated properly, causing some async-EDUs to be
    left behind without properly terminated. When this issue
    happens, the db2stop force process will be hanging on the
    following stack:
    
    waitid
    waitpid
    sqlowchd
    sqloexec2
    sqleStartStopSingleNode
    sqleIssueStartStop
    sqleProcessStartStop
    main
    
    The db2diag.log will show that the system controller keeps
    waiting on some active EDUs:
    
    2011-06-02-13.32.42.517358-240 I7277360E388       LEVEL: Event
    PID     : 28643                TID  : 2           PROC : db2sysc
    INSTANCE: db2inst1             NODE : 000
    EDUID   : 2                    EDUNAME: db2sysc
    FUNCTION: DB2 UDB, oper system services,
    sqloSystemControllerMain, probe:270
    DATA #1 : String, 26 bytes
    Active EDUs to be waited :
    DATA #2 : unsigned integer, 4 bytes
    24
    

Local fix

  • The instance will have to be shutdown by killing the process
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * all                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * see error description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Avoid the out-of-memory condition by increasing the amount   *
    * of physical memory on the system                             *
    ****************************************************************
    

Problem conclusion

  • v97 fp 5
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC77765

  • 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-07-27

  • Closed date

    2012-02-28

  • Last modified date

    2012-02-28

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

    IC77759

  • 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

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
28 February 2012