Skip to Content
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.

Responding to unsatisfactory object status

An object must have a status of OK for 

BMC AMI Recovery Manager

 to include it in recovery JCL. For backup JCL, objects with certain non-OK statuses are included in addition to those with an OK status.

For information about object statuses, see BMC-AMI-Recovery-Manager-object-exception-status.

Processing object lists

After you have displayed a list of objects to be included in the object set, you can replace it with a new list, merge it with another list, or exclude one or more objects from the list.

Warning

Important

When you start the build by using a table space wildcard pattern or name, you can specify individual partitions or data sets. (This does not apply when you build your object set with table names or patterns.) However, when you start with an index pattern, you can specify only individual partitions.

You can also request the following during object list generation:

  • Partition expansion

    A partitioned object can be expanded into its constituent partitions. This technique is useful if you are planning to:

    • Selectively back up or recover partitions
    • Perform a recovery using IBM Db2 RECOVER and the existing image copies were made by partition

  • Index inclusion

    Any indexes on the table spaces in the list can be included in the list. If you are building an object set primarily for recovering to the current time, indexes are usually not an issue. However, if you are building an object set for a recovery to a prior point and indexes were not included, the indexes may not be synchronized with the data when the space is recovered. You have two opportunities to include indexes--during list generation and again at recover time if point-in-time recovery is selected.

    Error
    Warning

    Do not choose this option if you are using INDEX ALL when generating recovery JCL (for more information, see General-recovery-options).

  • RI inclusion

    Objects that are related by referential integrity can be included in the list during list generation. If you are building an object set primarily for recovering to the current time, referential integrity is usually not an issue. However, if you are building an object set for a recovery to a prior point and objects related by referential integrity were not included, the entire RI set may not be in a consistent state after a recovery.

  • LOB Inclusion

    Any objects related by LOB structure to an object in the list can be included in the list during list generation. Because of their unique structure, LOB-related objects must always be recovered to the same point.

  • XML Inclusion

    Any objects related by XML structure to an object in the list can be included in the list during list generation. Because of their unique structure, XML-related objects must always be recovered to the same point.

  • History (Versioning) Inclusion

    Any objects related by a history (versioning) relationship to an object in the list can be included in the list during list generation.

Related topics

Validating-the-objects-in-an-object-set

Validating-and-revalidating-application-object-sets



 

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

BMC AMI Recovery Manager for Db2 12.1