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.

Cleaning up the BMCUTIL and BMCSYNC tables

If an 

BMC AMI Copy

 job fails and you do not plan to restart it, you must clean up the BMCUTIL and BMCSYNC tables and reset the space status before running any more BMC utilities against the space.

We recommend that you specify TERM/RESET for the restart parameter in the EXEC statement in the BMC AMI Copy JCL and submit the job for execution. For more information, see Utility-parameters-on-the-EXEC-statement.

For copy jobs, if the original job failed in the COPY phase with the FULL YES and RESETMOD YES options specified for table spaces, BMC AMI Copy also does the following things:

  • Puts a T entry in the ICTYPE column of SYSIBM.SYSCOPY to prohibit incremental copying until a full copy is successfully made.

  • For special case table spaces, BMC AMI Copy issues a Db2 -TERM UTILITY command.

    Important

    Specifying TERM/RESET will also terminate XBM caching for restartable Snapshot Copies.

Subject to the warnings that follow, you can also clean up the BMCUTIL and BMCSYNC tables with Catalog Manager. If you have installed Catalog Manager version 3.4, fix lib 3606 or above, you can issue the BMCUTIL TERM command from Catalog Manager. For more information, see BMC AMI Catalog Manager for Db2 documentation.

Warning

Be aware of the following situations:

  • If BMC AMI Copy changed the space status, you must manually reset it with the Db2 -START command.
  • If a copy job was terminated in the COPY phase and it was specified using FULL YES and RESETMOD YES for table spaces, page-modification indicators might be partially reset. The next copy must be specified using FULL YES before making any more incremental copies, since an incremental copy could not identify all changed pages.
  • To terminate and cleanup following a failed Snapshot Copy (an XBM supported copy), run BMC AMI Copy with the TERM/RESET option (Restart parameter (restartParm)).
  • If the space was in COPY-pending status, BMC AMI Copy might have reset the status, so make a copy before updates.
  • XBM caching for restartable Snapshot Copies will not be terminated. You must terminate the caching through XBM. For restartable Snapshot Copies, you must be using XBM version 3.0 or later.


Related topics

Building-and-running-BMC-AMI-Copy-jobs

Terminating-a-BMC-AMI-Copy-job-during-execution


 

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