Limited supportBMC 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 Copy for Db2 13.1.

Making incremental index copies

Making incremental copies of indexes has the following benefits:

  • Reduces the need for excessive Db2 log application for an index space recovery
  • Reduces the amount of data that you must copy to disk or tape

Important

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

To request incremental index copies

Request incremental index copies by using one of the following options:

  • The FULL NO, FULL AUTO, or CHANGELIMIT syntax option with COPY INDEXSPACE
  • COPY TABLESPACE with INDEXES YES specified.

The incremental index space copy process parallels the incremental copy process for table spaces, with the following considerations:

  • Incremental index space copies that are produced by BMC AMI Copy are registered in the BMCXCOPY table (Registering-index-copies).
  • Because index spaces lack the ability to identify modified pages, incremental index space copies are always produced using the READTYPE FULLSCAN method.
  • If you specify the INDEXES YES option and copy table spaces with the FULL NO option, BMC AMI Copy also use the FULL NO option for the index copy.
  • Index spaces with the COPY NO attribute do not have log ranges, so they are not checked to qualify FULL AUTO processing.
  • Because COPY YES indexes are skipped when the SYSIBM.SYSLGRNX table shows no update activity has occurred since the START_RBA of the last copy, BMC AMI Copy may skip the copy if the COPY YES attribute was recently changed from COPY NO.
  • When you perform a REORG or REBUILD on an index in a COPY NO index space with an IBM utility, a SYSCOPY record is not stored to identify the activity. Consequently, a full copy registered prior to the disruptive activity is not usable for a recovery-to-current. For the same reason, a FULL NO copy that is based on that full copy is unusable. If you do not use a BMC product to reorganize or rebuild a COPY NO index and you intend to recover the index, rather than rebuild it, you should immediately make a FULL YES copy of the index space.
  • When you use FULL AUTO or CHANGELIMIT to make incremental index copies, the percent of changed pages for each index is the incrPct value from the FULL AUTO or the CHANGELIMIT syntax or the INCRPCT installation option default value plus a value of .01. This applies a bias to a FULL NO copy for index spaces.

  • A request for a FULL AUTO index copy with the EMPTY NO option specified does not result in the following message:

    BMC47312I INCREMENTAL COPY SELECTED DUE TO EMPTY NO.

    Instead, BMC AMI Copy issues the following message:

    BMC47312I INCREMENTAL COPY SELECTED DUE TO ESTIMATED PERCENT
     CHANGED(value) > PERCENT VALUE1 (0.00) AND ZERO IN PERCENT VALUE2
     (BYPASS)

Restrictions on incremental index copies

The following restrictions apply to incremental index copies:

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

Incremental copies of nonpartitioned indexes and recovery

You should use the IXDSNUM=ALL option to make incremental copies for nonpartitioned indexes. Using IXDSNUM=DATASET would require that your BMC AMI Recover statements specify the data set number on the RECOVER statement.

Example

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 integer

or

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


Related topics

Creating-index-backups

Basic installation options

Managing-multiple-image-copies

Registering-copies

 

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