Collecting data for corruption and inconsistency problems

If you encounter corrupted or inconsistent data problems, collect diagnostic data from a time period when the problem occurred. DSNI and DSNT messages usually indicate that the Db2 data manager subcomponent encountered a problem.

About this task

Diagnosing data corruption problems and inconsistencies between indexes and data require IBM® Software Support expertise. A common reason for these errors is the incorrect use of DSN1COPY to replace or restore Db2 objects. If the underlying data is consistent, a rebuild of the index might resolve the problem.

Procedure

To collect diagnostic data if DSNI and DSNT messages indicate a corruption or inconsistency problem:

  1. Collect Db2 archive log data sets from all Db2 members to the last point of consistency. Also, collect the corresponding consistent REORG or IMAGE COPY data sets.
  2. If data is corrupted, collect the DSN1COPY of the table space or index.
  3. If an index is inconsistent, run CHECK INDEX or CHECK LOB.
  4. Collect the SYSLOG, which might contain messages that indicate the source of the problem.
  5. Collect the LOGREC, which might contain messages that indicate the source of the problem.
  6. Collect the JES job log for the system services address space (ssnmMSTR).
  7. Collect any supervisor call (SVC) dump generated with abend code 04E and reason code 00C9xxxx for your Db2 environment.