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.

Escalation due to prohibition by COPY-pending status

If the target space is in COPY-pending status (and the installation option ESCALATE=YES), 

BMC AMI Copy

 escalates a FULL NO, FULL AUTO, or CHANGELIMIT request to a full request.

BMC AMI Copy will escalate to full copies in the following situations:

  • When no backups exist after you have run the DB2 MODIFY utility.
  • If the table space is currently unrecoverable because you ran a LOAD or REORG utility with LOG NO specified. Even if you turn off the COPY-pending status indicator, which these utilities turn on, BMC AMI Copy detects the situation by examining the SYSIBM.SYSCOPY rows.
  • After you have executed a CHECK DATA utility with the LOG NO option. You must run a full image copy because this utility does not set the modified-page indicators when you specify LOG NO. BMC AMI Copy cannot determine which pages have actually changed, so it cannot produce a valid incremental copy.

BMC AMI Copy issues messages and return codes as shown in Escalating-incremental-copies-to-full-copies in these COPY-pending cases. The same table also shows how BMC AMI Copy processes an incremental request of this type when the installation option ESCALATE=NO.

Related topic

Escalating-incremental-copies-to-full-copies

 

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