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 BMC AMI Recover for Db2 13.1.

Using incremental index image copies

Using incremental copies of indexes made by 

BMC AMI Copy

 in recovery has the following benefits:

  • Reduces the need for excessive Db2 log application for an index space recovery
  • Reduces the amount of data that must be copied to disk or tape in order to maintain current copies
  • Reduces the volume of image copy data to manage
  • Improves recovery times compared to rebuilding indexes or to using only full index image copies
Warning

Important

To use the incremental index copies made with BMC AMI Copy, the same version of BMC AMI Recover is required. If you attempt a recovery using incremental index copies and earlier versions of BMC AMI Recover, unpredictable results can occur.

BMC AMI Recover recognizes incremental copies of indexes recorded in BMCXCOPY, includes them in BMC AMI Recover analysis and planning, shows them in the BMC AMI Recover object summary, and uses them whenever appropriate to speed up recovery of indexes.

When you use incremental index copies for recovery, note the following considerations:

  • Incremental index space copies that are produced by BMC AMI Copy are registered in the BMCXCOPY table.
  • Because index spaces lack the ability to identify modified pages, incremental index space copies are always produced using the READTYPE FULLSCAN method.
  • Because index spaces lack the ability to identify modified pages, the RESETMOD option for copies does not apply. All index copies are RESETMOD NO.
  • BMC AMI Recover processing for cumulative incremental image copies applies to incremental index copies. For more information, see Recovery-using-cumulative-incremental-image-copies.

Restrictions on incremental index copies

The following restrictions apply to incremental index copies:

  • You cannot use DSNUM n incremental copies of nonpartitioned indexes in a DSNUM ALL recovery.
  • BMC AMI Copy and BMC AMI Recover do not support incremental index copies of catalog and directory.

Incremental copies of nonpartitioned indexes and recovery

When you make incremental copies for nonpartitioned indexes, you should make these copies using the BMC AMI Copy IXDSNUM=ALL option.

If you make the copies using the BMC AMI Copy IXDSNUM=DATASET option, your BMC AMI Recover statements must specify the data set number on the RECOVER statement.

If you copy a nonpartitioned index with IXDSNUM=ALL, examples of your BMC AMI Recover syntax are:

RECOVER INDEX IX.A

or

RECOVER INDEX IX.A DSNUM ALL

If you copy a nonpartitioned index with IXDSNUM=DATASET, examples of your BMC AMI Recover syntax are:

RECOVER INDEX IX.A DSNUM n

or

 RECOVER INDEX IX.A DSNUM n:n(more than one data set to be recovered)

For more information about IXDSUM option, seeBMC AMI Copy for Db2 documentation.

 

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

BMC AMI Recover for Db2 12.1