Skip to Content
Information
Limited support BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see Recovery Management for Db2 13.1.

Status considerations

For Online Consistent Copy to start a copy of a space or partition, the status of the space or partition must meet certain requirements:

  • The space and database must have a start status of RW, RO, UT, or UTRW.
  • Online Consistent Copy will not run on a space that is in UTUT or UTRO status.
  • The space can be in any of the following statuses:
    • COPY pending (COPY) status
    • REORG pending (REORP) status
Warning

Important

Each partition in a table space can have a different initial status.

If the space is in any status other than those listed, Online Consistent Copy will not run. Online Consistent Copy will not alter the space status.

Warning

Important

BMC AMI Recover can use Instant Snapshot copies made by Online Consistent Copy for normal forward recovery. If you use BMC AMI Copy to perform a COPY IMAGECOPY of the Instant Snapshot copies made by Online Consistent Copy, the IBM RECOVER utility can use the image copies (now registered in SYSCOPY) in normal forward recovery with the following restriction. If the table space uses LOCKSIZE ROW, the IBM RECOVER utility can use the copies only for a TOCOPY recovery. This restriction does not apply to BMC AMI Recover. For more information, see Using-Online-Consistent-Copy-for-recovery .

Copies produced by Online Consistent Copy are also useful for data migration. See Using-Online-Consistent-Copy-for-migration.


Related topic

Concurrency-issues


 

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

Recovery Management for Db2 12.1