When you perform parallel direct path loads, there are options available for specifying attributes of the temporary segment to be allocated by the loader. These options are specified with the FILE
and STORAGE
parameters. These parameters are valid only for parallel loads.
To allow for maximum I/O throughput, Oracle recommends that each concurrent direct path load session use files located on different disks. In the SQL*Loader control file, use the FILE
parameter of the OPTIONS
clause to specify the file name of any valid data file in the tablespace of the object (table or partition) being loaded.
For example:
LOAD DATA INFILE 'load1.dat' INSERT INTO TABLE emp OPTIONS(FILE='/dat/data1.dat') (empno POSITION(01:04) INTEGER EXTERNAL NULLIF empno=BLANKS ...
You could also specify the FILE
parameter on the command line of each concurrent SQL*Loader session, but then it would apply globally to all objects being loaded with that session.
The FILE
parameter in the Oracle database has the following restrictions for parallel direct path loads:
For nonpartitioned tables: The specified file must be in the tablespace of the table being loaded.
For partitioned tables, single-partition load: The specified file must be in the tablespace of the partition being loaded.
For partitioned tables, full-table load: The specified file must be in the tablespace of all partitions being loaded; that is, all partitions must be in the same tablespace.
You can use the STORAGE
parameter to specify the storage attributes of the temporary segments allocated for a parallel direct path load. If the STORAGE
parameter is not used, then the storage attributes of the segment containing the object (table, partition) being loaded are used. Also, when the STORAGE
parameter is not specified, SQL*Loader uses a default of 2 KB for EXTENTS
.
For example, the following OPTIONS
clause could be used to specify STORAGE
parameters:
OPTIONS (STORAGE=(INITIAL 100M NEXT 100M PCTINCREASE 0))
You can use the STORAGE
parameter only in the SQL*Loader control file, and not on the command line. Use of the STORAGE
parameter to specify anything other than PCTINCREASE
of 0, and INITIAL
or NEXT
values is strongly discouraged and may be silently ignored.