Table space specification

For option descriptions for specifications which are included in the table space specification, see:

The syntax diagram for the table space specification is in RECOVER TABLESPACE, RECOVER INDEX, and RECOVER INDEXSPACE syntax.

TABLESPACE databaseName.tableSpaceName

The TABLESPACE option specifies the table space to be recovered.

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

OBJECTSET specification

Use the OBJECTSET specification with TABLESPACE to recover only the table spaces that are in a defined group.

For more information, see OBJECTSET specification and Using BMC AMI Recovery Manager groups.

Important

To include the indexes in a recovery using TABLESPACE OBJECTSET, specify INDEXES YES.

INDEXES

The INDEXES option allows you to specify that you want BMC AMI Recover to recover the indexes associated with the table space(s) given by the TABLESPACE option of the RECOVER command. The default is INDEXES NO indicating no indexes recovery.

Important

The use of INDEX is synonymous to INDEXES for this option.

The INDEXES option is not applicable to INDEXSPACE or INDEX specifications.

INDEXES NO	Specifying INDEXES NO tells BMC AMI Recover to not recover the indexes for the specified table space or table spaces.
INDEXES YES	Specifying INDEXES YES tells BMC AMI Recover to recover all indexes associated with the table space(s) specified by the TABLESPACE. Important INDEXES YES is invalid with an unqualified OBJECTSET specification (OBJECTSET without TABLESPACE).

DSNUM

DSNUM specifies a single data set in the specified table space or the entire table space for recovery.

DSNUM ALL	DSNUM ALL is the default and specifies that all of the data sets in the table space are to be recovered. If the table space is nonpartitioned and DSNUM ALL is specified or implied, image copies made for specific data sets will only be considered for recovery if they are registered at the same log point.
DSNUM integer	Use this option to recover only one partition or data set in the table space. For partitioned table spaces, DSNUM integer specifies the number (from 1 through 4096) of a single partition in the specified table space. For nonpartitioned table spaces, DSNUM integer specifies the number (from 1 to 32) of a single data set of the specified table space.
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 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.

AUX

The AUX option specifies if auxiliary objects will be included with the recovery of the base table spaces. For more information, see AUX.

RICHK

RICHK specifies if BMC AMI Recover will check for referential integrity constraints on the objects being recovered.

RICHK YES	RICHK YES checks for referential integrity constraints and sets check pending (CHKP) status for dependent objects not recovered in the same step to the same PIT.
RICHK NO	RICHK NO does not check for referential integrity. NO is the default value.

DROPRECOVERY

DROPRECOVERY specifies that you want to recover a dropped table space. The DROPRECOVERY keyword requires either INCOPY, INLOG, LOGONLY, or LOGAPPLY ONLY. When DROPRECOVERY is coded, the utility attempts to locate the point at which the table space was re-created and uses that point as a stopping point or verifies it against the TORBA or TOLOGPOINT value. If the space was dropped and re-created several times, you must specify a TORBA or TOLOGPOINT value in the BMC AMI Recover job to tell BMC AMI Recover when to stop applying log records. Use DSN1LOGP to identify the log point of the first CREATE TABLESPACE statement after the drop. This is the log point that you should specify with the TORBA or TOLOGPOINT option. If you do not specify a TORBA or TOLOGPOINT value in this case, the recovery will result in an empty table space.

If the dropped space was versioned, you must recreate the space with the same versions, or in some cases, you can use DB2 REPAIR VERSIONS.

If the dropped space has been reorganized after the first alter, you can recreate the space to match the latest version of the space, recover the space, and then run DB2 REPAIR VERSIONS. You cannot rebuild indexes until after you run DB2 REPAIR VERSIONS.
If the dropped space has not been reorganized, you must recreate the space as it existed originally, before any alters, perform the alters to create the same versions that the dropped space had, and then recover the space.

Warning

Use DROPRECOVERY only if the table space has been dropped (not just a table within the table space).

Important

DROPRECOVERY is not valid for index recovery.

For examples on how to use DROPRECOVERY, see Recovering a dropped table space or table.

Example 6: Extracting nonpartitioned index keys

Example 5: Recovering to a specific log point

Example 17: Using timestamp recovery

Example 14: Simulating recovery

Examples of BMC AMI Recover jobs

NOSYSLGRNG

Table space specification

TABLESPACE databaseName.tableSpaceName

Comments