|
Problem IC70417
|
Status: Closed |
CONNECT RESET (IMPLICIT OR EXPLICIT) MAY APPEAR TO HANG WHEN ALTER TABLESPACE TYPE OPERATIONS ARE RUNNING |
| product: |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 |
| 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.
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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users *
****************************************************************
* 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. *
* *
* 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. *
****************************************************************
* RECOMMENDATION: *
* Upgrade DB2 to 9.1 Fix Pack 10 or later version *
* *
* This issue has been fixed in these versions *
* v9.1 FP10 IC70417 *
* v9.5 FP7 IC70418 *
* v9.7 FP4 IC70419 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
|
| Solution |
Problem was first fixed in Version 9.1 Fix Pack 10 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.08.2010
13.06.2011
30.08.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.FP10,
9.5.FP7,
9.7.FP4
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.10
|
 |
