|
Problem IT04049
|
Status: Closed |
REORG_CURRENT_COUNTER IS LESS THAN REORG_MAX_COUNTER ON COMPLETED REORGS IN SYSIBMADM.SNAPTAB_REORG, DB2PD AND DB2TOP. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
In certain inplace reorg scenarios, it is possible for monitor
information to show that REORG_CURRENT_COUNTER is less than
REORG_MAX_COUNTER when the REORG_STATUS is completed. A similar
issue exists with db2pd and db2top where the reorg percentage is
below 100% even though the reorg has successfully completed.
This is purely a cosmetic issue rather than a functional issue
and the reorg has actually completed.
Sample output follows:
db2 "select substr(TABNAME,1,24) as tabname
REORG_CURRENT_COUNTER, REORG_MAX_COUNTER, REORG_STATUS,
REORG_COMPLETION from sysibmadm.snaptab_reorg where
REORG_CURRENT_COUNTER < REORG_MAX_COUNTER"
TABNAME REORG_CURRENT_COUNTER REORG_MAX_COUNTER REORG_STATUS
REORG_COMPLETION
---------- --------------------- -----------------
---------------------------------------------
TABLE1 263088 522111
COMPLETED SUCCESS
db2pd -db sample -reorg
Address TbspaceID TableID PartID MasterTbs
MasterTab TableName Type IndexID TempSpaceID
0x00002AAD685CA128 2 3592 n/a n/a
n/a TABLE1 Online 0 2
Address TableName Start
End PhaseStart MaxPhase Phase
CurCount MaxCount Status Completion
0x00002AAD685CA128 TABLE1 08/12/2014 06:05:11 08/12/2014
07:06:18 n/a n/a n/a 263088
522111 Done 0 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users prior to V10.1 FP5 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Please upgrade to DB2 V10.1 FP5. *
**************************************************************** |
| Local Fix: |
NA |
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 27.08.2014
23.06.2015
23.06.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
