The database option SECONDARY_FILE_ERROR allows
you to specify the action of the load if an error occurs while opening
or reading from a secondary BINARY FILE or ASCII
FILE.
If SECONDARY_FILE_ERROR is
ON, the load rolls back if an error occurs while opening or reading
from a secondary BINARY FILE or ASCII
FILE.
If
SECONDARY_FILE_ERROR is
OFF (the default), the load continues, regardless of any errors
that occur while opening or reading from a secondary
BINARY
FILE or
ASCII FILE. The
LONG
BINARY or
LONG VARCHAR cell is left with
one of these values:
NULL, if the column allows
nulls
Zero-length value, if the column does not allow
nulls
Any user can set SECONDARY_FILE_ERROR for the
PUBLIC
role or temporary; the option setting takes effect immediately.
When logging integrity constraint violations to the load error
ROW LOG file, the information logged for a
LONG BINARY or
LONG
VARCHAR column is:
Actual text as
read from the primary data file, if the logging occurs within the
first pass of the load operation
Zero-length value, if the logging occurs within
the second pass of the load operation