The effects of not specifying the OBIDXLAT option

If you use DSN1COPY to load data into a table space or index without specifying the OBIDXLAT option, be careful not to invalidate embedded Db2 internal identifiers.

Those OBIDs can become invalid in the following circumstances:

  • When you drop and re-create tables after the input data set to DSN1COPY was created.
  • When a difference exists among the following attributes between the target subsystem and the source subsystem:
    • Table space attributes of BUFFERPOOL or NUMPARTS
    • Table attributes other than table name, table space name, and database name
    • The order of the table spaces, indexes, and tables that the user defined or dropped in the source and target databases

To protect against invalidating the OBIDs, specify the OBIDXLAT parameter for DSN1COPY. The OBIDXLAT parameter translates OBID, DBID, PSID, or ISOBID before DSN1COPY copies the data.