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 Recover for Db2 13.1.

Limitations

BMC AMI Recover

 does not support the following items:

  • IBM Db2 Version 10 or earlier
  • IBM Db2 Version 10 running in compatibility mode or enabling new-function mode
  • Recovery of catalog or directory spaces
  • Recovery by using the ERROR RANGE and PAGE options (however, BMC AMI Recover removes an existing error range after a successful table space or index recovery)
  • Setting the check pending flag on a space recovered to a point in time prior to the definition of a column constraint

  • Recovery of the Db2 objects that are used by BMC AMI Recover:

    • xxxxxx.CMN_BMCUTIL
    • xxxxxx.CMN_BMCSYNC
    • xxxxxx.CMN_BMCXCOPY
    • xxxxxx.CMN_BMCHIST

    xxxxxx is the creator name or ID.

  • Index logical partition recovery
  • Setting check pending flags for related spaces that are not recovered

  • Use of an inline copy that has been merged with subsequent incremental copies

    The product tries to detect this condition by examining rows in SYSIBM.SYSCOPY indicating that an inline image copy is registered at the same START_RBA as a previous incremental copy. However, if those entries have been removed by the Db2 MODIFY utility or the BMC AMI Copy MODIFY command, other errors may occur.

  • REBUILD INDEX command if all of the following conditions are true:
    • A table is altered to add a column with the ROWID attribute.
    • An index is created with this new column.
    • A REORG is not performed.

  • Use of the second copy of archive logs, as directed by the DSNZPARM ARC2FRST parameter

    Important

    The same facility is provided with the RESOURCE SELECTION LOGS option of BMC AMI Recover.

  • Tracker sites
  • LISTDEF processing
  • Inline statistics for REBUILD

  • Same order of use for volumes from multivolume STOGROUP-defined spaces as IBM Db2 RECOVER

    BMC AMI Recover might use volumes from multivolume STOGROUP-defined spaces in a different order than IBM Db2 RECOVER. You can control the order with the STOGROUP...USEORDER option.

Consider the following restrictions when working with BMC AMI Recover and Db2:

  • BMC AMI Recover calls DSNUTILB for the following Db2 features:

    • Indexes defined using an expression

      DSNUTILB handles some rebuild requests for indexes defined using an expression and some natively, including, SUBSTR, UPPER, LOWER, DAY, MONTH, and YEAR; BMC AMI Recover handles recover requests.

    • Indexes with RANDOM-order columns

      DSNUTILB handles rebuild requests for indexes with RANDOM-order columns; BMC AMI Recover handles recover requests.

    • Indexes with DECFLOAT columns

      DSNUTILB handles rebuild requests for indexes with DECFLOAT columns; BMC AMI Recover handles recover requests.

  • BMC AMI Recover versions earlier than 11.1.00 will not work with Db2 Version 11.
  • BMC AMI Recover versions earlier than 12.1.00 will not work with Db2 Version 12.

  • If you recover an object to a point in time using DSNUTILB, you need to use DSNUTILB for subsequent recoveries of this object. You can recover this object using BMC AMI Recover after you perform one of the following actions:

    • Make an image copy
    • Use REORG LOG YES
    • Use LOAD REPLACE LOG YES

    Important

    Do not use BMC AMI Recover to back out over a range that includes an IBM backout recovery. Do not use IBM Db2 RECOVER to recover over a range that includes an BMC AMI Recover backout.

Related topic

Key-concepts



 

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