IBM Support

IC69576: CRASH RECOVERY WILL NOT BE TERMINATED ANY MORE IF THE FIRST CLIENT CONNECTION IS GONE

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Normally during a crash recovery, if the first client connection
    is gone, then the crash recovery will be terminated.
    This APAR fix will let the crash recovery complete, even when
    the first client connection is gone.
    The idea here is that recovery, if driven implicitly, has
    nothing to do with the client connection - the client just so
    happens to be the first to run into a database that needs
    restart processing.
    The bottom line is that the database requires recovery and that
    should be completed as soon as possible.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * CRASH RECOVERY WILL NOT BE TERMINATED ANY MORE IF THE FIRST  *
    * CLIENT CONNECTION IS GONE                                    *
    * Normally during a crash recovery, if the first client        *
    * connection                                                   *
    * is gone, then the crash recovery will be terminated.         *
    *                                                              *
    * This APAR fix will let the crash recovery complete, even     *
    * when                                                         *
    * the first client connection is gone.                         *
    *                                                              *
    * The idea here is that recovery, if driven implicitly, has    *
    *                                                              *
    * nothing to do with the client connection - the client just   *
    * so                                                           *
    * happens to be the first to run into a database that needs    *
    *                                                              *
    * restart processing.                                          *
    *                                                              *
    * The bottom line is that the database requires recovery and   *
    * that                                                         *
    * should be completed as soon as possible.                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 9.7 and Fixpack 4                     *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in DB2 Version 9.7 and Fixpack 4
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC69576

  • 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

    2010-06-30

  • Closed date

    2011-04-28

  • Last modified date

    2011-04-28

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

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

    IC70386 IC72714

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSY

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC69576

Modified date: 28 April 2011