Recovering a partitioned table space and rebuilding a nonpartitioned index
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 may run in less time than running one job to read all of the partitions. Contention for archive log tapes may cause jobs to wait.
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 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.
Comments
Log in or register to comment.