NonStop SQL/MP Reference Manual

NonStop SQL/MP Reference Manual—142115
L-31
Considerations—LOAD
PARALLEL EXECUTION { ON [ config-op ] | OFF }
config-op is:
CONFIG { config-file [ FOR index-name ] }
{ }
{ ( config-file FOR index-name }
{ [, config-file FOR index-name]... ) }
specifies whether to load partitions of a partitioned index in parallel. The default
(PARALLEL EXECUTION OFF) is to load partitions sequentially.
PARALLEL EXECUTION ON applies only to one partitioned index at a time. If the
loaded table has more than one partitioned index, the partitions of the first index are
loaded in parallel first. After the first index has been loaded, the partitions of the
second index are loaded in parallel, and so forth. The parallel load index operation,
therefore, loads the partitions of a physical index simultaneously; it does not load
two physical indexes simultaneously.
config-file is the name of an EDIT file that contains instructions for
configuring the processes that load the index. See Parallel Index Loading
on
page P-5 for information about how to specify configuration instructions in
config-file.
FOR INDEX index-name specifies which index to load in parallel using the
configuration in the preceding config-file. index-name is the name of any
partition of the index. Each specified index must be unique.
If you specify only one configuration file in the PARALLEL EXECUTION clause
and omit the FOR index-name clause, the configuration file applies to all indexes
for the loaded table.
If you specify more than one configuration file in the PARALLEL EXECUTION
clause, you must specify the FOR index-name clause for each configuration file.
If at least one index is specified in the CONFIG clause, then the partitions of any
indexes not specified are loaded in parallel using default configuration values.
Considerations—LOAD
•
Authorization requirements
LOAD requires authority to read the source file and to write to the target file. If you
load data to or from a table, you must have authority to read the catalog in which the
table is described.
•
LOAD operations
LOAD first purges all data from the target file or table, then begins writing source
records or rows to the target file or table, converting data and reorganizing records
or rows as appropriate.