OBIDXLAT—Define OBIDs for Recreated Tables
The OBIDXLAT keyword specifies the OBIDs of the original and recreated tables.
The OBIDXLAT keyword specifies the OBIDs of the table in the original tablespace and the OBIDs of the table being recreated. If you omit OBIDXLAT, recovery occurs without the OBID translation.
Consider the following items when you use this keyword:
- OBIDXLAT does not support concurrent copies.
- OBIDXLAT cannot be used with the Db2 directory and catalog tablespaces (DSNDB01 and DSNDB06) to populate user-defined objects such as shadow or ACM tables.
- The destination object must have the same DDL structure for the table and tablespace as the object when the source image copy was taken.Tablespace header pages may not reflect DDL changes that result in a new version record, such as altering a table, that were made before taking an image copy. If such an image copy is used as the source image copy, the recovery can fail. After you alter a table or tablespace, we recommend running REORG before you take an image copy. This process ensures that header pages reflect all DDL changes.
- Consistency checks for log ranges from different subsystems cannot be performed. Verify that the specified range does not include any not logged activity; for example, REORG with LOG=NO.
- OBIDXLAT is not valid with LIST, RECOVER DATABASE, OBJ-LIST, and RECOVER INDEX.
- OBIDXLAT with SORTLOG NO or SORTLOG CONCURRENT is not valid with LOG APPLY.
- If you specify OBIDXLAT with only one OBID, it is assumed that the tablespace contains only one table. In this case, the recovery job can contain only one OBIDXLAT statement.
This keyword has the following format:
- old-obidSpecifies the old OBID value of the recreated table. If the tablespace contains only one table (HPGTBLC='0001'X), do not specify an old OBID. The OBIDXLAT feature retrieves the OBID automatically.
- new-obidSpecifies the new OBID value for the recreated table. If the tablespace contains only one table (HPGTBLC='0001'X), do not specify a new OBID. The OBIDXLAT feature retrieves the OBID automatically.
Specify the old and new OBIDs for each table as an integer (the table OBID that is stored in the Db2 catalog). You can also specify the OBIDs as a hexadecimal number preceded by an X and enclosed in single quotes.
To recover multiple tables in a tablespace, include an OBIDXLAT phrase for each table.
For nonpartitioned indexes, set MAXTASKS or PARALLEL to the number of indexes to recover.
If the tablespace has always contained only one table (HPGTBLC='0001'X), you can specify OBIDXLAT without an OBID parameter. The translation is performed automatically.
You can apply log records from different subsystems (that is, the old and new OBIDs can be on separate subsystems). Shared DASD must be present and the SETUP parmlib member of the recovering system must have a defined bootstrap data set. To apply log records, use STARTRBA or STARTLOGPOINT. By default, no log records are applied.
An image copy of the destination tablespace is created dynamically unless you specify NO-NEW-COPY. To allocate the image copy data set manually, use the QUICKCOPY keyword.