SQL/MX 2.x Reference Manual (H06.04+)

SQL/MX Utilities
HP NonStop SQL/MX Reference Manual—540440-003
5-33
Considerations for import
If a character in the data file cannot be translated into one required by the target
column, NonStop SQL/MX issues an error. Importing an UCS2 data file into an
ISO88591 column with character' code values beyond the range of ISO88591 leads to
this translation error condition.
Datetime and Interval Data for Input File
For datetime and interval data, do not specify keywords that are part of the data type in
the column definition.
For example:
•
If the datetime value to be imported is DATE '1990-01-22', specify the field
without the keyword in the input data file, as:
1990-01-22
•
If the interval value to be imported is INTERVAL '03-04' YEAR TO MONTH,
specify the field without the keywords in the input data file, as:
03-04
Datetime Normalization
NonStop SQL/MX supports the three standard ANSI SQL:1999 datetime formats,
which can be loaded without normalization.
Date formats other than ANSI SQL:1999 formats must be normalized to substitute the
appropriate year, month, and day delimiters; zero-pad missing digits; and transpose
year, month, and day field order. Time formats other than ANSI SQL:1999 formats
must be normalized to substitute the appropriate hour, minute, and second delimiters,
and zero-pad missing digits. See [DATE FORMAT] on page 5-26.
Transaction Considerations for import
import might automatically turn auditing off for all partitions on an empty table without
indexes. Auditing is turned back on after the import operation completes or if it fails for
any reason. This behavior allows import to take advantage of fast loading techniques
and to avoid TMF transaction issues. Turning off auditing for the table invalidates
online dumps. After the import operation completes, you must perform a new TMF
online dump for all partitions of the table.
If multiple import processes are started on different partitions of a table without
indexes, the first import operation turns auditing off for all the partitions of the table. In
this scenario, only the first import operation would benefit from the efficient insert
technique. A warning about performance is issued for other import processes on the
same table, because the table can be unaudited and nonempty.
If the table is not empty or has dependent indexes, import continues with the normal
load operation using TMF transactions.