IBM Support

Understanding Reorg Stat's CurCount MaxCount

Question & Answer


Question

How do I interpret/understand the CurCount and MaxCount in the reorg stat's?

Cause

Unexpected end of reorg when CurCount has not reached MaxCount

Answer

Per the "db2pd -d tsmdb1 -reorg" output:

The reorg statistics for a table would look similar to the following:

    Database Member 0 -- Database TSMDB1 -- Active -- Up 4 days 15:10:50 --
    Date 2015-03-31-14.57.40.351691                                        
                                                                           
    Table Reorg Information:                                                
    Address            TbspaceID TableID PartID MasterTbs MasterTab        
    TableName          Type    IndexID    TempSpaceID                      
    0x07000009D03CE1F8 5         5       n/a    n/a       n/a              
    BACKUP_OBJECTS     Online  4          5                                
                                                                           
    Table Reorg Stats:                                                      
    Address            TableName          Start               End          
    PhaseStart          MaxPhase   Phase      CurCount   MaxCount   Status  
    Completion                                                              
    0x07000009D03CE1F8 BACKUP_OBJECTS     03/31/2015 14:46:17 n/a          
    n/a                 n/a        n/a        919935     17820091   Started 
    0

The CurCount is the current row being processed and the MaxCount is an estimate of the number of rows to process. In this example the reorg is ~ 5.16% complete (919935/17820091).

Interestingly the MaxCount as an estimate may not always be very accurate. In the case where a lot of filespaces or nodes were deleted a reorg may actually finish before reaching the MaxCount as there are fewer objects/rows in the table as seen in the following example:

    Database Member 0 -- Database TSMDB1 -- Active -- Up 9 days 13:20:25 --   Date 2015-04-05-13.07.15.309820                                          
                                                                           
    Table Reorg Information:                                                
    Address            TbspaceID TableID PartID MasterTbs MasterTab          
    TableName          Type    IndexID    TempSpaceID                        
    0x07000009D03CE1F8 5         5       n/a    n/a       n/a                
    BACKUP_OBJECTS     Online  4          5                                  
    Table Reorg Stats:                                                    
    Address            TableName          Start               End          
    PhaseStart          MaxPhase   Phase      CurCount   MaxCount   Status
    Completion                                                            
    0x07000009D03CE1F8 BACKUP_OBJECTS     04/04/2015 11:59:39 04/04/2015  
    13:03:16 n/a        n/a        n/a        3105768    17820147   Done   
    0  
This would seem to indicate the reorg is only ~17.43% complete (3105768/17820147) though the status is "Done".

If a Runstats were performed on the table prior to the reorg of the table then the MaxCount would be adjusted to more accurately reflect the number of rows to process.

Note: The Tivoli Storage Manager Server/DB2 automatically runs a Runstats after a table has been reorg'd by the server. This improves efficiency with the table searches.

[{"Product":{"code":"SSGSG7","label":"Tivoli Storage Manager"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Component":"Server","Platform":[{"code":"PF016","label":"Linux"},{"code":"PF025","label":"Platform Independent"},{"code":"PF033","label":"Windows"}],"Version":"All Supported Versions","Edition":"All Editions","Line of Business":{"code":"LOB26","label":"Storage"}}]

Product Synonym

TSM ADSM ITSM Tivoli Storage Manager IBM Spectrum Protect

Document Information

Modified date:
17 June 2018

UID

swg21883018