Start of change

DSNU671I csect-name - DBID=X'dbid' PSID=X'psid' OBID=X'obid' mismatched-information-type

Explanation

The REPAIR utility with the CATALOG option detected that information in the catalog table is different from the information in the page set. In this case, no value was available for the page set.

This problem might occur after copying data by using DSN1COPY or after using redirected recovery (RECOVER with the FROM option).

csect-name
The name of the control section that issued the message.
dbid
The database identifier (DBID) for the database in which mismatched information was detected.
psid
The page set identifier (PSID) for the table space for which mismatched information was detected.
obid
The object identifier (OBID) for the table for which mismatched information was detected.
mismatched-information-type
The type of information that did not match. mismatched-information-type can have one of the following values:
DBID IN THE CATALOG DOES NOT MATCH THE PAGE SET
The database identifier in the catalog does not match the value in the page set..
PSID IN THE CATALOG DOES NOT MATCH THE PAGE SET
The page set identifier in the catalog does not match the value in the page set.
OBID IN THE CATALOG DOES NOT MATCH THE PAGE SET
The object identifier in the catalog does not match the value in the page set.
TABLE SCHEMA IN THE CATALOG DOES NOT MATCH THE PAGE SET
The table schema definition in the catalog does not match the schema definition in the page set.
TABLE ENCODING SCHEME IN THE CATALOG DOES NOT MATCH THE PAGE SET
The encoding scheme (CCSID) definition of the table, column, or both in the catalog does not match the value in the page set.
TABLE VERSION IN THE CATALOG DOES NOT MATCH THE PAGE SET
The table version in the catalog does not match the value in the page set.
TABLE IN THE PAGE SET DOES NOT HAVE A SYSTEM PAGE
The table is missing a system page.
TABLE IS DROPPED IN THE PAGE SET, BUT EXISTS IN THE CATALOG
The table is logically dropped.
TABLE IN THE PAGE SET IS NOT IN THE CATALOG
A table exists in the page set, but not in the catalog.
PART(part-number) WAS A TARGET OF DSN1COPY. VERSION PAGE NOT INSERTED.
The table space partition with the number that is specified by part-number was previously the target of a DSN1COPY job. A system page cannot be inserted in the partition because the source and target partitions might not have matching schema definitions.
WAS A TARGET OF DSN1COPY. VERSION PAGE NOT INSERTED.
The table space was previously the target of a DSN1COPY job. A system page cannot be inserted in the table space because the source and target partitions might not have matching schema definitions.
PART(part-number) NO SPACE AVAILABLE TO INSERT VERSION PAGES
A system page cannot be inserted into the table space partition with the number that is specified by part-number because there is not enough space in the partition for the system page.
NO SPACE AVAILABLE TO INSERT VERSION PAGES
A system page cannot be inserted into the table space because there is not enough space in the table space for the system page.
PART(part-number) UNABLE TO INSERT VERSION PAGES
A system page cannot be inserted into the table space partition that is specified by part-number.
UNABLE TO INSERT VERSION PAGES
A system page cannot be inserted into the table space.
PART(part-number) SCHEMA MISMATCH. UNABLE TO INSERT VERSION PAGES.
A system page cannot be inserted into the table space partition that is specified by part-number because there is a schema mismatch between the content of the partition and the description in the OBDREC structure for the partition.
SCHEMA MISMATCH. UNABLE TO INSERT VERSION PAGES.
A system page cannot be inserted into the table space because there is a schema mismatch between the content of the table space and the description in the OBDREC structure for the table space.
Start of changeTABLE VERSION IS NOT IN THE RANGE OF TABLE SPACE VERSIONS End of change
Start of changeThe version number of the table is not in the range of valid version numbers for the table space. End of change

System action

Start of changeDepending on the type of mismatch, whether the TEST keyword is specified, and whether the table space was the target of DSN1COPY, REPAIR ends with return code 0, 4, or 8. Messages DSNU667I, DSNU690I, or DSNU695I are displayed to provide more information.End of change

System programmer response

  1. Examine messages DSNU667I, DSNU690I, or DSNU695I to learn more about the mismatch.
  2. Choose between the following alternative approaches:
    • Alternative 1:
      1. Find the DSN1COPY or redirected recovery job that copied or recovered the affected data, and check the following items:
        • Ensure that the SYSXLAT DD statement contains the correct IDs for each object to be translated.
        • Ensure that the correct object name is specified.
        • Ensure that the target and source table have matching columns. See the subsequently issued DSNU667I messages for additional information.
        • Ensure that the target and source objects have not been dropped. See the subsequently issued DSNU667I messages for additional information.
      2. If you made any changes based on the items you checked, rerun DSN1COPY or redirected recovery.
    • Alternative 2:
      1. Run REPAIR DBD TEST to determine whether the DBD in the EDM pool is up to date.
      2. If the DBD in the EDM pool is not up to date, with the guidance of IBM® Support, run REPAIR DBD REBUILD to rebuild the DBD from the catalog.
End of change