|
Problem IC70419
|
Status: Geschlossen |
CONNECT RESET (IMPLICIT OR EXPLICIT) MAY APPEAR TO HANG WHEN ALTER TABLESPACE TYPE OPERATIONS ARE RUNNING |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
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-Zusammenfassung: |
****************************************************************
* 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 *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Lösung |
Problem was fixed in Version 9.7 Fix Pack 4 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 05.08.2010
02.05.2011
02.05.2011 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP4
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.4
|
 |
