Space announcement


This space provides the same content as before, but the organization of the home page has changed. The content is now organized based on logical branches instead of legacy book titles. We hope that the new structure will help you quickly find the content that you need.


NGT 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, NGT 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 NGT 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 NGT 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


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

  • Tracker sites

  • LISTDEF processing

  • Inline statistics for REBUILD

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

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

Consider the following restrictions when working with NGT Recover and DB2:

  • NGT 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; NGT Recover handles recover requests.

    • Indexes with RANDOM-order columns

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

    • (PTF BQU2277 applied) Indexes with DECFLOAT columns 

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

  • NGT Recover versions earlier than 11.1.00 will not work with DB2 Version 11.

  • NGT 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 NGT Recover after you perform one of the following actions:

    • Make an image copy




    Do not use NGT Recover to back out over a range that includes an IBM backout recovery. Do not use IBM recover to recover over a range that includes an NGT Recover backout.

Related topic

Was this page helpful? Yes No Submitting... Thank you