DSNU355I csect-name INDEXVAL PHASE STATISTICS - error-count DUPLICATE KEY ERRORS, KEY EVALUATION ERRORS, XML ERRORS OR LOB ERRORS WERE CORRECTED BY DELETING deleted-count DATA ROWS

Explanation

This message reports the results of the INDEXVAL phase of the LOAD utility. Data rows that were added during the LOAD or RELOAD phase of this LOAD utility invocation were deleted because the data rows caused one of the following conditions:

  • Unique index violations in the BUILD phase
  • Key evaluation errors during the build of an index on an expression-based index
  • XML document errors or LOB errors in the BUILD phase
csect-name
The name of the control section that issued the message.
error-count
The number of unique index violations or key evaluation errors.
deleted-count
The number of data rows that were deleted to correct the errors.

Unique index violations are counted in one of two ways. An input data set record which has a value for a uniquely indexed column that duplicates a value that existed in the index prior to the LOAD job is counted as one duplicate key error. Two input data set records which have like values for a uniquely indexed column are counted as two unique index errors (that is, each of the two input data set records is in error).

System action

Processing continues.

System programmer response

If you suspect an error in Db2, you might need to report the problem. For information about identifying and reporting the problem, see Collecting diagnostic data.

User response

Examine the error summary from the LOAD job. Determine which of the discarded records need to be corrected and loaded into the table space.

Compare the number of duplicate key errors or key evaluation errors that were corrected in the INDEXVAL phase to the number of duplicate key errors that were detected in the BUILD phase (reported by message DSNU343I).

If the counts are unequal, notify the system programmer.

If the counts are equal, following the LOAD utility execution, examine the discards file or the LOAD error summary to determine which input data set records caused the unique index violations or key evaluation errors. Revise the input records so they will not introduce duplicate values into unique indexes and reapply the input records to the table space. Alternatively, if appropriate, make the index non-unique and reapply the rejected records that caused the duplicate key errors to the table space.

Problem determination

Collect the following diagnostic items:
  • Console output from the system on which the job was run, and a listing of the SYSLOG data set for the period of time that spans the failure.
  • Listing of SYS1.LOGREC data set, obtained by executing IFCEREP1.

Severity

4 (warning)