Skip to Content

Partitions added during processing

If a partition is dynamically added to a space while BMC AMI Copy is copying the space, a non-SHRLEVEL CHANGE copy might fail if the image copy does not include all of the partitions of the space at the point in time represented by the registration START_RBA.

The registration START_RBA is selected during the UTILINIT phase when you specify the following options together to make copies:

Related topic

Handling-added-partitions

  • SHRLEVEL CONCURRENT, SHRLEVEL REFERENCE, or SHRLEVEL NONE
  • GROUP YES

If a partition is added between the time that the copy is initialized and the time corresponding to the registration START_RBA selected, the image copy would not accurately reflect the space at the time corresponding to the registration START_RBA, and the copy will fail.

The registration START_RBA is selected at the end of the COPY PHASE when you specify the following options to make copies:

  • SHRLEVEL REFERENCE or SHRLEVEL NONE
  • GROUP NO

If BMC AMI Copy detects that a partition was added between the time the copy was initialized and the point in time represented by the START_RBA selected, the copy fails.

A DSNUM integer copy for an existing partition is not affected by an ALTER...ADD PARTITION. A DSNUM integer copy for a partition added during the copy, regardless of the SHRLEVEL and GROUP specification, fails.

If you specify SHRLEVEL CHANGE and partitions are added, BMC AMI Copy copies the partitions existing at copy initialization, and ignores any partition added while the copy is running.

If copy fails due to an ALTER...ADD PARTITION during the copy, BMC AMI Copy issues the following message and ends with a completion code 8:

 BMC160638E   COPY INVALIDATED: PARTITIONED SPACE spaceName DYNAMICALLY
             ALTERED.
             PARTITION ADDED DURING COPY INITIALIZATION.

 

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

BMC AMI Copy for Db2 13.1