Expanded recovery capabilities

BMC AMI Recover provides expanded recovery capabilities that enable you to recover from a dropped table space, create image copies without reading the table space or index space, and migrate data to other Db2 systems. With BMC AMI Recover, you can perform object ID translation, use unregistered input copies, and run recovery without SYSLGRNX entries.

Object ID translation

You can use the BMC AMI Recover OBIDXLAT option to translate internal Db2 object IDs (OBIDs) while processing. This feature supports the BMC AMI Recover drop recovery function to allow recovery of dropped table spaces and allows translation during data migration. Improved migration checking when the INCOPY option is used detects incompatible migrations. Some examples of incompatible migrations are:

Migration of a partitioned table space into a nonpartitioned table space
Migration into a table space with a different page size
Migration of a segmented table space into a table space with a different segment size

BMC AMI Recover translates OBIDs and resets log point values in the pages, but in all other respects, the internal structure of the source, target table spaces, and indexes must be the same.

When you use Instant Snapshots for migration and specify the OBIDXLAT option, BMC AMI Recover automatically detects if the OBIDs have not changed and avoids the overhead of reading and writing all of the pages.

For more information about the drop recovery function, see Recovering-a-dropped-table-space-or-table.

With the Copy Migration feature of the Recovery Management for Db2 solution, BMC AMI Recover will obtain the object ID values from a migration file and either the source or target catalog, simplifying the migration process. For more information, see Recovery Management for Db2 documentation.

Optional use of non-registered input copies

The INCOPY option allows you to specify the following types of copies as input:

Copies that have been dropped from SYSIBM.SYSCOPY
Copies made with DSN1COPY
Instant Snapshot copies that are not registered in BMCXCOPY
Copies that were made on another subsystem (or data sharing group)

Using non-registered input copies supports the following important functions of BMC AMI Recover:

Migration of data
Recovery of dropped table spaces

With the Copy Migration feature of the Recovery Management for Db2, BMC AMI Recover will obtain the input image copy name from a migration file or the source catalog, simplifying the migration process. For more information, see Recovery Management for Db2 documentation.

Optional use of non-registered table space reset events

Certain events that are recorded in SYSCOPY allow recovery of table spaces to be performed solely from the log. These events include LOAD LOG YES with REPLACE or REORG LOG YES. If these events no longer exist in SYSCOPY because of a table space being dropped or modified, the INLOG RBA/INLOG LOGPOINT option can be used to specify the starting point of a log-only recovery. The table space will be reset, and the log will be used to rebuild the table space. This feature does not apply to indexes.

Running without SYSLGRNX records

The NOSYSLGRNG option allows BMC AMI Recover to scan the log without referencing the Db2 SYSLGRNX table when processing a table space. The log is scanned from the beginning log point, such as the log point of the last copy, to TORBA/TOLOGPOINT or current. For indexes with the COPY NO attribute, index log records are always read without referencing the SYSLGRNX table.

This feature supports the BMC AMI Recover drop recovery function. This feature is also useful if you have a damaged SYSLGRNX table.

OUTCOPY ONLY

You can use the OUTCOPY ONLY option to build image copies without reading the table or index space or interfering with Db2 update access in any way. This feature allows you to avoid DASD contention and supports data migration.