|
Problem IT29984
|
Status: Closed |
ROW LOCK CAN TIMEOUT DURING OLR IF AN INDEX WAS SPECIFIED OR IF THERE'S A CLUSTERING INDEX ON THE TABLE
|
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Typically row locks will never timeout when OLR requests them.
However, if an index was specified in the OLR command or if
there's a clustering index on the table, it is possible for the
lock request coming from OLR to time out.
If a lock timeout occurs, this will pause the current OLR. If
db2pd -reorg is run, it will look something like this:
->EXECUTING(STMT-19): Resume Online Reorg
OUTPUT/RESULT:
Database Member 0 -- Database REORGDB -- Active -- Up 0
days 00:00:47 -- Date 2019-08-12-13.45.09.387531
Table Reorg Information:
Address TbspaceID TableID PartID MasterTbs
MasterTab TableName Type IndexID TempSpaceID
0x00007F1FD804D988 5 4 n/a n/a n/a
T1 Online 1 5
Table Reorg Stats:
Address TableName Start
End PhaseStart MaxPhase Phase
CurCount MaxCount Status Completion
0x00007F1FD804D988 T1 08/12/2019 13:44:34
08/12/2019 13:44:59 n/a n/a n/a 0
3015 Paused 4294967295 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* server side fix *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
see local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.08.2019
28.06.2020
28.06.2020 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
