Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Recover for Db2 13.1.

OBIDXLAT specification

The following rules apply to the OBIDXLAT specification:

  • The source or the target DBIDs and PSIDs may be omitted, or the DBID or PSID keyword may be omitted. If a source or target value is omitted from a DBID or PSID clause, the missing value defaults to the DBID or PSID of the object as reflected in the catalog of the current subsystem except when INCOPY is specified without DROPRECOVERY. If INCOPY is specified without DROPRECOVERY, the source DBID and PSID is taken from the image copy.
  • For a single-table table space, the source or the target OBID may be omitted, or the OBID keyword may be omitted. If a source or target value is omitted from an OBID clause, the missing value defaults to the OBID of the object as reflected in the catalog of the current subsystem except when INCOPY is specified without DROPRECOVERY. If INCOPY is specified without DROPRECOVERY, the source OBID is taken from the image copy. If more than one OBID clause is coded, the source and target values are required.
  • For multiple-table table spaces, rows are not translated for which there is no OBID clause, but you must code at least one OBID clause with both source and target values, or you must code a DBID or PSID clause.
  • For an index, if you code an OBID clause, you must code two OBID clauses, one for the index and one for the table on which the index is built. When INCOPY is specified for an index, you may omit both OBID clauses, in which case the source OBID for the index and the table is taken from the image copy. If you do not omit the ID clauses, you must code both the target and source values for both OBID clauses.

If you code INCOPY and OBIDXLAT, you must code TOCOPY or you must supply the source DBID and PSID in the clause. You can use the USEHDROBIDS option (USEHDROBIDS and USEHDROBIDS-YES) to indicate if the OBIDs in the header are valid or not.

If you code OBIDXLAT and log apply is required, you should also specify OUTCOPY ONLY. These specifications produce an output copy that you can use on a different system with different OBIDs. If you were to do OBIDXLAT to an existing space, the object IDs would no longer match.

For example, these are valid specifications:

RECOVER ... OBIDXLAT DBID(100,101) PSID (200,201)
INCOPY FULL DSNAME ... RBA X'123456'

or

RECOVER ... OBIDXLAT DBID(,101) PSID(,201)
INCOPY FULL DSNAME ...
TOCOPY LASTCOPY

The following example is not valid:

RECOVER ... OBIDXLAT DBID(,101) PSID(,201)
INCOPY FULL DSNAME ... RBA X'123456'

The syntax diagram for the OBIDXLAT specification is in RECOVER-TABLESPACE-RECOVER-INDEX-and-RECOVER-INDEXSPACE-syntax.

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 are larger than the RBAs on the source, RESET is probably not necessary.

Option

Description

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.

DBID (X'hexSourceID', X'hexTargetID')

DBID (decimalSourceID, decimalTargetID)

Optionally, specify this clause to provide the DBIDs to be translated. You can specify the DBID in hexadecimal or decimal format.

PSID (X'hexSourceID', X'hexTargetID')

PSID (decimalSourceID, decimalTargetID)

Optionally, specify this clause to provide the PSIDs to be translated. You can specify the PSID in hexadecimal or decimal format.

When you are recovering clone objects, remember that the base and clone objects are differentiated by differences in the PSID value. The high order bit of the PSID is used to refer to a particular data set instance number as follows:

  • A high order bit value of 0 indicates instance number 1
  • A high order bit value of 1 indicates instance number 2

Other than the high order bit, the PSID numbers are the same for both a base object and its clone. You should use the PSID with the high order bit set on for instance 2 objects in the OBIDXLAT translation specification.

OBID (X'hexSourceID', X'hexTargetID')

OBID (decimalSourceID, decimalTargetID)

Optionally, specify this clause to provide the OBIDs to be translated. You can specify the OBID in hexadecimal or decimal format.

Related topics

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

REBUILD-INDEX-command

 

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