OBJECTSET specification

The OBJECTSET option is available in RECOVER statement syntax to recover groups that are defined using BMC AMI Recovery Manager.

The OBJECTSET specification is shown in RECOVER-TABLESPACE-RECOVER-INDEX-and-RECOVER-INDEXSPACE-syntax.

OBJECTSET creator.name

OBJECTSET is available in the following syntactical forms:

  • RECOVER OBJECTSET creator.name

    RECOVER OBJECTSET recovers all objects in a group, both table spaces, and indexes.

    Important

    INDEXES YES is not valid with a RECOVER OBJECTSET specification.

Related topics

RECOVER-TABLESPACE-RECOVER-INDEX-and-RECOVER-INDEXSPACE-option-descriptions

Using-BMC-AMI-Recovery-Manager-object-sets

  • RECOVER TABLESPACE OBJECTSET creator.name
  • RECOVER TABLESPACE OBJECTSET recovers only the table spaces in the group.

  • RECOVER TABLESPACE OBJECTSET creator.name INDEXES YES

    RECOVER TABLESPACE OBJECTSET... INDEXES YES recovers the table spaces in the group along with their associated indexes.

  • RECOVER INDEX OBJECTSET creator.name

    RECOVER INDEX OBJECTSET recovers only the indexes in the group.

Important

SIMRCVR is also valid in place of RECOVER.

The following rules apply to creator.name:

  • creator specifies the name of the creator of the group and can have up to 128 characters in length.
  • name species the group name and can have up to 128 characters in length.
  • You can delimit both creator and name with single or double quotation marks.
  • Both creator and name can contain the special characters $, #, and @ in any position.

BMC AMI Recover uses dynamic grouping to determine the group contents at the time that you run the BMC AMI Recover job containing the OBJECTSET option. Because BMC AMI Recover reads the objects in the group each time the job is executed, objects might be added or removed from the group.

Important

BMC AMI Recover does not read BMC AMI Recovery Manager recovery options for the group. If BMC AMI Recovery Manager recovery options change, you must run BMC AMI Recovery Manager to pick up the new options and generate the control cards.

Following are restrictions that apply when you use OBJECTSET in any of its forms on the RECOVER statement:

  • AUX is ignored with any specification of OBJECTSET.
  • You cannot specify DSNUM with OBJECTSET. BMC AMI Recover uses the group definition for the object.
  • You can specify OBIDXLAT with OBJECTSET only when all the OBID specifications can be omitted. For information about OBIDXLAT, see OBIDXLAT-specification.
  • Only TOCOPY LASTCOPY is valid with OBJECTSET. (You cannot use a specific data set name.)
  • You cannot use INLOG with OBJECTSET.
  • BMC AMI Recover allows only one OBJECTSET clause, and the statement can not contain additional TABLESPACE, INDEX, or INDEXSPACE clauses.

When you use OBJECTSET, if BMC AMI Recover tries to recover a group of objects and more than 10 of the objects are unrecoverable, BMC AMI Recover issues an error for each object that is unrecoverable, and discontinues further processing of the group. This behavior is based on the ERRCONT option which has a default value of 10. To avoid this behavior, set the ON ERROR CONTINUE option with a value that will exceed the possible number of errors in the group, and the recovery will be complete.

EXCLUDE (dbname.ts or qualifier.ix)

Use the EXCLUDE option after an OBJECTSET specification to exclude one or more objects from recovery. You can use wildcards or fully qualified names to specify the exclusions. The following wildcards are valid:

  • % and * match no characters to any number of characters in the object name.
  • _ and ? match a single character in the object name.

List the excluded objects following the EXCLUDE keyword. Each item in the list must be in the form dbname.ts or qualifier.ix and you must separate the individual items with commas. Enclose the list in parentheses.

The following considerations apply to the use of the EXCLUDE option with the OBJECTSET specification:

  • When you specify INDEXES YES for a RECOVER OBJECTSET statement and specify a tablespace for exclusion, the associated indexes are also excluded.
  • You cannot exclude individual indexes when INDEXES YES is specified.

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.

DSNUM integer

Use this option to exclude 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 exclude 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.

OBIDXLAT

Use the OBIDXLAT keyword to change the internal IDs in the Db2 table space or index as the table space or index is recovered.

Important

Note the following information about the use of OBIDXLAT:

  • 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 further processing.
  • OBIDXLAT of Instant Snapshots of universal table spaces (UTS) further reduces the processing time, even if OBIDs change.
  • If you specify RESET, BMC AMI Recover does not get a speed improvement. For data sharing environments, RESET is usually not necessary. For non-data-sharing environments, if the RBAs on the target system is larger than the RBAs on the source, RESET is probably not necessary.

RESET

The RESET keyword causes the log points in each data page to be reset to 0. You must specify RESET when you are migrating data from one Db2 non-data-sharing system to another because the log point values on the first subsystem is meaningless or misleading on the target Db2.

The recovery log point and level fields in the header page are also reset to 0 if you are not using the INDEPENDENT OUTSPACE option. If you are using the INDEPENDENT OUTSPACE option, the level fields are reset but the recovery log point is not.

 

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