|
Problem IT16569
|
Status: Closed |
CURCOUNT IN DB2PD -REORG IS NOT MONITORED WHEN ONLINE REORG WITHCLEANUP OVERFLOWS OPTION |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
When a user issuing online reorg with cleanup overflows option,
db2pd -reorg cannot monitor CurCount.
A user only monitor 0 in CurCount like as the following example
during the reorg.
--------------------------------------
Database Member 0 -- Database XXXX -- Active -- Up 0 days
00:04:54 -- Date 2016-08-04-11.06.06.740359
Table Reorg Information:
Address TbspaceID TableID PartID MasterTbs MasterTab
TableName Type IndexID TempSpaceID
0x0A0002002D905C80 2 19 n/a n/a n/a
EMPP Online 0 2
Table Reorg Stats:
Address TableName Start End
PhaseStart MaxPhase Phase CurCount MaxCount
Status Completion
0x0A0002002D905C80 EMPP 08/04/2016 11:05:59 n/a
n/a n/a n/a 0 141610
Started 0
-------------------------------------- |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* db2pdh *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 11.1 Fix Pack 1 or higher. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 11.1 Mod1 Fix Pack1 iFix001 for Linux, UNIX, and Windows
DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.08.2016
18.05.2017
18.05.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 11.1.1.1
|
 |
