Skip to Content
Information
Space announcement This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.

Renaming consistent copies to migrate objects

This scenario describes how to rename consistent copies to migrate objects. This scenario assumes that the following points are true:

  • The objects on the target subsystem have the same structure and internal identifiers (DBID, PSID, OBID, ISOBID) as the objects on the source subsystem.
  • You do not plan to do updates on the target objects.
  • The subsystems have shared DASD.

Related topic

Using-Online-Consistent-Copy-for-migration

To rename consistent copies

  1. Use Online Consistent Copy to make consistent copies Instant Snapshots of the source objects.This process has practically no effect on the source objects, so you can do it at any time of the day. If the consistent copies are Instant Snapshots (hardware copies), it takes only a few seconds to make each Instant Snapshot, regardless of the size of the space being copied.
  2. Stop the objects on the target subsystem.
  3. Rename or delete the existing data sets for the spaces on the target subsystem.
  4. Rename the consistent copy Instant Snapshot data sets to match the naming convention for the target subsystem.
  5. Start the objects on the target subsystem.The data is now available on the target subsystem.

 

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

Recovery Management for Db2 13.1