Improved data validation after running DSN1COPY

After the DSN1COPY utility runs, mismatches between the data page format and the catalog description of the format can result. The REPAIR utility is enhanced to identify and fix more of those mismatches.

If DSN1COPY is not used correctly, subsequent attempts to access the data can result in abends, data corruption, and storage overlays. For example, the following scenarios might result in such errors:

  • Incorrect DBID, PSID, or OBID values are specified when you run DSN1COPY with the OBIDXLAT option.
  • DSN1COPY is used to copy data to a table space of a different type. For example, data is copied from a segmented table space to a partition-by-growth table space.
  • DSN1COPY is used to copy data to a table space with a different version number or table definition.

Beginning in Db2 12, the REPAIR CATALOG utility enables the following mismatches to be fixed:

  • The column data type or length in the table space differs from the catalog definition for the column. If Db2 supports conversion from the data type and length in the table space to the data type and length in the column, REPAIR CATALOG enables conversion of the data type or length of the data in the table space to match the catalog definition the next time that the data is accessed.

In Db2 12, the REPAIR CATALOG TEST utility is enhanced to detect the following mismatches:

  • The table space is a partition-by-range table space with absolute page numbering, but the catalog indicates that the table space has relative page numbering.
  • The table space is partition-by-range with relative page numbering, but the catalog indicates that the table space has absolute page numbering.
  • The table space is a partition-by-range table space with absolute page numbering, but the catalog indicates that the table space has relative page numbering. REPAIR CATALOG changes the catalog definition to match the table space format.
  • The number of columns in the table space is greater than the number of columns in the catalog definition of the table.
  • The column data type or length in the table space differs from the catalog definition for the column.
Restriction: None of these data validation enhancements apply to LOB and XML table spaces.