Recovering a table space and rebuilding a partitioned index and a nonpartitioned index
After running these concurrent jobs, you can build the nonpartitioned index. The following combination of RECOVER TABLESPACE, REBUILD INDEX, and RECOVER UNLOADKEYS command statements illustrates this method:
Run jobs 1 and 2 concurrently.
RECOVER TABLESPACE X.Y DSNUM 1 REBUILD INDEX (X.YCLUS) PART 1 RECOVER UNLOADKEYS (X.YNCLUS) PART 1
RECOVER TABLESPACE X.Y DSNUM 2 REBUILD INDEX (X.YCLUS) PART 2 RECOVER UNLOADKEYS (X.YNCLUS) PART 2
When jobs 1 and 2 are complete, run job 3.
RECOVER BUILDINDEX (X.YNCLUS)
Because NGT Recover reads all of the contents of SYSIN before deciding on a recovery plan, the utility can process the RECOVER TABLESPACE, REBUILD INDEX, and RECOVER UNLOADKEYS command statements for each run as a single unit.
When you run a RECOVER BUILDINDEX job, ensure that no updates or other changes have been made to the table space since the keys were extracted. Otherwise, the integrity of the data cannot be guaranteed. For a discussion, see Concurrency with RECOVER UNLOADKEYS and RECOVER BUILDINDEX.