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 limiting the number of incremental copies

Escalation due to limiting the number of incremental copies is controlled by the MAXINCRS syntax option (or the MAXINCRS installation option) and the use of the FULL AUTO or CHANGELIMIT option.

Escalation occurs when you have reached the number of incremental copies specified by MAXINCRS and you request a new incremental copy. The setting of the ESCALATE installation option has no effect on this feature.

Important

For the purpose of counting incremental copies, merged FULL NO CUMULATIVE YES RESETMOD NO copies count as one copy only.

Recovery considerations determine the number of incremental copies that should be made between full copies. The number that exist at recovery time affects the length of the recovery since all incremental copies must be merged with the last full copy.

If the incremental copies are on tape, IBM Db2 RECOVER uses only the first n copies, where n is the number of tape drives available; IBM Db2 RECOVER ignores other incremental copies.

The default for MAXINCRS is the value of the installation option. The installation default is 6, which can provide, for example, one full copy per week and a maximum of 6 incremental copies for daily runs.

When escalation occurs due to this condition, BMC AMI Copy issues message BMC47312 and return code 0.

Related topics

Escalating-incremental-copies-to-full-copies

Global-COPY-options

 

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