SQL/MP Reference Manual

HP NonStop SQL/MP Reference Manual523352-013
L-35
Considerations—LOAD
To load a single partition (primary or secondary), specify the name of the
partition as out-file, and specify the name of the volume that contains the
partition in the PARTOF option. If you attempt to load a secondary partition
when you have not specified the PARTOF option, you receive an error
message.
To load all partitions, specify the name of the primary partition as out-file
and omit the PARTOF option.
Be careful when you use PAD and TRIM options. If your data contains the
trim-character or pad-character, data might be added or lost. Use a
pad-character or trim-character that does not appear in your data. For
example, suppose that you pad each record in a data file with zeros to a standard
size in bytes and then store the records in another file. If you later trim the trailing
zeros when you load the stored records, zeros at the end of the original data are
also trimmed.
The target file must have default values defined for columns that do not have
source fields mapped to them. To define default values, use the DEFAULT clause
of the CREATE TABLE or ALTER TABLE command.
If a record from a non-SQL source is not long enough to supply data to all fields
mapped to target columns, each target column whose source field is missing must
have a default value defined for it.
In general, if a source record from a non-SQL source does not end exactly at a
field boundary, an error occurs. These exceptions apply:
If the record ends in the middle of a VARCHAR field, the end of the record
defines the end of the VARCHAR data.
If the file is an EDIT file and the record ends in the middle of a field, SQL adds
enough blanks to the end of the input record to fill the field. In such a case,
blanks must be acceptable in that column of the source record. For example, a
decimal field would not accept blanks; a character field would.
If the record contains an array defined by an OCCURS DEPENDING ON
clause and at least one element of the array is present, the field that contains
the count must be present and the number of elements in the record must be
equal to the value of the field that contains the count.
Move options associate source fields and target fields so that data is transferred
from each source field to its corresponding target field. Some considerations for
using move options follow:
If you move data from a table to a table or between a non-SQL object and a
table and you do not specify MOVE, MOVEBYNAME, or MOVEBYORDER,
SQL uses MOVEBYORDER.
You cannot specify any move options when both source and target are
non-SQL objects.