You can use BL_OPTIONS=
to pass options to the DBMS bulk-load facility when it is called,
which affects how data is loaded and processed.
Aster n
Cluster: By
default, no options are specified.
DB2
under UNIX and PC Hosts: This option passes DB2
file-type modifiers to DB2 LOAD or IMPORT commands to affect how data
is loaded and processed. Not all DB2 file type modifiers are appropriate
for all situations. You can specify one or more DB2 file type modifiers
with .IXF files. For a list of file type modifiers, see the description
of the LOAD and IMPORT utilities in the
IBM DB2
Universal Database Data Movement Utilities Guide and Reference.
Netezza: Any
text that you enter for this option is appended to the USING clause
of the CREATE EXTERNAL TABLE statement—namely, any external_table_options
in the
Netezza Database User's Guide.
OLE
DB: By default, no options are specified. This
option is valid only when you are using the Microsoft SQL Server provider.
This option takes the same values as the
-h HINT
option of the Microsoft BCP utility. For example, the ORDER= option
sets the sort order of data in the data file; you can use it to improve
performance if the file is sorted according to the clustered index
on the table. See the Microsoft SQL Server documentation for a complete
list of supported bulk copy options.
Oracle: This
option lets you specify the SQL*Loader options ERRORS= and LOAD=.
The ERRORS= option specifies the number of insert errors that terminates
the load. The default value of ERRORS=1000000 overrides the default
value for the Oracle SQL*Loader ERRORS= option, which is 50. LOAD=
specifies the maximum number of logical records to load. If the LOAD=
option is not specified, all rows are loaded. See your Oracle utilities
documentation for a complete list of SQL*Loader options that you can
specify in BL_OPTIONS=.
Sybase
IQ: By default, no options are specified. Any
text that you enter for this option is appended to the LOAD TABLE
command that the
SAS/ACCESS interface uses for the bulk-load process.