SQL*Loader Messages 报错

SQL*Loader Messages

This chapter lists messages you might see when using SQL*Loader. SQL*Loader messages take the form:

SQL*Loader-code number: message text

Along with its own messages, SQL*Loader sometimes displays related messages issued by the Oracle Server. These messages can be found in the ORA message chapters in this manual. For more information on SQL*Loader, see Oracle8 Server Utilities.

00100-00199: Command Line Messages

SQL*Loader-100: syntax error on command line

Cause: Possible causes for this error include: placing a positional argument after keyword arguments, misspelling a keyword, not balancing parentheses or quotes, or leaving space between the operator, '=', and an argument.

Action: Check the command syntax and the spelling, then retry.

SQL*Loader-101: invalid argument for username/password

Cause: The username/password argument specified on the command line was not recognized. Another argument (not identified by a keyword) could be in the position where username/password is expected.

This error could also result from a spelling mistake. The password, if present, must be separated by a slash (/). No spaces can appear between the slash and username or password. Otherwise, SQL*Loader sees them as multiple arguments.

Action: Check the format of the username/password argument, which is the first argument on the command line, if arguments are given without keywords.

SQL*Loader-102: invalid control file name on command line

Cause: The control filename specified on the command line was not recognized. It could be misspelled, or another argument (not identified by a keyword) could be in its place. One possible cause is the existence of a space between username and password. See error 101, above.

Action: Check the spelling and position of the arguments on the command line.

SQL*Loader-103: invalid log file name on command line

Cause: The log file name specified on the command line was not recognized. It could be misspelled, or another argument (not identified by a keyword) could be in its place.

Action: Check the spelling and position of the arguments on the command line.

SQL*Loader-104: invalid bad file name on command line

Cause: The bad file name specified on the command line was not recognized. It could be misspelled, or another argument (not identified by a keyword) could be in its place.

Action: Check the spelling and position of the arguments on the command line.

SQL*Loader-105: invalid datafile name on command line

Cause: The datafile name specified on the command line was not recognized. It could be misspelled, or another argument (not identified by a keyword) could be in its place.

Action: Check the spelling and position of the arguments on the command line.

SQL*Loader-106: invalid discard file name on command line

Cause: The discard file name specified on the command line was not recognized. It could be misspelled, or another argument (not identified by a keyword) could be in its place.

Action: Check the spelling and position of the arguments on the command line.

SQL*Loader-107: invalid maximum number of discards

Cause: The argument's value is inappropriate, or another argument (not identified by a keyword) is in its place.

Action: Check the command line and retry.

SQL*Loader-108: invalid number of logical records to load

Cause: The argument's value is inappropriate, or another argument (not identified by a keyword) is in its place.

Action: Check the command line and retry.

SQL*Loader-109: invalid number of logical records to skip

Cause: The argument's value is inappropriate, or another argument (not identified by a keyword) is in its place.

Action: Check the command line and retry.

SQL*Loader-110: invalid maximum number of errors

Cause: The argument's value is inappropriate, or another argument (not identified by a keyword) is in its place.

Action: Check the command line and retry.

SQL*Loader-111: invalid number of rows for bind array or data saves

Cause: The argument's value is inappropriate, or another argument (not identified by a keyword) is in its place.

Action: Check the command line and retry.

SQL*Loader-112: invalid maximum bind array size

Cause: The argument's value is inappropriate, or another argument (not identified by a keyword) is in its place.

Action: Check the command line and retry.

SQL*Loader-113: invalid silent mode option

Cause: The only valid options for the SILENT command-line argument are ALL, ERROR, FEEDBACK, or HEADER. The argument could be misspelled, or another argument (not identified by a keyword) could be in its place.

Action: Check the command line and retry.

SQL*Loader-114: error in OPTIONS statement

Cause: Command line options specified in the control file with the OPTIONS clause were found to be incorrect.

Action: Check the format of the OPTIONS clause in the control file.

SQL*Loader-115: invalid direct path option

Cause: The only valid options for the DIRECT command-line argument are TRUE or FALSE. The argument could be misspelled, or another argument (not identified by a keyword) could be in its place.

Action: Check the command line and retry.

SQL*Loader-116: error prompting for password

Cause: An internal error has occurred.

Action: Contact customer support.

SQL*Loader-118: invalid parallel load option

Cause: The command-line argument used for the parallel load is incorrect.

Action: Use only TRUE or FALSE as the value for the parallel load option.

SQL*Loader-119: invalid parallel file (data file) name on command line

Cause: The command-line argument for the parallel file was entered incorrectly.

Action: Check the command line argument and retry the operation.

SQL*Loader-120: invalid _synchro option string

Cause: The command-line argument _synchro is incorrect.

Action: Use only one of the allowed modes: see ulminv[].

SQL*Loader-121: invalid skip_unusable_indexes option

Cause: The command line argument for SKIP_UNUSABLE_INDEXES is incorrect.

Action: Use only TRUE or FALSE as the value for the SKIP_UNUSABLE_INDEXES option.

SQL*Loader-122: invalid skip_index_maintenance option

Cause: The command line argument for SKIP_INDEX_MAINTENANCE is incorrect.

Action: Use only TRUE or FALSE as the value for the SKIP_INDEX_MAINTENANCE option. (Note: only on direct loads!)

00200-00299: DDL Syntax Messages

SQL*Loader-200: FORMAT clause should not be present - flat data files only

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: PIECE