Fast Recover for Db2 RECOVER TABLESPACE ... OBIDXLAT execution found an inconsistency with the number of columns between source and target

Products

• Fast Recover for DB2 for z/OS

Issue/Introduction

A Fast Recover for Db2 for z/OS (PFR) RECOVER TABLESPACE ... OBIDXLAT execution found the following inconsistency error messages.

PFR0386E - DATA IS INCONSISTENT WITH THE DEFINITION       
           OF TABLESPACE ...              
           OBJECT TYPES DO NOT MATCH                      
           This Error has Occurred in CSECT - FRA@OBID    
                                                          
PFR0389E - IDENTIFIER    TARGET OBJECT   SOURCE IMAGE COPY
           SSID              DBT1             DB2U        
           DBID              020C             020C        
           OBID              0001             0001        
           PSID              0002             0002        
                                                          
PFR0388E - ATTRIBUTE     TARGET OBJECT   SOURCE IMAGE COPY
           TYPE            SEGMENTED        SEGMENTED
           PAGE SIZE         10               10     
           SEGSIZE           0020             0020   
           TOTAL PARTS       0000             0000   
           ROW FORMAT        BRF              BRF    
           DATASET SIZE        2G               1G   
           # OF COLUMNS      0161             0160   

The DDL between the source and the target was exactly the same with same data set size and number of columns.

Resolution

Problem was the source table was modified to add a column via ALTER TABLE ADD COLUMN and a reorg was pending to be run.

On the source the following was run:

1. ALTER TABLE ADD COLUMN...
2. Created image copy without reorg being executed against tablespace.

The number of columns in the header page of the source tablespace is not updated until a reorg is run so in the header of the image copy there was a value of 0160.

And on the target the following was run:

1. Created table with the added column in original definition of object (No ALTER TABLE ADD COLUMN).
2. RECOVER TABLESPACE ... OBIDXLAT using image copy from source above.

The DDL was correct and in the header page of the target tablespace there was a value of 0161. PFR checked values in the header pages and failed.

A reorg must be run against the source tablespace to update the header page and remove the AREO* status set after the column was added.
Then create the image copy of source tablespace to be used by RECOVER TABLESPACE ... OBIDXLAT in the target environment.