00200-00299: DDL Syntax

Cause:	SQL/DS FORMAT clause is not supported.

Action:	Remove the FORMAT command from the control file or comment it out.

SQL*Loader-250 work data sets are not used by SQL*Loader

Cause:	The control file contains a WRKDDN statement. SQL*Loader ignores this clause.

Action:	No action required. This is an informational message.

SQL*Loader-251 sort devices are not used by SQL*Loader

Cause:	The control file contains a SORTDEVT statement. SQL*Loader ignores this clause.

Action:	No action required. This is an informational message.

SQL*Loader-252 sort data sets are not used by SQL*Loader

Cause:	The control file contains a SORTNUM statement. SQL*Loader ignores this clause.

Action:	No action required. This is an informational message.

SQL*Loader-253 DB2 partition number has no significance -- ignored

Cause:	The control file contains a PART statement. SQL*Loader ignores this clause.

Action:	No action required. This is an informational message.

SQL*Loader-254 cannot have DISCARDFILE specs here when multiple datafiles

Cause:	The control file contained multiple INFILE statements and a DISCARDFILE statement was found below the RESUME clause.

Action:	Move the DISCARDFILE statement above the RESUME clause, so it is adjacent to one of the INFILE statements.

SQL*Loader-255 log file for error recovery not used by SQL*Loader

Cause:	The control file contains a LOG statement. SQL*Loader ignores this clause.

Action:	No action required. This is an informational message.

SQL*Loader-256 SORTED INDEXES option allowed only for direct path

Cause:	The control file contains a SORTED INDEXES statement, but it was not used in a direct path load.

Action:	Specify a direct path load with DIRECT=TRUE on the command line, remove the statement from the control file, or comment it out.

SQL*Loader-257 index name specified in SORTED INDEXES does not exist on table name

Cause:	A non-existent index was specified in the SORTED INDEXES clause. Either the index does not exist or its name was misspelled.

Action:	Create the index, change the spelling, remove the specification, or comment it out.

SQL*Loader-258 maximum number of sorted indexes num exceeded on table name.

Cause:	There are too many indexes in the SORTED INDEX clause. The message displays the maximum number that are permitted.

Action:	Reduce the number of indexes specified in the SORTED INDEX clause or use the conventional path load instead of the direct path load.

SQL*Loader-259 could not escalate DDL share lock to exclusive on table name

Cause:	This error occurs when another user has a parse lock on the table, for example, when another user is doing a select on the table. The parse lock should clear momentarily.

Action:	Give the parse lock a chance to clear and then retry or else use the conventional path load.

SQL*Loader-260 index num is in an invalid state

Cause:	The specified index is in an invalid state.

Action:	Drop and re-create the index.

SQL*Loader-262 PIECED keyword (on column num) allowed only when path is direct

Cause:	The PIECED keyword cannot be used in a conventional path load.

Action:	Remove the PIECED keyword or use the direct path load.

SQL*Loader-263 PIECED column num must be last specified column in table name

Cause:	A column that is not the last column was specified as PIECED.

Action:	Remove the PIECED keyword or place the column last.

SQL*Loader-264 file mode token name parsed but ignored

Cause:	An obsolete file mode token was used in the control file. As of Release 1.1 of SQL*Loader, the file-processing options string is used to control file processing, rather than keywords like STREAM, RECORD, FIXED, and VARIABLE.

Action:	No action required. This message is informational. Removing the obsolete keywords will eliminate the message without changing the way in which the datafile is processed.

SQL*Loader-265 unable to get default character set name

Cause:	SQL*Loader was unable to locate the default character set name for the environment.

Action:	Supply a character set name with the CHARACTERSET keyword.

SQL*Loader-266 unable to locate character set handle for name

Cause:	SQL*Loader could not find the character set handle for the named character set.

Action:	Correct the character set name.

SQL*Loader-267 control file must be first datafile

Cause:	The control file is specified as containing data using the INFILE "*" clause, but other datafiles were named first.

Action:	Move the INFILE "*" clause so that it is the first datafile declared in the control file.

SQL*Loader-268 UNRECOVERABLE keyword may be used only in direct path

Cause:	The UNRECOVERABLE keyword can only be specified in the direct path load.

Action:	Use the direct path load or remove the keyword. (Conventional path loads are always recoverable).

SQL*Loader-269 Null string not allowed as clause comparison text

Cause:	A clause is being compared to a null string.

Action:	Modify the clause to compare to at least one character.

SQL*Loader-270 table name has index defined upon it

Cause:	Parallel load was specified into a table that has an index defined for it.

Action:	Drop the index or indexes defined for the table or do not use parallel load.

SQL*Loader-271 not a parallel load. Table level OPTIONS statement ignored

Cause:	A table-level OPTIONS statement was specified for a non-parallel load.

Action:	Remove the OPTIONS statement from the control file.

SQL*Loader-272 table level OPTIONS statement ignored

Cause:	In the parallel load option, the file specified on the command line overrides the file specified in the control file.

Action:	Remove the OPTIONS statement from the control file.