Integrity Constraint Violation Messages

LOAD TABLE allows you to control load behavior when integrity constraints are violated and to selectively log information about the violations.

Using the MESSAGE LOG ... ROW LOG option with the ONLY LOG clause, you can direct the load to log information about specific types of integrity constraint violations both per violation in a message log file and per row in a row log file. If the ONLY LOG clause is not specified, only the timestamps indicating the start and completion of the load are logged in these files.

Note that the message log and row files for integrity constraint violations are distinct from the IQ message log file (.iqmsg).

You can specify whether to ignore UNIQUE, NULL, DATA VALUE, and/or FOREIGN KEY constraint violations that occur during a load and the maximum number of violations to ignore before initiating a rollback. You can also direct the load to log information about specific types of integrity constraint violations both per violation in a message log and per row in a row log.

• MESSAGE LOG Contents and Format
  The MESSAGE LOG file contains row and column information for each integrity constraint violation logged.
• ROW LOG Contents and Format
  The ROW LOG file contains rowid and data values for each row on which logged integrity constraint violation(s) occurred.
• MESSAGE LOG and ROW LOG Example
  This example illustrates the contents and format of the MESSAGE LOG and ROW LOG files.