IBM Support

IC78993: LONG DATABASE ACTIVATION AFTER HADR RESTART DUE TO A DB2 CRASH.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If an HADR primary database abends for some reason and is
    restarted, with an active client application workload against it
    (read clients trying to connect to it), the activation of the
    database may take a VERY long time to occur
    (minutes to hours depending on the number of clients trying to
    connect).
    
    The client workload needs to have a timeout configuration such
    that if the client is unable to connect within timeout settings,
    the client closes the connection to the server and, attempts
    (client re-route/ ACR) a connection to the secondary. This
    leaves an agent resource on the primary on a "queue" behind the
    activation of the database.
    
    When this agent finally gets its turn, it tries to activate the
    db and realizes it needs to start the HADR primary. While doing
    that, it determines that its client connection has gone away so
    it aborts. All agents on the queue go through this processing.
    
    The client workload, once it fails to connect to the secondary
    database, re-attempts to connect to the primary where, again, it
    eventually times out, adding even MORE agents to the queue and
    the cycle continues...
    

Local fix

  • As a workaround:
    
    1. Restart db2 server
    2. Uncatalog the database
    3. Re-catalog the database
    4. Activate the database
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users on DB2 v97 Fp5 and earlier                         *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 v97 FP6                                       *
    ****************************************************************
    

Problem conclusion

  • First Fixed in DB2 v97 FP6
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC78993

  • 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-09-29

  • Closed date

    2012-06-22

  • Last modified date

    2012-06-22

  • 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 PSY

       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:
22 June 2012