Concurrency issues

This section explains how BMC AMI Recovery Manager determines the status of Db2 objects and ensures the validity of resources that can be shared during BMC AMI Recovery Manager processing.

BMC AMI Recovery Manager permits optional control of concurrent updates to multiple spaces or partitions and provides a more consistent view of the data in an updated transaction environment. BMC AMI Recovery Manager exercises control by issuing DB2 -STOP, -START, and QUIESCE commands as needed to control access to spaces or partitions. BMC AMI Recovery Manager might also issue these commands at the partition level for table spaces when using the DSNUM option to make copies by partition.

Changes that BMC AMI Recovery Manager might make to the status of a target space or partition during the UTILINIT and UTILTERM phases are discussed and summarized in Db2-commands-issued-by-BMC-AMI-Copy-for-read-and-write-databases.

Related topics

Bypassing-spaces-with-a-bad-status

Retrying-spaces-in-UTxx-status

Db2-commands-issued-by-BMC-AMI-Copy-for-read-and-write-databases

Running-BMC-AMI-Copy-jobs-concurrently

BMC AMI Recovery Manager might also coordinate the status changes required for space or partition access with other concurrently executing BMC utilities. For more details, see Concurrency-with-other-BMC-utilities.

This section contains the following topics:

 

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