|
Problem IT39048
|
Status: Closed |
HANG WAITING FOR SQLO_LT_SQLI_IDXCB__IDXTREELATCH WITH NO HOLDERS after failed REORG INDEX(ES) .. RECLAIM EXTENTS
|
| product: |
DB2 FOR LUW / DB2FORLUW / B50 - DB2 |
| Problem description: |
If REORG INDEX(ES) .. RECLAIM EXTENTS encounters an error in a
certain timing window, it may fail without releasing the
SQLO_LT_SQLI_IDXCB__IDXTREELATCH
Any subsequent access to the corresponding index that needs to
get this latch, will hang.
db2stop may get error SQL6037N START or STOP DATABASE MANAGER
timeout value was reached.
The following is an example of output from db2pd-latches showing
a number of applications waiting on
SQLO_LT_SQLI_IDXCB__idxTreeLatch without any holders:
Address Holder Waiter ..
LatchType
0x0A0002082A8E3FA0 0 156006 ..
SQLO_LT_SQLI_IDXCB__idxTreeLatch
0x0A0002082A8E3FA0 0 168829 ...
SQLO_LT_SQLI_IDXCB__idxTreeLatch |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* User of Reorg Indexes .. Reclaim Extents on a column *
* organized table that fails in a specific timing condition *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v115m7fp0 *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* User of Reorg Indexes .. Reclaim Extents on a column *
* organized table that fails in a specific timing condition *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to v115m7fp0 *
**************************************************************** |
| Comment |
Fixed in v115m7fp0 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.11.2021
21.11.2021
21.11.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
