The MESSAGE LOG file contains row and column information for each integrity constraint violation logged. For a given load, there are three types of messages logged: a timestamped header, row information, and a timestamped trailer. The header appears once per load. The tailer appears once if the statement executes successfully. The row information appears once for each integrity constraint violation logged.
The format of the header message is as follows:
<datetime load started> Load Table <table-name>: Integrity Constraint Violations
For example:
2009-05-24 23:04:31 Load Table Customers: Integrity Constraint Violations
The row information message consists of three parts:
rowid The row number within the table where this row would have been loaded, if an integrity constraint violation had not occurred.
column numbers The column number(s) specified by the schema.
For example,
1267 DATA VALUE 4 3216 UNIQUE 1 3216 NULL 3 3216 NULL 6 9677 NULL 1
The format of the trailer message is as follows:
<datetime load completed> Load Table <table-name> Completed
For example:
2009-05-24 23:05:43 LOAD TABLE Customers: Completed
The number of rows (errors reported) in the MESSAGE
LOG file can exceed the IGNORE CONSTRAINT option
limit, because the load is performed by multiple threads running
in parallel. More than one thread may report that the number of
constraint violations has exceeded the specified limit.
