Recovering a partitioned table space and rebuilding a nonpartitioned index

If you need to recover a partitioned table space and a nonpartitioned index, you can combine RECOVER TABLESPACE and RECOVER UNLOADKEYS command statements.

As shown in the following figure, you can set up multiple jobs to do the processing on the individual partitions followed by a RECOVER BUILDINDEX job to build the nonpartitioned indexes. If your system has enough resources, these jobs can extract the keys from several partitions concurrently and might run in less time than running one job to read all of the partitions. Contention for archive log tapes might cause jobs to wait.

Related topic

Recovering-partitioned-table-spaces-and-indexes

GUID-B0833D37-4044-4382-9845-8E88F01E5660-low.png

When you run a RECOVER BUILDINDEX job, the JCL must include all of the data sets containing the extracted keys, and use a separate SKEYnn ddname for the file from each UNLOADKEYS job step.

Important

When you run a RECOVER BUILDINDEX job, ensure that no updates or other changes have been made to the table space because the keys were extracted. Otherwise, the integrity of the data cannot be guaranteed. For a discussion, see Concurrency with RECOVER UNLOADKEYS and RECOVER BUILDINDEX.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*