SQL/MX 2.x Reference Manual (H06.10+, J06.03+)

SQL/MX Utilities
HP NonStop SQL/MX Reference Manual—544517-008
5-35
Considerations for import
The error messages written to exec-errormsg-filename will not have any row
number in them to indicate the row in the input file or in exec-error-filename
associated with the error message.
Regardless of whether exec-errormsg-filename and exec-error-
filename are the same file, if you invoke import again with exec-error-
filename as the input file, the same format file can be used. Any interspersed
error messages will be automatically ignored by import. You must specify the
same file type (DELIM or FIXED) when using exec-error-filename as was
used for the original input file.
It is important to note that Dataloader/MX has a pass-through mode where the
input data is sent on as the output data without performing any transformations on
the data. That capability should allow an error log file produced by import (with or
without interspersed error message strings) to be used as the input file for
Dataloader/MX, if desired.
-Z charset
specifies the character set for the data being imported. Valid values are ISO88591
or UCS2. The default value for -Z option is ISO88591. For details about character
set conversion, see Data Types of Input Values for Input File on page 5-43.
Considerations for import
You must have ALL privileges on the destination table or be the super ID.
Fast Loading and Transaction Considerations
If you are importing into an empty table, import uses the fast-loading technique if the
target table meets these criteria:
•
It is empty.
•
It has no indexes.
•
It has no droppable primary key, unique key, or foreign key constraints.
•
It has no enabled triggers or you specified the -D option to disable triggers.
To improve the performance of the fast-loading technique, import turns off the audit
attribute for the entire table at the start of the operation and turns it back on when the
operation ends. If another import operation is attempted on the same table while an
Note. If the -XM option is used, you should also consider the space consumed by the
error message log file when choosing the -XL value. Each error message will take at least
65 bytes and may be much longer if the error message includes a specified table name,
check condition name, and so on. If exec-errormsg-filename and exec-error-
filename are the same file, the error messages also have the indicator prefix and suffix
strings and with both the error messages and the rows in error going into the same file, an
even smaller -XL value may be appropriate.