×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')
BMC AMI Recover for Db2 12.1 ... Command and syntax reference RECOVER TABLESPACE, RECOVER INDEX, and RECOVER INDEXSPACE commands RECOVER TABLESPACE, RECOVER INDEX, and RECOVER INDEXSPACE option descriptions

REDEFINE

Use the REDEFINE option to avoid the normal deletion and reallocation of the object data sets for STOGROUP-defined objects. This option is ignored for VCAT-defined object data sets. The value that you specify for REDEFINE applies to all STOGROUP-defined objects included with a single BMC AMI Recover command. To recover multiple STOGROUP-defined objects with some reallocated and others not reallocated, you must use one BMC AMI Recover command statement for the objects to be reallocated and a second BMC AMI Recover command statement for those objects not to be reallocated.

Regardless of the value of REDEFINE, if the data sets for a STOGROUP-defined object do not exist, BMC AMI Recover creates the VSAM data sets.

Important

When a point-in-time recovery of a multi-data-set, nonpartitioned object is performed, more or fewer data sets may result than were previously used. If data sets were added after the point-in-time recovery point, there are fewer data sets after the point-in-time recovery. If the object was reorganized after the point-in-time recovery point, there may be more data sets.

REDEFINE YES

REDEFINE YES is the default. If you specify REDEFINE YES, BMC AMI Recover deletes and reallocates the VSAM data sets for STOGROUP-defined objects prior to the recovery. For more information, see Storage group-defined data sets.

NOSCRATCH

If you specify NOSCRATCH with REDEFINE YES, BMC AMI Recover invokes IDCAMS to uncatalog without scratching. You can use NOSCRATCH to support disaster recovery scenarios where the following conditions are true:

  • DASD volumes at the recovery site differ from those at the primary site.

  • The operating system catalog and the DB2 catalog and directory are restored before running BMC AMI Recover.

  • DB2 STOGROUPS are changed to point to the recovery site packs.

Using this option eliminates mount messages for the primary site packs that do not exist at the recovery site.

Important

REDEFINE YES has no effect if you specify INDEP OUTSPACE. For the instructions for creating data sets for INDEP OUTSPACE, see INDEPENDENT OUTSPACE specification. If an Instant Snapshot copy is used to recover the object, REDEFINE YES has no effect and the data sets are processed as if REDEFINE NO had been specified.

REDEFINE NO

REDEFINE NO tells BMC AMI Recover not to delete and reallocate the VSAM data sets for the object. This option enables you to treat STOGROUP-defined objects as VCAT-defined objects and to reallocate the VSAM data sets manually, or use the data sets already assigned to the object. New volumes are used as needed from the STOGROUP, even with REDEFINE NO specified.

Important

With REDEFINE NO specified, when recovery of a multi-data-set, nonpartitioned object is performed as DSNUM ALL, any necessary additional data sets are created and unused data sets are deleted.

When you specify REDEFINE NO, BMC AMI Recover does not free unused extents in a retained data set. If you want the recovery to free unused extents, specify REDEFINE YES, which is the default.

Related topic

RECOVER TABLESPACE, RECOVER INDEX, and RECOVER INDEXSPACE option descriptions

Was this page helpful? Yes No Submitting... Thank you
Last modified by Anagha Evans on Sep 30, 2021
command_reference syntax

Comments

Log in or register to comment.

RECOVERYSITE
REUSE
© Copyright 1994-2024 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.