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.

Keeping and recalling merged incremental copies

When you routinely merge incremental copies, you improve the efficiency of a recovery to the current time.

BMC AMI Copy provides the KEEP option when you use FULL NO to make an incremental copy request. This option allows you to specify whether to retain the entry in SYSIBM.SYSCOPY in the event that the most recent prior incremental copy was made with the RESETMOD NO option. When you choose to keep an incremental copy that is being merged, the SYSIBM.SYSCOPY entry is uniquely marked with ICTYPE=i to prevent that copy from being used in a normal recovery.

Important

KEEP is valid only when CUMULATIVE YES (the default) is in effect.

If you want to perform a point-in-time recovery that requires a particular merged incremental copy, the BMC AMI Recover utility will detect and use the retained incremental copy. If you use IBM Db2 RECOVER to perform a point-in-time recovery that requires a 'kept' incremental copy, you must reinstate that copy using the BMC AMI Copy RECALL command before you can proceed with the recovery.

The RECALL command has the following syntax:

    RECALL COPY TABLESPACE [databaseName.]tableSpaceName     
  [DSNUM {ALL/integer}]     
  ATRBA X'byteString'/ATLOGPOINT X'byteString'

In this example:

  • databaseName defaults to DSNDB04.
  • DSNUM defaults to DSNUM ALL.
  • ATRBA or ATLOGPOINT specify the value contained in the START_RBA column of SYSCOPY for the incremental copy you want to reinstate. This value may be an RBA or LRSN depending on whether the copy was made in a non-data-sharing or a data sharing environment respectively.

BMC AMI Copy reinstates any local or remote primary or backup copies with the same START_RBA value.

After you recall an incremental copy, IBM Db2 RECOVER can use the copy in the normal way.

Because the rows for retained copies are left in SYSIBM.SYSCOPY, they are displayed by any tool or report that displays SYSCOPY information. Also, the BMC C+/MODIFY component of BMC AMI Copy or IBM Db2 MODIFY can clean up these rows in the same way as any other rows in SYSCOPY.

For more information about the KEEP option and the RECALL command, respectively, see Global-COPY-options and RECALL-command.

Related topics

Managing-table-space-incremental-image-copies

RESETMOD

 

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