SQL/MX 3.2 Reference Manual (H06.25+, J06.14+)

SQL/MX Utilities
HP NonStop SQL/MX Release 3.2 Reference Manual—691117-001
5-49
import Utility
-XL max-exec-errors
is an option that directs import to ignore the specified number max-exec-
errors (from 0 to 2147483646) of ignorable execution errors without terminating.
If the number of execution errors detected by import exceeds max-exec-
errors, import shall terminate, although because of internal bundling of multiple
rows for insertion, import may report several more than max-exec-errors
detected when it does terminate.
If this option is not specified, the default value shall be zero and if any row
encounters an execution error, import terminates and writes the associated error
message to Stdout (similar to the current version of import). Regardless of the
value specified for max-exec-errors, non-ignorable execution errors cause
import to terminate and write the associated error message to Stdout.
If import terminates before exhausting the input data, any rows that were inserted
but not yet committed are backed out (similar to the current import utility).
-XM exec-errormsg-filename
is an option that specifies the pathname exec-errormsg-filename of an OSS
output file to which import logs the error messages that correspond with the
logged data rows that have execution errors. The name of the error message file
must be specified in OSS format, for example /usr/jdoe/errfile, and may be
the same as the one specified with the -XE option, but must not be the same as
any other output file.
This output file shall be created by the Import utility as a non-audited, OSS
unstructured file (or a Guardian file of type 180 if the error log file is specified to be
under /G). If the file already exists, import terminates with an error message. If
the -XM option is not specified, the error messages corresponding to rows with
execution errors shall not be logged. If the -XM option is specified but the -XE
option is not, import terminates with an error message.
If exec-errormsg-filename and exec-error-filename are specified to be
the same file, import logs each error message to the error log file, prefixed by the
string ^@ERR_ST]^ and suffixed by the string ^\[ERR_ND^ and by a row delimiter
if the input file is a delimited file. The corresponding row in error will immediately
follow.
Note. Although the -XL option allows a maximum of 2,147,483,646 errors to be ignored,
the execution error log file grows to consume a large amount of disk space long before
that many errors were actually encountered. Even if the average input row size were only
50 bytes, the error log file grows to the current OSS file size limit of 2,090,950,656 bytes
when the number of encountered errors is only 41,819,013. Therefore, it is important to
remember that if the -XE option is used, the potential size (and disk space consumption)
of the error log file must be considered when choosing the -XL value.