1.0

Specifies the number of threads to use for the import process. Each thread
processes a different portion of the file 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.sqlfire.load.Import. The specified class overrides the default import
IMPORTCLASSNAME
process, and can perform on-the-fly 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 identifier, 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 identifier,
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 file. If you are
importing from a non-Derby source, the format of the reference to the LOB stored in the main import file must
be lobsFileName.Offset.length/.
•
Offset is position in the external file 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 from a main import file that contains references which point to a
separate file that contains LOB data
The following example shows how to import data into the STAFF table in a sample database from a delimited
data file staff.del. This example defines a comma as the column delimiter. The data will be appended to
the existing data in the table. The import procedure uses the default import implementation with 2 threads, and
does not lock the target table:
CALL SYSCS_UTIL.IMPORT_TABLE_LOBS_FROM_EXTFILE(
'APP','STAFF','c:\data\staff.del',',','"','UTF-8',0,0,2,0,null,null);
SYSCS_UTIL.SET_EXPLAIN_CONNECTION
Enables or disables capturing query execution plans and statistics for the current connection.
After enabling query execution plan capture, you can optionally enable statistics timing using
SYSCS_UTIL.SET_STATISTICS_TIMING.
Enable query execution plan capture by calling this procedure with a non-zero argument. Disable capture by
calling the procedure with a zero argument. See Capture Query Execution Plans for All Statements on page 260.
Syntax
SYSCS_UTIL.SET_EXPLAIN_CONNECTION(IN SMALLINT ENABLE)
563
SQL Language Reference