Skip to Content

Single index specification

Related topics

RECOVER TABLESPACE, RECOVER INDEX, and RECOVER INDEXSPACE option descriptions

Example 5: Recovering to a specific log point

Example 17: Using timestamp recovery

For option descriptions for the OBIDXLAT, Non-Registered Copy, FROMRBA, and OUTCOPY specifications, which are included in the Single index specification, see:

The syntax diagram for the Single index specification is in RECOVER TABLESPACE, RECOVER INDEX, and RECOVER INDEXSPACE syntax.

Warning

Important

If INDEXLOG=NO is specified as an installation option or on the OPTION command, single index specifications are not valid on the same RECOVER statement with TABLESPACE. Without TABLESPACE, the parser understands that REBUILD is implied.

INDEX creatorID.indexName

The INDEX option specifies the index to be recovered.

  • creatorID is the qualifier creator ID for the index. The default is the user identifier for the utility.
  • indexName is the name of the index. Indexes for BMCUTIL, BMCSYNC, and BMCXCOPY (tables that are used by BMC utilities) cannot be used.

OBJECTSET specification

Use the OBJECTSET specification with INDEX to recover only the indexes that are in a defined group. For more information, see OBJECTSET specification and Using BMC AMI Recovery Manager object sets.

INDEXSPACE databaseName.indexSpaceName

The INDEXSPACE option specifies the index space to be recovered.

  • databaseName is the name of the database containing the index space. The default is DSNDB04. The name cannot be DSNDB01, DSNDB06, DSNDB07, or any database defined with TYPE='W' in SYSIBM.SYSDATABASE.
  • indexSpaceName is the name of the index space within the named database. Indexes for BMCUTIL, BMCSYNC, and BMCXCOPY (tables that are used by BMC utilities) cannot be used.

DSNUM

DSNUM specifies either a single data set for the specified index or the entire index for recovery.

Warning

Important

If you code INDEXLOG=NO in the installation options or on the OPTION command, RECOVER INDEX is analogous to REBUILD INDEX and you should use PART (PART) rather than DSNUM. Otherwise, BMC AMI Recover ends, issues BMC40442 and BMC40443, and requests validation of the options.

DSNUM ALL

DSNUM ALL is the default and specifies that all of the data sets for the index are to be recovered.

If the index is nonpartitioned and DSNUM ALL is specified or implied, only image copies made for the entire index (those registered with DSNUM 0) are used for recovery, with the following exception: If DSNUM ALL is specified and BMC AMI Recover detects that one or more DSNUM n copies are registered for an index at the same RBA, BMC AMI Recover expands the request from DSNUM ALL to DSNUM n, (where n is the number of image copies registered together) and issues an informational message.

For multi-data-set, nonpartitioned index spaces, if the index copy used for recovery is a DSN1COPY, DSNUM ALL is not allowed.

DSNUM integer

Use this option to recover only one partition or data set for an index. For partitioned indexes, DSNUM integer specifies the number (from 1 through 4096) of a single partition of the specified index. For nonpartitioned indexes, DSNUM integer specifies the number (from 1 to 4096) of a single data set for the specified index.

DSNUM begin : end

Use this option to recover a range of partitions in the table space. For partitioned table spaces, begin specifies the number (from 1 through 4095) of the first partition in the range and the end specifies the number (from 2 through 4096) of the last partition in the range. The two numbers are separated by a colon (:) with or without spaces. Wrapping partition numbers (for example, DSNUM 4050 : 300) is not supported.

NOWORKDDN

The NOWORKDDN option causes the keys to be sent directly to the sort routine without first writing these keys to a work data set. With RECOVER INDEX, NOWORKDDN is only valid when you have also specified INDEXLOG AUTO.

 

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

BMC AMI Recover for Db2 13.1