The ROW LOG file contains rowid and data values for each row on which logged integrity constraint violation(s) occurred. The row data appears exactly once for a given row, regardless of the number of integrity constraint violations that occurred on that row. For a given load, there are three types of messages logged: a timestamped header, row data, and a timestamped trailer. The header and trailer appear once per load.
The format of the header message is as follows:
<datetime load started> LOAD TABLE <table-name> Integrity Constraint Violations <formatting information>
where <formatting information> is
the date, time, and datetime formats used in formatting the row
data. For example:
2002-02-24 23:04:31 LOAD TABLE customer Integrity Constraint Violations Date Format: yyyy/mm/dd Time Format: hh:mm:ss Datetime format: yyyy/mm/dd hh:mm:ss
The row data message consists of two parts:
rowid The row number within the table where this row would have been loaded, if an integrity constraint violation had not occurred.
data values The data values in the row, separated by either a comma or the user-specified LOG DELIMITED BY separator.
For example,
3216 #Jones John#NULL#NULL#S#1945/01/12#NULL#
The format of the data values in the row data message is determined by the following rules:
When the data type is VARBINARY or BINARY, the data is represented by ASCII hexadecimal characters.
DATE values are represented in the format specified by the DATE_FORMAT database option. The default format is YYYY-MM-DD.
DATETIME and TIMESTAMP values are represented in the format specified by the TIMESTAMP_FORMAT database option. The default is YYYY-MM-DD HH:NN:SS.SSS.
TIME values are represented in the format specified by the TIME_FORMAT database option. The default is HH:NN:SS.SSS.
NULL values are represented by the token NULL.
Filler fields do not appear in
the row data message.
The format of the trailer message is as follows:
<datetime load completed> LOAD TABLE <table-name> Completed
For example:
2002-02-24 23:05:43 LOAD TABLE customer Completed
The number of distinct errors in the MESSAGE
LOG file may not exactly match the number of rows in the ROW
LOG file. The difference in the number of rows is due
to the parallel processing of the load performed by multiple threads.
More than one thread may report that the number of constraint violations
has exceeded the specified limit.
