Information
Limited support BMC 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 Recovery Manager for Db2 13.1.

Validating and revalidating application object sets


After you have created an object set, all objects are validated for their availability to Db2 and their eligibility for recovery.

If BMC AMI Recovery Manager encounters a problem with an object, an appropriate status is returned for that object. These unsatisfactory statuses are handled differently in a recovery situation or in a backup situation. See Responding-to-unsatisfactory-object-status for more information.

After initial validation is complete, you can save the object set to the repository and then periodically revalidate it to determine whether any changes that affect the recoverability of the object set (as it was initially defined) have taken place. If changes have occurred, they are reported and can be implemented automatically.

Warning

Important

With the introduction of dynamic object sets in BMC AMI Recovery Manager version 9.2.00, revalidation no longer refers to the process of running the object set definitions again to populate the object set with an updated list of objects based on the current system. This type of revalidation is no longer needed with dynamic object sets. Revalidation now refers to checking the recoverability of the objects in the object set.

BMC AMI Recovery Manager does not revalidate catalog and directory resources.

Whenever a recovery point is selected, the objects are also validated for recoverability to that point.

Revalidation can be performed online or in batch.


 

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

BMC AMI Recovery Manager for Db2 12.1