Fast Recover OBIDXLAT recovery returns PFR0382E / PFR0388E messages for Partition By Growth tablespace indicating partition mismatch
search cancel

Fast Recover OBIDXLAT recovery returns PFR0382E / PFR0388E messages for Partition By Growth tablespace indicating partition mismatch

book

Article ID: 8035

calendar_today

Updated On:

Products

Fast Recover for DB2 for z/OS

Issue/Introduction

Fast Recover for Db2 for z/OS (PFR) OBIDXLAT recovery fails with below error messages
against a Partition By Growth tablespace:

 

PFR0382E - DATA IS INCONSISTENT WITH THE DEFINITION
OF TABLESPACE 'dbname.tsname'
TOTAL NUMBER OF PARTITIONS DO NOT MATCH
This Error has Occurred in CSECT - FRA@OBID

 

PFR0388E - ATTRIBUTE     TARGET OBJECT   SOURCE IMAGE COPY 
           TYPE            UTS - PBG        UTS - PBG      
           PAGE SIZE         04               04           
           SEGSIZE           0020             0020         
           TOTAL PARTS       0001             0002         
           ROW FORMAT        RRF              RRF          
           DATASET SIZE        4G               4G         
           # OF COLUMNS      0014             0014         
           RBA FORMAT       EXTENDED         EXTENDED 

 

The target definition was cloned from the source object.

 

Resolution

PFR does perform some basic integrity checks between the source and target objects.

The OBIDXLAT type of recovery is very sensitive to the source and target definitions being identical
to ensure a successful recovery or unpredictable results may occur.

 

Based on the PFR0388E message:

SOURCE IMAGE COPY - TOTAL PARTS 0002
TARGET OBJECT - TOTAL PARTS 0001

 

This is a Partition By Growth tablespace where it appears the source tablespace has extended to a
second partition but the target definition appears to be in a single partition.

 

For this specific scenario suggest the following to resolve the problem:

1. Utilize ALTER TABLE ADD PARTITION on the target table to add a partition to match the source object:

ALTER TABLE creator.tablename ADD PARTITION;

The above recommendation appears to be the easiest to implement.

 

or

 

2. Drop and recreate the target object using NUMPARTS 2 to instantiate the 2 partitions on the target object.