1.0

Table Of Contents
Species the code set of the data in the input le. The code set name should be
one of the Java-supported character encoding sets. Data is converted from the
CODESET
specied code set to the database code set (UTF-8). You can specify a NULL
value to interpret the data le in the same code set as the JVM in which it is
being executed. The CODESET parameter takes an input argument that is a
VARCHAR (128) data type.
SQLFire does not implement this argument. Imported data is always added
(inserted) to the target table without changing the existing table data. Specify
any value of type SMALLINT.
REPLACE
A input argument of type SMALLINT. With a non-zero value, this procedure
operates similar to SYSCS_UTIL.IMPORT_TABLE, and it locks the table
LOCKTABLE
during the import operation. Specify a value of zero to prevent SQLFire from
locking the table during the import operation.
Species the number of threads to use for the import process. Each thread
processes a different portion of the le in parallel, and performs a bulk insert to
the SQLFire system.
NUMTHREADS
A input argument of type SMALLINT. With a non-zero value, SQLFire treats
the SCHEMANAME and TABLENAME arguments as case-sensitive. With a
zero value, SQLFire treats the schema and table names as case insensitive.
CASESENSITIVENAMES
The argument can specify a custom class that extends
com.vmware.sqlre.load.Import. The specied class overrides the default import
IMPORTCLASSNAME
process, and can perform on-the-y data conversions from external formats to
formats that SQLFire supports. If you specify NULL for this argument, then
SQLFire uses the default Import class.
This argument is reserved for future use. Always specify NULL for the argument
in this release
ERRORFILE
If you create a schema, table, or column name as a non-delimited identier, you must pass the name to the import
procedure using all uppercase characters. If you created a schema, table, or column name as a delimited identier,
you must pass the name to the import procedure using the same case that was used when it was created.
Usage
This procedure will read the LOB data using the reference that is stored in the main import le. The format of
the reference to the LOB stored in the main import le must be lobsFileName.Offset.length/.
Offset is position in the external le in bytes
length is the size of the LOB column data in bytes
For additional information on using this procedure see the section "Using the bulk import and export procedures"
in the Apache Derby Tools and Utilities Guide.
Example importing data into specific columns, using a separate import file for the LOB data
The following example shows how to import data into several columns of the STAFF table. The STAFF table
includes a LOB column in a sample database. The import le staff.del is a delimited data le. The
staff.del le contains references that point to a separate le which contains the LOB data. The data in the
import le is formatted using double quotation marks (") as the string delimiter and a comma (,) as the column
557
SQL Language Reference