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: 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.
SQL*Loader-273: READBUFFERS may be used only in direct path
Cause: The READBUFFERS specification was not entered as part of a direct path.
Action: Use the direct path or remove the READBUFFERS specification from the control file.
SQL*Loader-274: at least 2 read buffers have to be specified
Cause: Fewer than 2 read buffers have been specified.
Action: Specify at least 2 read buffers in the READBUFFERS statement, in the control file.
SQL*Loader-275: data is in control file but \"INFILE *\" has not been specified
Cause: The INFILE specification was not entered in the control file.
Action: If data in the control file is to be read, specify INFILE * in the control file.
SQL*Loader-276: local storage option overrides global storage
Cause: A storage clause has been specified in the table level options statement and also in the global options statement.
Action: This is only a warning message. Table level options take precedence over global options. Drop the table level options statement if this is not the intent.
SQL*Loader-277: local file specification overrides global file specification
Cause: A filename has been specified in the table level options statement and also in the global options statement.
Action: This is only a warning message. Table level options take precedence over global options. Drop the table level options statement if this is not the intent.
SQL*Loader-278: incorrect file specification for parallel load
Cause: The filename used to perform the parallel load was entered incorrectly.
Action: Correct the filename and re-invoke parallel loader.
SQL*Loader-279: only APPEND mode allowed when parallel load specified
Cause: INSERT, REPLACE, or TRUNCATE mode was used in a parallel load specification.
Action: Change the control file to use the APPEND keyword and re-invoke the parallel loader.
SQL*Loader-280: bitmap index num (on table name) is not yet supported by SQL*Loader
Cause: Bitmap indexes are not supported by this version of SQL*Loader.
Action: Remove all bitmap indexes from the table and retry the load.
SQL*Loader-281: warning: ROWS parameter ignored in parallel mode
Cause: Specifying save points using the ROWS parameter is not supported for parallel loads.
Action: Remove the ROWS parameter from the command-line arguments or specify a non-parallel direct load to have save points performed.
00300-00399: DDL Parsing Messages
SQL*Loader-303: non-hex character encountered where hex char expected
Cause: A non-hexadecimal character was found in a hexadecimal string.
Action: Change it to the intended hexadecimal character.
SQL*Loader-304: illegal combination of non-alphanumeric characters
Cause: The control file contains a combination of non-alphanumeric characters that SQL*Loader does not recognize. For example, the combination != is recognized as "not equal", but the combination =! is not valid.
Action: Remove the unrecognized characters from the control file.
SQL*Loader-305: more than one end of file character encountered
Cause: The file contains multiple end-of-file marks.
Action: Remove the excess end-of-file characters.
SQL*Loader-306: token longer than max allowable length of num characters
Cause: The control file contains a single word or combination of characters (a token) that is longer than the maximum permissible value. The maximum possible value is shown. This error could result from missing spaces, so that multiple tokens are joined.
Action: Check that the proper control file is being executed. Separate tokens, if joined, or shorten the token.
SQL*Loader-307: Warning: conflicting lengths num1 and num2 specified for column name
Cause: The control file specifies two different lengths for the named column. There are three ways to specify the length of a field:
A conflict could occur between any two of these specifications (or among all three, but only two are shown).
A common cause of this error is the specification of some numeric datatype, such as INTEGER, when the numeric external form is intended (INTEGER EXTERNAL). The external form consists of character data, so it is considerably longer than the numeric form, which consists of binary data.
- with the POSITION keyword: POSITION(1:3)
- with the length specifier: CHAR(6)
- with the implied length of a datatype; for example, INTEGER
Action: No action is necessarily required, because SQL*Loader uses only one of the lengths. Check the log file under the heading "Len" in the table-description section to see which length was used. Adjusting the control file to produce uniform length specifications will remove the warning.
SQL*Loader-308: optional SQL string of column name must be in double quotes
Cause: A SQL string was found that was not quoted or in single quotes.
Action: Use double quotes for the SQL string, rather than single quotes.
SQL*Loader-350: syntax error at line num
Cause: num identifies the line in the control file at which the error occurred. This message is followed by another of the form
Expecting str1, found str2
where str1 is a description of what SQL*Loader expected in the control file, and str2 is what was found. Then SQL*Loader displays the offending line from the control file, indicating the location of the error in the line by a carat (^) or an asterisk (*). An example follows:
SQL*Loa er-350: Syntax error at line 28
Expecting column name, found keyword CHAR
col3 ENCLOSED BY '"', CHAR ENCLOSED "'",
Action: Compare the DDL syntax against the syntax diagrams in Oracle8 Server Utilities and make any necessary corrections.
00400-00499: Column Messages
SQL*Loader-401: end field position num must be greater than or equal to start num
Cause: The named field contains a (start:end) clause in which end is less than start.
Action: Modify the clause so that end is greater than or equal to start.
SQL*Loader-402: unable to determine length of column name.name from specification
Cause: The specified datatype does not have an implied length (for example, a numeric external or RAW datatype), it is not specified with delimiters, no length was specified, and a length cannot be determined from a POSITION clause.
Action: If a POSITION clause is specified, adding an end location to it produces a length specification. This clause then has the form
POSITION(start:end)
A length can also specified after the datatype, as in
Finally, the field could be specified with delimiters, or the datatype changed to one that has an implied length.
SQL*Loader-403: referenced column name not present in table name
Cause: The named column is not present in the given table.
Action: Correct the column name or table name.
SQL*Loader-404: column name present more than once in table name
Cause: The named column is specified more than once in a single INTO TABLE statement.
Action: Remove the extraneous column specification.
SQL*Loader-405: need termination delim with optional enclosure delim: column name.name
Cause: The named column was specified with an optional enclosure delimiter, but no termination delimiter. Enclosure delimiters can only be optional when termination delimiters are present.
Action: Specify a termination delimiter or make the enclosure delimiters non-optional.
SQL*Loader-406: if data is all generated, number to load cannot be ALL
Cause: When only generated data is loaded, a number to load must be given so SQL*Loader knows when to stop.
Action: Specify a number to load.
SQL*Loader-407: if data is all generated, number to skip is meaningless
Cause: When all data is generated, no file is read, and there are no records to skip.
Action: Remove the number to skip.
SQL*Loader-408: physical record stack overflow
Cause: An internal error has occurred.
Action: Contact customer support.
SQL*Loader-409: number to skip must be table-level, not load-level on continued loads
Cause: The SKIP parameter was specified on the command line or in the OPTIONS statement, but the load was specified as continued with CONTINUE_LOAD.
When a multiple-table direct load is interrupted, it is possible that a different number of records were loaded into each table. As a result, the number of records to skip must be specified for each table when continuing the load. In this case, the load is specified as continued with the CONTINUE_LOAD statement, and the number of records to skip is given in each INTO TABLE statement.
See also messages 410 and 411 for more information.
Action: Check the log file to determine the appropriate number of records to skip for each table and specify this number in the INTO TABLE statement for each table in a continued load or with the command-line SKIP parameter in a standard load.
SQL*Loader-410: number to skip must be load-level, not table-level
Cause: A SKIP clause was found in the INTO TABLE statement of a standard (non-continued) load.
In a standard load, specified with LOAD DATA, it is not possible to skip a different number of records for each table. The number of records to skip must be specified for the entire load by using the SKIP parameter on the command line or in the OPTIONS clause.
If table-level skip is required, because a different number of records were loaded into each table (only possible for a multiple-table direct load), then specify a continued load with the CONTINUE_LOAD statement.
See also messages 409 and 411 for more information.
Action: If the load was not a multiple-table, direct path load, then move the SKIP clause from the INTO TABLE statements to the command line or to the OPTIONS clause. Otherwise, specify the load as continued with CONTINUE_LOAD.
SQL*Loader-411: only a direct path load may be continued
Cause: The load is specified with CONTINUE_LOAD, but DIRECT=FALSE. CONTINUE_LOAD is only possible for a direct path load and is only necessary for a multiple-table, direct path load when a different number of records have been loaded into each table.
See also messages 409 and 410 for more information.
Action: If CONTINUE_LOAD is necessary, specify a direct load and put the number of records to skip in each INTO TABLE statement. Otherwise, use the command line or OPTIONS clause to specify the number of records to skip and use LOAD DATA instead of CONTINUE_LOAD.
SQL*Loader-412: more columns specified for table name than the maximum num
Cause: More columns were specified for the table than the maximum number allowed by the database.
Action: Remove the extraneous columns.
SQL*Loader-413: maximum number of constraints num exceeded on table name
Cause: An internal error has occurred.
Action: Contact customer support.
SQL*Loader-414: maximum number of triggers num exceeded on table name
Cause: An internal error has occurred.
Action: Contact customer support.
SQL*Loader-415: unimplemented database column type num on column name
Cause: An internal error has occurred.
Action: Contact customer support.
SQL*Loader-417: SQL string (on column name) not allowed in direct path
Cause: Because the direct path bypasses SQL processing, the SQL string cannot be used.
Action: Remove the SQL string or use the conventional path.
SQL*Loader-457: comparison text str of CONTINUEIF LAST must have length 1 not num
Cause: The comparison text is too long. It can only be one character.
Action: Reduce the comparison text to one character.
SQL*Loader-458: comparison text of CONTINUEIF LAST must be non-whitespace
Cause: The comparison text is a whitespace character (blank or tab).
Action: Change the comparison text to a non-whitespace character.
00500-00599: File I/O and Operating System Messages
SQL*Loader-500: unable to open file name
Cause: SQL*Loader could not open the named file.
Action: Check the operating system messages below this one in the log file.
SQL*Loader-501: unable to read file name
Cause: SQL*Loader could not read the named file.
Action: Check the operating system messages below this one in the log file.
SQL*Loader-502: unable to open log file for write name
Cause: SQL*Loader could not open the named file.
Action: Check that the file location is specified correctly and that write privileges for the file have been granted.
SQL*Loader-503: error appending extension to file name
Cause: SQL*Loader could not append the default extension to create the filename. The given name could be too long or contain illegal characters.
Action: Check the specified filename.
SQL*Loader-504: error skipping records in file name
Cause: SQL*Loader could not open the file or could not read from it.
Action: Check that the file is where it is expected and that read access has been granted.
SQL*Loader-506: unable to open bad file name
Cause: SQL*Loader could not open the named file.
Action: Check the errors below it in the log file for more information.
SQL*Loader-507: unable to open discard file name
Cause: SQL*Loader could not open the named file.
Action: Check the errors below this message in the log file for more information.
SQL*Loader-510: physical record in datafile name is longer than the maximum num
Cause: The datafile has a physical record that is too long.
Action: Use CONCATENATE or CONTINUEIF. Break up the physical records.
SQL*Loader-511: unable to initialize read functions
Cause: SQL*Loader could not initialize the read functions.
Action: Check the errors below this message in the log file for more information.
SQL*Loader-512: unable to free read buffer
Cause: An internal error has occurred.
Action: Contact customer support.
SQL*Loader-513: unable to close file name
Cause: SQL*Loader could not close the named file.
Action: Check the errors below this message in the log file for more information.
SQL*Loader-514: error getting elapsed time
Cause: SQL*Loader could not get the elapsed time from the system.
SQL*Loader-515: error getting CPU time
Cause: SQL*Loader could not get the CPU time from the system.
SQL*Loader-516: control file name has no contents
Cause: The named file was found to be empty.
Action: Check that the intended file was referenced and that it is not empty.
SQL*Loader-517: error decomposing filename name
Cause: SQL*Loader could not break down the filename into its component parts.
Action: Check the filename for illegal characters.
SQL*Loader-518: error reassembling filename name
Cause: SQL*Loader could not put the filename back together again from its components.
Action: Check the filename for illegal characters.
SQL*Loader-519: error num writing to filename name
Cause: SQL*Loader could not write to the named file. The error number displayed in the message is the one returned by the C language FWRITE function. More information can be obtained by accessing a C language reference manual for the system.
Action: Check that the file's location is where it is expected to be and that write privileges on it have been granted. Be sure that adequate disk space is available and that the disk quota is not exceeded.
SQL*Loader-520: lfimknam failed for file (name)
Cause: LFI failed to make a name object for the file.
Action: Contact Oracle Worldwide Support.
SQL*Loader-521: lfilini failed for file (name)
Cause: LFI failed to create or initialize a file object for the file.
Action: Contact Oracle Worldwide Support.
SQL*Loader-522: lfiopn failed for file (name)
Cause: LFI failed to open the file.
Action: Check for any possible operating system errors and/or potential memory problems.
SQL*Loader-523: error writing to file (name)
Cause: Could not write to specified file.
Action: Check the following:
If all of these conditions are satisfied, then retry the operation.
- the file actually resides in the specified location
- you have write privileges on the file
- you have sufficient disk space
- you have not exceeded your disk quota
00600-00619: Messages Returned During the Load
SQL*Loader-600: specified max. bind size num bytes must be num bytes to hold 1 row
Cause: The space needed to contain a single row is longer than the specified bind size.
Action: One solution is to increase the amount of space allowed for the bind array, using the BINDSIZE keyword on the command line or in the OPTIONS statement in the control file.
If the row contains VARCHAR or VARGRAPHIC data, specifying a maximum length for these fields can also reduce the amount of memory needed to buffer a row.
SQL*Loader-601: for INSERT option, table must be empty. error on name
Cause: A non-empty table is being loaded with the INSERT option.
Action: Use the REPLACE keyword to empty the old table and store the new data in its place. Use the APPEND keyword to leave the table's contents intact and add the new data to it.
SQL*Loader-602: maximum converted length num of column name.name is too big for bind array
Cause: The named column cannot undergo the specified character set conversion and still be placed in a contiguous piece of memory on the system.
Action: Specify a shorter data column or eliminate the conversion.
SQL*Loader-603: maximum length num of column name.name is too big for bind array
Cause: The named column cannot be put in a contiguous piece of memory on the system.
Action: Specify a shorter data column.
SQL*Loader-604: error occurred on an attempt to commit
Cause: An error occurred while trying to commit changes to the database.
Action: Look at the message listed below this one in the log file for more information.
SQL*Loader-605: non-data dependent Oracle error occurred load discontinued
Cause: An error occurred that is independent of the data. For example, an out-of-space condition. Because all further rows will be rejected, the load is discontinued. (If the error were data dependent, then other rows might succeed.)
Action: See the errors below this one in the log file for more information.
SQL*Loader-606: synonym name refers to an object on a remote database
Cause: The synonym specified in the INTO TABLE clause in the SQL*Loader control file specifies a remote object via a database link. Only a synonym for an existing local table can be specified in the INTO TABLE clause.
Action: Ensure that a local table name or a synonym for a local table is fully specified in the INTO TABLE clause. The table must already exist.
SQL*Loader-607: for INSERT option, partition must be empty. Error on table name, partition name
Cause: An attempt was made to use the INSERT option on a non-empty partition.
Action: Empty the partition, or use the REPLACE or TRUNCATE option.
00620-00649: Formatting Messages
These are errors in data described by free-format (TERMINATED, ENCLOSED) statements in the control file. Format errors occur when the data does not meet format specifications and might cause the loading of incorrect data into the database. A format error causes the record to be written to the bad file because an attempt to insert data failed.
SQL*Loader-620: initial enclosing character not found
Cause: A mandatory initial enclosure delimiter was not present. Either it is missing on the current field or the previous field is missing an identical closing delimiter.
Action: Supply the missing delimiters.
SQL*Loader-621: field in datafile exceeded maximum specified length
Cause: A field exceeded its maximum allowable length. The maximum length is either the length specified in the control file, or, for delimitable fields without a length specified, the maximum length of the corresponding database column (for CHAR, VARCHAR columns).
Action: Check for missing delimiters and/or shorten the field.
SQL*Loader-622: column not found before end of logical record (use TRAILING NULLCOLS)
Cause: The logical record ended before all specified fields were found.
Action: If the missing fields should be loaded as null, use the TRAILING NULLCOLS clause. Otherwise, correct the data.
SQL*Loader-623: logical record ended - second enclosure character not present
Cause: The logical end of record occurred before a second enclosure delimiter was found.
Action: Supply the missing delimiter.
SQL*Loader-624: no terminator found after TERMINATED and ENCLOSED field
Cause: No termination delimiter was found after the enclosed field ended.
Action: Supply the missing termination delimiter.
SQL*Loader-625: multi-byte character error in control file
Cause: Incomplete multi-byte character strings were found in the control file.
Action: Edit the control file to check that all multi-byte character data is valid.
SQL*Loader-640: variable length field was truncated
Cause: The end of the logical record was encountered before the end of a variable length field. The length of each variable-length field is embedded in the field, so SQL*Loader knows that more data should have been present.
Action: Check the data for inadvertent truncation and verify the control file specifications against the log file - the field may be starting in the wrong place.
SQL*Loader-641: invalid zoned decimal nibble
Cause: Each byte (character) in a zoned decimal field contains two 4-bit nibbles. Each nibble must have a valid value.
Action: Check the control file's specifications against the log file to ensure that the field location was specified correctly. Check the contents of the field.
SQL*Loader-642: relative start position > absolute field end position
Cause: A field specified as POSITION(*+n:y) had its relative start occur after the absolute position y.
Action: Check that a delimiter is not missing and that the values of n and y are correct.
00700-00799: Fatal Errors
SQL*Loader-700: out of memory while performing essential allocations num
Cause: SQL*Loader could not allocate the memory it needs.
Action: Check the operating system and process memory. Increase memory available to SQL*Loader if possible. Otherwise, wait until more memory becomes available.
SQL*Loader-701: out of memory while allocating bind array
Cause: SQL*Loader could not allocate memory for the bind array.
Action: Check the operating system and process memory. Increase memory available to SQL*Loader if possible. Otherwise, wait until more memory becomes available.
SQL*Loader-702: internal error - str
Cause: An internal error has occurred.
Action: Make a note of the message and contact customer support.
SQL*Loader-703: internal error: argument num
Cause: An internal error has occurred.
Action: Make a note of the message and the number, then contact customer support.
SQL*Loader-704: internal error: str num
Cause: An internal error has occurred.
Action: Make a note of the message and the number, then contact customer support.
SQL*Loader-705: internal error
Cause: An internal error has occurred.
Action: Contact customer support.
SQL*Loader-706: bad argument to ulerr num
Cause: An internal error has occurred.
Action: Contact customer support.
SQL*Loader-707: Sql*Loader exiting with return code=[%d]
Cause: An internal error has occurred.
Action: Contact customer support.
00900-00949: Direct Path Load Preparation Messages
SQL*Loader-901: error logging on to Oracle
Cause: An attempt was made to log on to Oracle in direct path load mode.
Action: Ensure that the instance is up and running. Check the Oracle messages below this one in the log file for more information.
SQL*Loader-902: error opening cursor: num
Cause: An internal error has occurred.
Action: Check the Oracle messages below this one in the log file and contact customer support.
SQL*Loader-903: database must be at least version num for direct path
Cause: The direct path load mode is being used with an incompatible database.
Action: Upgrade the database to the specified version or else use the conventional path load.
SQL*Loader-904: you cannot use the direct path when linked with v5 of the database
Cause: The direct path mode is being used after SQL*Loader has been linked with a Version 5 database.
Action: Use the conventional path.
SQL*Loader-905: error parsing SQL statement for upi: num
Cause: This is a header message.
Action: Check the message below this one in the log file for more information.
SQL*Loader-906: error executing SQL statement for upi: num
Cause: An internal error has occurred.
Action: Check the message below this one in the log file for more information.
SQL*Loader-907: error parsing insert statement on table name
Cause: Loader cannot insert into the specified table.
Action: Check that the table exists and that insert privileges on it have been granted.
SQL*Loader-908: unable to lock table name in exclusive mode due to Oracle error num
Cause: SQL*Loader could not get a DML exclusive lock on the table it needed.
Action: Check the message below this one in the log file for more information. Find the object number of the table in the catalog view USER_OBJECTS. Use the SQL*DBA MONITOR LOCK command to list all processes with outstanding locks. Identify the process that has the lock on the table. Then use the MONITOR PROCESS command to find out who is connected as the Oracle process holding the lock and get them to relinquish it, or simply wait and retry.
SQL*Loader-909: loader views must be loaded (as SYS) for direct path to be used
Cause: Database views required for the direct path mode are not present.
Action: The Oracle8 Server Administrator's Guide details how to run the required scripts as user SYS for loading the required views.
SQL*Loader-910: error binding input variables of upi: num
Cause: This is a header message.
Action: Check the message below this one in the log file for more information.
SQL*Loader-911: error defining output variables for upi: num
Cause: This is a header message.
Action: Check the message below this one in the log file for more information.
SQL*Loader-912: tables loaded through the direct path may not be clustered
Cause: A direct path load mode is being used to put data into a clustered table.
Action: Use the conventional path.
SQL*Loader-913: error fetching results of select statement (upi): num
Cause: This is a header message.
Action: Check the message below this one in the log file for more information.
SQL*Loader-914: error locking table name in exclusive mode
Cause: The direct path load mode could not lock the named table.
Action: Check the message below this one in the log file for more information. Check that the necessary privileges have been granted.
SQL*Loader-915: error closing cursor: num
Cause: This is a header message.
Action: Check the message below this one in the log file for more information.
SQL*Loader-916: error checking path homogeneity
Cause: To do a direct path load when the front end and back end of the database are on separate hardware systems, the systems must be identical, using the same machine, operating system, and character set. This error occurs when SQL*Loader detects a difference between the systems that will prevent a direct load from operating properly.
Action: Use a conventional path load for this configuration.
SQL*Loader-917: error parsing insert statement on table name
Cause: For security purposes, SQL*Loader generates a SQL INSERT statement and uses it to verify that the load specifications make sense and that the proper access privileges exist. This message occurs when the INSERT statement cannot be used.
Action: Check the Oracle messages below this one in the log file for more information. Check that all the columns to be loaded exist and that insert privileges on the table exist. Finally, check any SQL strings defined for the named table.
SQL*Loader-918: the catalog must be loaded (as SYS) for SQL*Loader to be used
Cause: The catalog is not loaded.
Action: Logon as user SYS and load the Oracle catalog and the views in the script ULVIEW.SQL.
SQL*Loader-919: error during upi fetch: num
Cause: An internal error has occurred.
Action: Check the message below this one in the log file for more information.
SQL*Loader-920: error deleting data from table name (due to REPLACE keyword)
Cause: The REPLACE option is specified in the control file but SQL*Loader could not delete the data from the table.
Action: Check the message below this one in the log file for more information.
SQL*Loader-921: NOT NULL column name.name has a NULLIF clause
Cause: A column that is NOT NULL in the database has a NULLIF clause in the control file.
Action: Remove the NULLIF clause.
SQL*Loader-922: NOT NULL column name.name has a default if clause which may evaluate to null
Cause: A column that is NOT NULL in the database has a NULLIF clause that may evaluate to null.
Action: Remove the NULLIF clause.
SQL*Loader-923: column name in table name is NOT NULL but is not being loaded
Cause: A column that is NOT NULL in the database is not being loaded, so every row will be rejected.
SQL*Loader-925: error while str
Cause: An internal error has occurred.
Action: Check the message below this one in the log file for more information. The table or column referenced may not be accessible.
SQL*Loader-926: OCI error while executing name for table name
Cause: An OCI error has occurred.
Action: Check the message below this one in the log file for more information. The table or column referenced may not be accessible.
SQL*Loader-927: table name does not exist
Cause: SQL*Loader could not find the named table. The specified table may not exist. On some systems, this message will also appear if the necessary privileges have not been granted.
Action: Check that the table exists, its name is spelled properly, and that the necessary privileges on it have been granted.
SQL*Loader-928: column name.name does not exist
Cause: SQL*Loader could not find the named table.
Action: Check that the column exists, its name is spelled properly, and the necessary privileges on it have been granted.
SQL*Loader-929: error parsing insert statement for table name
Cause: The table's insert statement caused a parse error.
Action: Check all SQL strings that were used.
SQL*Loader-930: error parsing insert statement for column name
Cause: The named column's INSERT statement caused a parse error.
Action: Check the message below this one in the log file for more information. Check the SQL string used for this column.
SQL*Loader-931: OCI error while binding variable for column name
Cause: An OCI error has occurred.
Action: Check the errors below it for more information. The SQL string for this column may be in error.
SQL*Loader-932: could not truncate table name
Cause: Truncation of the table was attempted and failed.
Action: Check the following errors for more information. Truncation due to referential constraints should not occur.
SQL*Loader-933: specified file name not part of database
Cause: The specified filename to load the table is not a database file.
Action: Specify a valid datafile.
SQL*Loader-934: incorrect datafile name specified for table tabnam
Cause: A datafile name was given to load the table that is not part of the tablespace in which the table resides.
Action: Specify a valid datafile.
SQL*Loader-935: error verifying required option for parallel load
Cause: An error was encountered because a required option was not found or was invalid.
Action: Correct the problem as described in the accompanying Oracle message.
SQL*Loader-936: unable to lock table name partition name due to ORACLE error num
Cause: Loader could not lock the partition it needed.
Action: Have the holder of the lock relinquish it or retry the operation.
SQL*Loader-937: parallel load requested and name has enabled triggers or constraints
Cause: A request was made for a parallel direct load, but the object to be loaded has an enabled constraint (check, referential) and/or enabled triggers.
Action: Disable the offending enabled constraints and/or triggers and retry the parallel direct load.
SQL*Loader-938: partition load requested and name has enabled triggers or constraints
Cause: A request was made for a direct load of a single partition, but the object to be loaded has an enabled constraint (check, referential) and/or enabled triggers.
Action: Disable the offending enabled constraints and/or triggers and retry the parallel direct load.
SQL*Loader-939: OCI error while name for table name partition name
Cause: This is a header message.
Action: Check the following errors for more information. The table or partition referenced may not be accessible.
SQL*Loader-940: UPI error while setting NCHAR bind attributes for column name table name
Cause: An error occured while setting the CHARSETFORM attribute of an NCHAR column.
Action: This is an internal error. Report to Oracle Worldwide Support.
SQL*Loader-941: error during describe of table name
Cause: An error occured while executing a DESCRIBE of a SELECT list on the given table. Check the error immediately preceding this error.
Action: Check to make sure that the table name, and all column names specified in the SQL*Loader control file are correct.
SQL*Loader-942: partition name not part of table name
Cause: The specified partition is not part of the specified table
Action: Check to make sure that the partition specified is correct (that it is indeed a partition of the specified table.
SQL*Loader-943: incorrect datafile name specified for table name partition name
Cause: The specified datafile is not in the tablespace of the specified partition. This error is most likely due to the use of FILE= keyword on a partitioned table. When loading all partitions of a partitioned table, the partitions must be in the same tablespace. When loading a single partition, the tablespace of the partition being loaded must be the same as the tablespace in which the specified datafile file resides.
Action: Check to make sure that the datafile specified via the FILE= keyword is in the tablespace of the partition being loaded.
00950-00999: Direct Path Load - Header Messages
These messages are informational. They describe the kind of error that has occurred. Check the messages below them in the log file for more detailed information.
SQL*Loader-950: error shipping data structures across 2-task
SQL*Loader-951: error calling once/load initialization
SQL*Loader-952: error calling once/datafile initialization
SQL*Loader-953: error shipping read buffer across 2-task
SQL*Loader-954: error shipping index to read buffer across 2-task
SQL*Loader-955: error calling col array build, block formatter
SQL*Loader-956: error calling once/datafile finishing
SQL*Loader-957: error shipping text string across 2-task
SQL*Loader-958: error popping data relocation address stack
SQL*Loader-959: error shipping buffer across 2-task
SQL*Loader-960: error escalating DDL share lock to exclusive
SQL*Loader-961: error calling once/load finishing
SQL*Loader-962: error setting user-side Ctrl-C handler
SQL*Loader-963: error clearing user-side Ctrl-C handler
SQL*Loader-964: error logging off Oracle
SQL*Loader-965: error num disabling constraint name of table name
SQL*Loader-966: error num disabling all triggers on table name
SQL*Loader-967: Oracle error: str
SQL*Loader-968: error disconnecting from Oracle
SQL*Loader-969: error performing filename translation on kernel side