SQL/MP Reference Manual

HP NonStop SQL/MP Reference Manual—523352-013
L-34
Considerations—LOAD
You should perform these operations when you need to load data into an audited
table:
1. Use ALTER TABLE to set the AUDIT attribute of the table OFF.
2. Execute the LOAD utility to load data into the nonaudited table.
3. Use ALTER TABLE to set the AUDIT attribute of the table ON.
4. Perform online dumps of all table partitions and indexes. For more information
about performing online dumps, see the TMF Operations and Recovery Guide.
If you press the Break key to interrupt a load operation, SQLCI stops the load
operation and returns the SQLCI prompt immediately, but any sort processes
started by the load operation continue to execute to completion unless you exit
SQLCI and stop them separately. Any data loaded at the time you interrupt a
load operation remains in the table or file.
If a load operation fails, the target table or file is not usable. (Depending upon
the reason for the failure, it might or might not be empty and it might or might
not be marked corrupt, but in no case is it usable.) Make any necessary
corrections in the LOAD options you specified and rerun the load operation.
Alternately, if you do not want to rerun the load operation, use the
PURGEDATA command to clear the corrupt flag.
LOAD errors can occur at the time LOAD compiles the operation or at the time
the actual data is loaded. Compile-time errors (such as references to
nonexistent fields, mapping between incompatible source and target fields, or
unmapped target fields that have no default value) always terminate the LOAD
operation. Data-loading errors (such as violations of integrity constraints,
source data that exceeds the size of the target field, or a null value in a field
mapped to a target field that does not allow null values) can be permitted or
restricted with the ALLOWERRORS option.

Rules for using LOAD with CLASS TAPE DEFINEs or labeled tapes are described
in the discussion of the FUP COPY command in the File Utility Program (FUP)
Reference Manual.

Loading data into Enscribe files and other non-SQL objects
A non-SQL object into which you load data must be an existing file. LOAD does not
load data into any alternate-key file associated with a non-SQL object.
The target file must have default values defined for fields that do not have source
fields mapped to them. To define a default value for a data item, use the VALUE IS
clause in the DDL description of the field.
When you load key-sequenced partitioned files, consider:

In a partitioned file, the range of keys for the different partitions is stored in the
primary partition.