How violations are identified

CHECK DATA issues a message for every row that contains a referential constraint violation or table check constraint violation.

The violation is identified by:

  • The RID of the row
  • The name of the table that contains the row
  • The name of the constraint that is being violated

The following figure shows an example of messages that CHECK DATA issues.

Figure 1. Example of messages that CHECK DATA issues
DSNU0501   DSNUGUTC - CHECK DATA TABLESPACE DBJM1203.TLJM1203
            TABLESPACE DBJM1203.TPJM1204
            FOR EXCEPTION IN TLJM1203.TBJM1203 USE ADMF001.EXCPT3
            IN TPJM1204.TBJM1204 USE ADMF001.EXCPT4 DELETE YES
DSNU7271 = DSNUKINP - TABLESPACE 'DBJM1203.TLJM1203' IS NOT CHECK PENDING

DSNU7301   DSNUKDST - CHECKING TABLE TPJM1204.TBJM1204
DSNU0421   DSNUGSOR - SORT PHASE STATISTICS -
            NUMBER OF RECORDS=4
            ELAPSED TIME=00:00:00
DSN0733l   DSNUKERK - ROW (RID=X'000000020B') HAS NO PARENT FOR
TPJM1204.TBJM1204.TABFK
DSN0733l   DSNUKERK - ROW (RID=X'0010000201') HAS NO PARENT FOR
TPJM1204.TBJM1204.TABFK
DSN0733l   DSNUKERK - ROW (RID=X'002000020B') HAS NO PARENT FOR
TPJM1204.TBJM1204.TABFK
DSN0733l   DSNUKERK - ROW (RID=X'0030000201') HAS NO PARENT FOR
TPJM1204.TBJM1204.TABFK
DSNU739l   DSNUKDAT - CHECK TABLE TPJM1204.TBJM1204 COMPLETE, ELAPSED
TIME=00:00:00
DSNU741l = DSNUKRDY - 4 ROWS DELETED FROM TABLE TPJM1204.TBJM1204
DSNU568l = DSNUGSRX - INDEX TPJM1204.IPJM1204 IS IN INFORMATIONAL COPY PENDING
DSNU568l = DSNUGSRX - INDEX TPJM1204.IXJM1204 IS IN INFORMATIONAL COPY PENDING
DSNU7491   DSNUK001 - CHECK DATA COMPLETE,ELAPSED TIME=00:00:02
DSNU010l   DSNUGBAC - UTILITY EXECUTION COMPLETE, HIGHEST RETURN CODE=4