Recover Plus migrate job issues BMC96348S SOURCE CURRENT VERSION n DOES NOT MATCH TARGET CURRENT VERSION 0. REBUILDS MUST RUN SEPARATELY AFTER REPAIR VERSIONS Input is several (thru DSNUM 60) BMC40611I INPUT STATEMENTS: BMC40101I RECOVER TABLESPACE dbname.tsname DSNUM 1 BMC40101I OBIDXLAT RESET BMC40101I INCOPY FULL DSNAME hlq..icname....P001(0) BMC40101I TOCOPY LASTCOPY Message is issued for all 60 parts BMC96348S SOURCE CURRENT VERSION n DOES NOT MATCH TARGET CURRENT VERSION 0. REBUILDS MUST RUN SEPARATELY AFTER REPAIR VERSIONS BMC40279S ELIMINATING BUILD STEP FOR: BMC40346S INDEXSPACE = index.spacename BMC40305S DSNUM = 1 BMC40970W COPY REQUIRED FOR OBJECT BMC40345W SPACE = dbname.tsname BMC40305W DSNUM = 1 |
The user is migrating the tablespaces from one DB2 to another. The version on the copies (source) is greater than the version on the target system. So a REPAIR VERSIONS needs to be run after the restore to correct the Catalog version. You can do this in 2 ways. 1. Run a separate (IBM) REPAIR VERSIONS step 2. Or you can include the keyword UPDATE VERSIONS with each recover statement. For example: RECOVER TABLESPACE dbname.tsname DSNUM 1 OBIDXLAT RESET INCOPY FULL DSNAME hlq..icname....P001(0) TOCOPY LASTCOPY UPDATE VERSIONS Either way, this will need to be followed by a REBUILD INDEX(ALL) TABLESPACE step to prevent further data errors. |