IBM Support

IC70419: CONNECT RESET (IMPLICIT OR EXPLICIT) MAY APPEAR TO HANG WHEN ALTER TABLESPACE TYPE OPERATIONS ARE RUNNING

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • An CONNECT RESET operation (either an explicit CONNECT RESET, or
    a CONNECT TO DB operation that invokes a connect-reset
    implicitly because a connection already exists) may hang when an
    ALTER TABLESPACE EXTEND/RESIZE/DROP type of operation is
    running.
    
    The latching protocol used by the connect-reset operation to
    determine if the disconnecting application has quiesced any
    tablespaces conflicts with latches that are held by the
    alter-tablespace operation.
    
    Stack dumps of the hanging processes will show:
    - the connect-reset operation executing in
    sqlbTerminateApplication and waiting for this readLatch:
    "Waiting on latch type: (SQLO_LT_SQLB_POOL_CB__readLatch) -
    Address: (0x643144fb8), Line: 6278, File: sqlbenvi.C"
    
    - the alter-tablespace operation typically executing in
    sqlbAlter... and holding this readLatch:
    "Holding Latch type: (SQLO_LT_SQLB_POOL_CB__readLatch) -
    Address: (0x643144fb8), Line: 5210, File: sqlbistorage.h"
    
    The fix will prevent the connect-reset from waiting only if no
    other application is holding a QUIESCE state on the tablespace
    that is being altered.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users at DB2 V9.7 FP3a and below level                   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * An CONNECT RESET operation (either an explicit CONNECT       *
    * RESET, or                                                    *
    * a CONNECT TO DB operation that invokes a connect-reset       *
    *                                                              *
    * implicitly because a connection already exists) may hang     *
    * when an                                                      *
    * ALTER TABLESPACE EXTEND/RESIZE/DROP type of operation is     *
    *                                                              *
    * running.                                                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 LUW Version 9.7 Fix Pack 4                    *
    ****************************************************************
    

Problem conclusion

  • Problem was fixed in Version 9.7 Fix Pack 4
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC70419

  • 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-08-05

  • Closed date

    2011-05-02

  • Last modified date

    2011-05-02

  • 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



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC70419

Modified date: 02 May 2011