Validation sequence for renaming chunks

During a cold restore, ontape performs the following validations to rename chunks:
  • It validates that the old chunk path names and offsets exist in the archive reserved pages.
  • It validates that the new chunk path names and offsets do not overlap each other or existing chunks.
  • If renaming the primary root or mirror root chunk, it updates the onconfig file parameters ROOTPATH and ROOTOFFSET, or MIRRORPATH, and MIRROROFFSET. The old version of the onconfig file is saved as $ONCONFIG.localtime.
  • It restores the data from the old chunks to the new chunks (if the new chunks exist).
  • It writes the rename information for each chunk to the online log.
If either of the validation steps fails, the renaming process stops and ontape writes an error message to the ontape activity log.
Important:
  • Perform a level-0 archive after you rename chunks; otherwise your next restore fails.
  • If you add a chunk after performing a level-0 archive, that chunk cannot be renamed during a restore. Also, you cannot safely specify that chunk as a new path in the mapping list.
  • Renaming chunks for database servers participating in HDR involves a significant amount of offline time for both database servers. For more information, see the HCL OneDB™ Administrator's Guide.