Release 8.1.5
A67785-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8i Error Messages Release 8.1.5 A67785-01 |
|
This chapter lists messages generated by the SQL*Loader utility. For more information about this utility, refer to Oracle8i Utilities.
SQL*Loader-00100 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-00101 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-00102 Invalid control file name on command line
Cause: The control 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. 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-00103 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-00104 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: Correct it.
SQL*Loader-00105 Invalid data file 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-00106 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-00107 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-00108 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-00109 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-00110 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-00111 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-00112 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-00113 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-00114 Error in OPTIONS statement
Cause: Command line options specified in the SQL*Loader control file with the OPTIONS clause were found to be incorrect.
Action: Check the format of the OPTIONS clause in the SQL*Loader control file.
SQL*Loader-00115 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-00116 Error prompting for password
Cause: An internal error has occurred.
Action: Contact Oracle Customer Support.
SQL*Loader-00118 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-00119 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-00121 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-00122 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!)
SQL*Loader-00123 specified value for bindsize(number) less than readsize(number)
Cause: The command line argument specified for BINDSIZE was less than the value of READSIZE.
Action: No action is required. SQL*Loader automatically adjusts the value of BINDSIZE to equal the value of READSIZE.
SQL*Loader-00124 specified value for readsize(number) less than bindsize(number)
Cause: The command line argument specified for READSIZE was less than the value of BINDSIZE.
Action: No action is required. SQL*Loader automatically adjusts the value of READSIZE to equal the value of BINDSIZE.
SQL*Loader-00125 specified value for readsize(number) less than max_record_size(number)
Cause: The command line argument specified for read size was less than the value of MAX_RECORD_SIZE.
Action: No action is required. SQL*Loader automatically adjusts the value of read size to equal the value of MAX_RECORD_SIZE.
SQL*Loader-00126 Invalid read 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-00127 Invalid maximum record 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-00200 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 SQL*Loader control file or comment it out.
SQL*Loader-00250 Work data sets are not used by SQL*Loader
Cause: The SQL*Loader control file contains a WRKDDN statement. SQL*Loader ignores this clause. This is an informational message.
Action: No action required.
SQL*Loader-00251 Sort devices are not used by SQL*Loader
Cause: The SQL*Loader control file contains a SORTDEVT statement. SQL*Loader ignores this clause. This is an informational message.
Action: No action required.
SQL*Loader-00252 Sort data sets are not used by SQL*Loader
Cause: The SQL*Loader control file contains a SORTNUM statement. SQL*Loader ignores this clause. This is an informational message.
Action: No action required.
SQL*Loader-00253 DB2 partition number has no significance -- ignored
Cause: The SQL*Loader control file contains a PART statement. SQL*Loader ignores this clause. This is an informational message.
Action: No action required.
SQL*Loader-00254 Cannot have DISCARDFILE specs here when multiple data files
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-00255 Log file for error recovery not used by SQL*Loader
Cause: The SQL*Loader control file contains a LOG statement. SQL*Loader ignores this clause. This is an informational message.
Action: No action required.
SQL*Loader-00256 SORTED INDEXES option allowed only for direct path
Cause: The SQL*Loader 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 SQL*Loader control file, or comment it out.
SQL*Loader-00257 TERMINATED BY EOF option not valid with ENCLOSED BY option
Cause: A field description in the SQL*Loader control file contains both the TERMINATED BY EOF and the ENCLOSED BY options. These options are mutually exclusive.
Action: Remove either or both of the clauses.
SQL*Loader-00258 Maximum number of SORTED INDEXES (number) exceeded on table string
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-00259 Could not escalate DDL share lock to exclusive on table string
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-00260 TERMINATED BY EOF option available only with LOBFILE option
Cause: The TERMINATED BY EOF option can be used only when describing data to be loaded from a LOBFILE. It cannot be specified at the table level and it cannot be for data in "regular" datafiles.
Action: Verify that you have specified the correct option for TERMINATED BY and verify that the TERMINATED BY option is specified for the correct fields.
SQL*Loader-00261 illegal use of TERMINATED BY for RAW field
Cause: The TERMINATED BY option cannot be used for loading data of type RAW from the datafile. The only exception is when loading RAW data from LOBFILES. In that case, you may specify the TERMINATED BY EOF option.
Action: Remove the TERMINATED BY option from the RAW field in the SQL*Loader control file.
SQL*Loader-00262 PIECED keyword (on column string) 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-00263 PIECED column string must be last specified column in table string
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-00264 File mode token string parsed but ignored
Cause: An obsolete file mode token was used in the SQL*Loader 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-00265 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-00266 Unable to locate character set handle for string.
Cause: SQL*Loader could not find the character set handle for the named character set.
Action: Correct the character set name.
SQL*Loader-00267 Control file must be first data file.
Cause: The SQL*Loader 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 SQL*Loader control file.
SQL*Loader-00268 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-00269 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-00270 TERMINATED BY EOF valid only for CHAR or RAW datatypes
Cause: A field description in the SQL*Loader control file used the TERMINATED BY EOF option when the field was not a RAW or CHAR datatype.
Action: Modify the SQL*Loader control file to either remove the TERMINATED BY EOF clause or change the datatype for the field to be CHAR or RAW.
SQL*Loader-00271 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 SQL*Loader control file.
SQL*Loader-00272 Table level OPTIONS statement ignored.
Cause: In the parallel load option, the file specified on the command line overrides the file specified in the SQL*Loader control file.
Action: Remove the OPTIONS statement from the SQL*Loader control file.
SQL*Loader-00273 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 SQL*Loader control file.
SQL*Loader-00274 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 SQL*Loader control file.
SQL*Loader-00275 Data is in control file but "INFILE *" has not been specified.
Cause: The INFILE specification was not entered in the SQL*Loader control file.
Action: If data in the SQL*Loader control file is to be read, specify INFILE * in the SQL*Loader control file.
SQL*Loader-00276 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. Table level options take precedence over global options. This is a warning message.
Action: Drop the table level options statement if this is not the intent.
SQL*Loader-00277 Local file specification overrides global file specification.
Cause: A file name has been specified in the table level options statement and also in the global options statement. Table level options take precedence over global options. This is a warning message.
Action: Drop the table level options statement if this is not the intent.
SQL*Loader-00278 Incorrect file specification for parallel load.
Cause: The file name used to perform the parallel load was entered incorrectly.
Action: Correct the file name and re-invoke parallel loader.
SQL*Loader-00279 Only APPEND mode allowed when parallel load specified.
Cause: INSERT, REPLACE, or TRUNCATE mode was used in a parallel load specification.
Action: Change the SQL*Loader control file to use the APPEND keyword and re-invoke the parallel loader.
SQL*Loader-00280 table string is a temporary table
Cause: The SQLLDR utility does not load temporary tables. Note that if SQLLDR did allow loading of temporary tables, the data would disappear after the load completed.
Action: Load the data into a non-temporary table.
SQL*Loader-00281 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.
SQL*Loader-00282 Unable to locate character set handle for character set ID (number).
Cause: SQL*Loader could not find the character set handle for the given character set ID.
Action: The character set ID was obtained from the database server, the SQL*Loader client does not have knowledge of the given character set ID. Possible mismatch of NLS data on the client and server side.
SQL*Loader-00283 file processing string 'string' ignored for INFILE *
Cause: The SQL*Loader control file specified INFILE * for a load data file along with an optional file processing string. This message is a warning that the file processing string will be ignored since SQLLDR will expect the data to have the same record format as the SQL*Loader control file.
Action: If the data in the SQL*Loader control file is in the same format as the rest of the SQL*Loader control file, then you do not need to do anything. Removing the file processing string will get rid of this error message. If the data in the SQL*Loader control file has a different record format, then you need to copy the data into a separate file and use that file's name in the INFILE clause.
SQL*Loader-00303 Non-hex character encountered where hex char expected
Cause: A non-hex character was found in a hexadecimal string.
Action: Change it to the intended hexadecimal character.
SQL*Loader-00304 Illegal combination of non-alphanumeric characters
Cause: The SQL*Loader 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-00305 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-00306 Token longer than max allowable length of number chars
Cause: The SQL*Loader 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 SQL*Loader control file is being executed. Separate tokens, if joined, or shorten the token.
SQL*Loader-00307 Warning: conflicting lengths number and number specified for column string table string
Cause: The SQL*Loader 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.
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 SQL*Loader control file to produce uniform length specifications will remove the warning.
SQL*Loader-00308 Optional SQL string of column string 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-00350 Syntax error at line number.
Cause: number identifies the line in the SQL*Loader 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 SQL*Loader control file, and str2 is what was found. Then SQL*Loader displays the offending line from the SQL*Loader control file, indicating the location of the error in the line by a carat (^). or an asterisk (*). An example follows:
SQL*Loader-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 inOracle8i Utilities and make any necessary corrections.
SQL*Loader-00401 End field position number must be greater than or equal to start number
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-00402 Unable to determine length of column string 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:
INTEGER EXTERNAL (6)
Finally, the field could be specified with delimiters, or the datatype changed to one that has an implied length.
SQL*Loader-00403 Referenced column string not present in table string.
Cause: The named column is not present in the given table.
Action: Correct the column name or table name.
SQL*Loader-00404 Column string present more than once in string's INTO TABLE block.
Cause: The named column is specified more than once in a single INTO TABLE statement.
Action: Remove the extraneous column specification.
SQL*Loader-00405 Need termination delim with optional enclosure delim: column string table string
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-00406 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-00407 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-00408 Physical record stack overflow
Cause: An internal error has occurred.
Action: Contact Oracle Customer Support.
SQL*Loader-00409 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-00410 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-00411 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-00412 More columns specified for table string than the maximum (number)
Cause: More columns were specified for the table than the maximum number allowed by the database.
Action: Remove the extraneous columns.
SQL*Loader-00413 NULLIF or DEFAULTIF clause specified for filler field string in table string.
Cause: A NULLIF or DEFAULTIF clause was specified in the SQL*Loader control file for the named filler field. These options cannot be specified for filler fields.
Action: Remove the NULLIF or DEFAULTIF clause from the field definition.
SQL*Loader-00414 no columns to load for table string
Cause: There were no fields in the datafile to be loaded for the table. Probably all fields were identified as FILLER fields.
Action: Verify that the FILLER attribute was set correctly for the fields.
SQL*Loader-00415 column string in table string cannot use and be the object of an SDF or LOBFILE.
Cause: The named column is identified as the target of a secondary datafile (SDF) or LOBFILE clause. However, the column also gets its value from an SDF or LOBFILE. If a field name is named in an SDF or LOBFILE clause, then that field cannot have an SDF or LOBFILE clause.
Action: Verify that the SDF and LOBFILE clauses in the SQL*Loader control file name the correct fields. Also verify that the SDF and LOBFILE clauses are specified for the correct field.
SQL*Loader-00416 SDF caluse for field string in table string references a non existent field.
Cause: The secondary datafile clause for the field identified another field that does not exist in the table definition for the SQL*Loader control file.
Action: Verify the definition of the secondary datafile to make sure it identifies the intended field.
SQL*Loader-00417 SQL string (on column string) 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-00418 Bad datafile datatype for column string
Cause: The datatype in the data file specified for the column cannot be used to load the column. This message is often displayed for columns that need to be loaded with special features. For example, BFILE columns can only be loaded via the BFILE directive in the control file; same goes for REF fields in the SQL*Loader control file. Similarly, REF columns can only be loaded with the REF datatype in the SQL*Loader control file.
Action: Determine the datatype of the column in the database check the documentation for the correct mechanisms to use to load columns of that type.
SQL*Loader-00419 input datatype for column string is not supported when loading varrays
Cause: The datatype in the SQL*Loader control file for the column is cannot be used to load data in a VARRAY.
Action: Use a different datatype.
SQL*Loader-00420 unsupported datatype conversion requested for column string in table string
Cause: The column needs to have its data converted to another datatype before loading the data. The required conversion cannot be done by SQLLDR.
Action: Verify that the correct datatype was specified for the column.
SQL*Loader-00421 error converting data
Cause: This message can be displayed as one of the reasons for rejecting a row. The SQLLDR utility was attempting to convert data for the column from its datatype in the datafile to the datatype for the column in the database. This message should be followed with another message describing the conversion error.
Action: Correct the data in the datafile so that it can be converted.
SQL*Loader-00422 constant element count of number for column string is greater than maximum, number
Cause: The number of elements specified for a VARRAY column in a table is greater than the maximum number of elements allowed for the type of the VARRAY column.
Action: Increase the number of elements allowed for the type or remove unwanted elements from the datafile.
SQL*Loader-00423 element count is greater than maximum allowed for the column
Cause: When building a VARRAY from the datafile, SQL*Loader encountered more VARRAY elements than are allowed for the column.
Action: The previous error messages contain the name of the column and the row number containing the bad data.
SQL*Loader-00424 table string makes illegal reference to collection field string
Cause: A WHEN, OID or SID clause for the table refers to a field declared inside of a collection.
Action: Move the data containing the value for a SID or OID clause outside of the collection definition.
SQL*Loader-00425 column string makes illegal reference to collection field string
Cause: A clause, such as NULLIF or BFILE clause, for the column refers to a field declared inside of a collection.
Action: Move the data containing the value for a SID or OID clause outside of the collection definition.
SQL*Loader-00426 count of elements in VARRAY string comes after the data for the varray
Cause: The COUNT clause for a VARRAY field indicates that the count of elements in the VARRAY is stored in another data field. However, that data field comes after the VARRAY data in the datafile. Since finding the count field would require SQL*Loader to know the number of elements in the VARRAY first, SQL*Loader requires that the count field come before the VARRAY data.
Action: Move the count field to be before the collection data in the data file.
SQL*Loader-00427 a field condition references a non-scalar field or a LOB field string
Cause: The field condition is referencing a field which is either a nested table, VARRAY, column object, LOB or BILE field. These fields with these types cannot be referenced by other fields.
Action: Correct the NULLIF, DEFAULTIF, or WHEN clauses to reference only non-LOB scalar data fields.
SQL*Loader-00428 count for field string not stored in character or integer field
Cause: The count clause for a field references another field, but the referenced field is not a character or integer datatype.
Action: Modify the count field so that it reference a a data field that has the count in an integer or character format.
SQL*Loader-00429 insufficient number of elements found for varray
Cause: The COUNT directive was specified for a VARRAY, but the number of elements found is less than the number specified by the COUNT directive.
Action: Correct the data so that the count and the number of elements agree.
SQL*Loader-00430 NULL nested table element is not allowed
Cause: A row in a nested table was set to NULL. Nested tables cannot contain NULL fields.
Action: Correct the data so that there are no NULL rows in the nested table.
SQL*Loader-00431 illegal NULLIF or DEFAULTIF clause specified for nested table column string
Cause: Rows in a nested table cannot be set to NULL. SQLLDR displays this error when a NULLIF clause was specified for the element that defines the row that makes up a nested table. SQLLDR also displays this error if a DEFAULTIF clause is specified for an element that is a named type, since SQLLDR will set a named type to NULL if the DEFAULTIF evaluates to TRUE.
Action: Use only legal clauses.
SQL*Loader-00432 converted data too large
Cause: This message is preceded by a message identifying a row and column. It is displayed when there is insufficient room to convert the data from the datatype in the input file to the datatype for the column in the database.
Action: Modify the data so that it fits in the database field.
SQL*Loader-00440 Invalid table specified as scope of a REF
Cause: As part of the REF directive one specifies the table name or another fields name which contains the table name of the table which the REF references.
Action: Make sure that the right referenced table name is specified.
SQL*Loader-00456 end of collection found after number elements when looking for number elements
Cause: A count value was specified for a VARRAY or nested table column and the number of rows found is less than the number of rows specified.
Action: Verify that the count field has the correct value and that there is no missing data for the collection.
SQL*Loader-00457 Comparison text of CONTINUEIF LAST must have length 1 not number
Cause: The comparison text is too long. It can only be one character.
Action: Reduce the comparison text to one character.
SQL*Loader-00458 Comparison text ('string') of CONTINUEIF LAST must be non-whitespace
Cause: The comparison text is a white space character (blank or tab).
Action: Change the comparison text to a non-white space character.
SQL*Loader-00459 error fetching numeric value for sequence on column (string)
Cause: An attempt was made to retrieve a non-numeric value for a sequenced column.
Action: Verify that the data for the sequenced column is numeric. Then retry the operation.
SQL*Loader-00460 Column (string), form of use (number) does not match char set id of (number)
Cause: The given column with the given form of use does not have the same character set ID as a previous column with the same form of use.
Action: This should not happen. Contact Oracle Customer Support and supply the following information: DDL for the table being loaded, and the SQL*Loader control file.
SQL*Loader-00461 direct path loading of datatype for column string not supported
Cause: The datatype for the specified column is one that cannot be loaded with direct path.
Action: If the datatype is supported with conventional path, load the table using conventional path.
SQL*Loader-00462 error inserting LOB into table string; column string; row number
Cause: An error occurred while attempting to write a LOB into a row. The row will remain in the table and the LOB column will be set to NULL. Loading of other LOB columns will continue.
Action: This message is followed by another message describing why the LOB could not be stored. If you want to attempt to try and store the LOB from another utility or program, you can use the information from the message to find the data for the LOB was in the datafile.
SQL*Loader-00463 secondary data file for LOB is string
Cause: This message identifies the secondary datafile that was in use for populating the LOB when an error occurred.
Action: No action required.
SQL*Loader-00464 file offset for beginning of lob is string
Cause: This message identifies the offset into the secondary datafile that contains the start of the LOB that was being written when an error occurred.
Action: No action required.
SQL*Loader-00465 string directive expects number arguments, number found.
Cause: A directive such as COUNT() or BFILE() was specified in the control file. The directive specifies a fixed number of arguments, but the SQL*Loader control file contains a different number of arguments.
Action: Correct the SQL*Loader control file so that the directive contains the correct number of arguments.
SQL*Loader-00466 Column string does not exist in table string.
Cause: The SQL*Loader control file specified a table column that does not exist.
Action: Check the name of the table column.
SQL*Loader-00467 attribute string does not exist in type string for table string.
Cause: The SQL*Loader control file specified an attribute that does not exist for the specified type. The table that contains the type is also identified in the error message.
Action: Verify that the correct table in the correct schema is named in the SQL*Loader control file. Also verify that the column name is spelled correctly.
SQL*Loader-00468 OID directive expects 1 argument, number found.
Cause: More than one argument was specified for an OID clause.
Action: Specify the name of the field containing the value to use for the OID. If the OID for the table is user-defined, then do not use the OID clause in the control file.
SQL*Loader-00469 SID directive expects 1 argument, number found.
Cause: More than one argument was specified for a SID clause.
Action: Only specify the name of the field containing the value to use for the SID in the SID clause.
SQL*Loader-00470 table string does not have system generated OID
Cause: You specified an OID clause for a table but the table is either not an object table or the table is an object table but the OIDs for the rows are not system generated.
Action: Verify that the you are loading the correct table. If you are, then you must not specify the OID clause for this table. You should use the OID clause only when the table is an object table, has system generated OIDs and when you want to specify OIDs to be assigned to each row of the table.
SQL*Loader-00471 OID clause has an argument that is CONSTANT
Cause: You specified a CONSTANT as an argument in the OID clause. Since every OID must be unique, you are not allowed to specify a constant.
Action: Store the OID for each row in a filler field and specify the name of the filler field as an argument.
SQL*Loader-00472 collections can contain only one non FILLER field specification.
Cause: More than one non filler field specification is found in a collection field's member field list.
Action: See the correct syntax in Oracle8i Utilities. If indeed there is more than one attribute that makes up the particular collection, then it must be a collection of a object type which needs to be specified using the COLUMN OBJECT field specification syntax.
SQL*Loader-00473 nesting of collections is not allowed.
Cause: Nesting of one collection type field description within another is not allowed.
Action: Verify that indeed collection nesting is attempted in the SQL*Loader control file. Correct the mistake.
SQL*Loader-00474 no value set for dynamic file for column string in table string row number
Cause: The data for the named column is in a dynamic LOBFILE or secondary data file. This message is returned when the field containing the name of the file with the data for this field has not been set or is NULL. This could be because the record in the datafile does not match the format described by the SQL*Loader control file.
Action: Correct any errors in the datafile or the SQL*Loader control file.
SQL*Loader-00475 field for dynamic file name is string in table string
Cause: This message is always displayed after message 474.
SQL*Loader-00476 count of elements for collection is not set or null, 0 will be used
Cause: This message is displayed following a message that identifies the column and row that contained the problem. The message indicates that the collection field named in the previous message has the count of elements in the collection stored in another field. This message is displayed if the field containing the count does not have a value or is set to NULL. When this happens, SQL*Loader uses 0 as the number of elements.
Action: If 0 is not the count of elements for the collection, correct the data in the data file.
SQL*Loader-00477 REF directive for field string requires at least two arguments
Cause: The SQL Loader control file contains a REF directive for the field, but only one argument was supplied for the directive. The REF directive always requires at least two arguments.
Action: Supply the missing argument to the REF directive. Remember that you must always supply a table name to the REF directive even if the REF is scoped.
SQL*Loader-00478 unable to continue due to missing filename for LOBFILE or SDF
Cause: The name for a LOBFILE or secondary data file is either missing or NULL for the current row. SQL*Loader is unable to continue loading since it cannot determine how to get the LOB for the next row.
Action: Correct the data file so that there are valid values for all fields containing the names of LOBFILEs and secondary data files.
SQL*Loader-00479 REF directive for column string expects number arguments; found number.
Cause: The number of arguments in the REF directive for the column is incorrect.
Action: Specify the correct number of arguments for REF. Remember that the REF directive always requires a table name. Also, primary key REFs require one arguments for each field in the primary key.
SQL*Loader-00500 Unable to open file (string)
Cause: SQL*Loader could not open the named file.
Action: Check the operating system messages below this one in the log file.
SQL*Loader-00501 Unable to read file (string)
Cause: SQL*Loader could not read the named file.
Action: Check the operating system messages following this message in the log file.
SQL*Loader-00502 unable to open data file 'string' for field string table string
Cause: An attempt to open a LOBFILE or secondary datafile failed.
Action: Check the operating system messages following this message for information on why the open failed. Verify that the correct name is specified for the LOBFILE or secondary datafile.
SQL*Loader-00503 Error appending extension to file (string)
Cause: SQL*Loader could not append the default extension to create the file name. The given name could be too long or contain illegal characters.
Action: Check the specified file name.
SQL*Loader-00504 Error skipping records in file (string)
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-00505 error reading LOBFILE
Cause: An attempt to read a secondary datafile failed.
Action: Check the operating system message that follows this message for more information.
SQL*Loader-00506 formatting error number reading SDF or LOBFILE string for column string in table string
Cause: The record format of the named LOBFILE or SDF file is incorrect.
Action: Fix the record formatting problems in the file.
SQL*Loader-00507 unexpected EOF reading SDF or LOBFILE string for column string in table string
Cause: The end of file was reached for a secondary datafile or LOBFILE before the data for the current row was found.
Action: If the file is a LOBFILE, verify the correct datatype was specified for the field. If the file is a secondary datafile, make sure the record format is specified correctly in the SQL*Loader control file.
SQL*Loader-00508 record formating error in data file string
Cause: The data found in the datafile does not correspond to the record format in the SQL*Loader control file.
Action: Verify that all records in the datafile match the format as described in the SQL*Loader control file.
SQL*Loader-00510 Physical record in data file (string) is longer than the maximum(number)
Cause: The datafile has a physical record that is too long.
Action: Use CONCATENATE or CONTINUEIF. Break up the physical records.
SQL*Loader-00511 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-00512 Unable to free read buffer
Cause: An internal error has occurred.
Action: Contact Oracle Customer Support.
SQL*Loader-00513 Unable to close file (string)
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-00514 Error getting elapsed time
Cause: SQL*Loader could not get the elapsed time from the system.
Action: No action required.
SQL*Loader-00515 Error getting CPU time
Cause: SQL*Loader could not get the CPU time from the system.
Action: No action required.
SQL*Loader-00516 Control file (string) 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-00517 Error decomposing file name (string)
Cause: SQL*Loader could not break down the file name into its component parts.
Action: Check the file name for illegal characters.
SQL*Loader-00518 Error reassembling file name (string)
Cause: SQL*Loader could not put the file name back together again from its components.
Action: Check the file name for illegal characters.
SQL*Loader-00520 lfimknam failed for file (string)
Cause: LFI failed to make a name object for the file.
Action: Contact Oracle Customer Support.
SQL*Loader-00521 lfilini failed for file (string)
Cause: LFI failed to create or initialize a file object for the file.
Action: Contact Oracle Customer Support.
SQL*Loader-00522 lfiopn failed for file (string)
Cause: LFI failed to open the file.
Action: Check for any possible operating system errors and/or potential memory problems.
SQL*Loader-00523 error number writing to file (string)
Cause: Could not write to specified file.
Action: Check the following:
If all of these conditions are satisfied, then retry the operation.
SQL*Loader-00524 partial record found at end of datafile (string)
Cause: An incomplete record was found at the end of the indicated datafile.
Action: Make sure the last record in the datafile is complete and has the correct terminating character(s). Also, if fixed-length records are in use, verify that no record exceeds the platform-specific length for a single record.
SQL*Loader-00525 OCI return status: success
Cause: The message describes the status code returned by an OCI call.
Action: See surrounding messages for more information.
SQL*Loader-00526 OCI return status: success with info
Cause: The message describes the status code returned by an OCI call.
Action: See surrounding messages for more information.
SQL*Loader-00527 OCI return status: no data
Cause: The message describes the status code returned by an OCI call.
Action: See surrounding messages for more information.
SQL*Loader-00528 OCI return status: error
Cause: The message describes the status code returned by an OCI call.
Action: See surrounding messages for more information.
SQL*Loader-00529 OCI return status: invalid handle
Cause: The message describes the status code returned by an OCI call.
Action: See surrounding messages for more information.
SQL*Loader-00530 OCI return status: need data
Cause: The message describes the status code returned by an OCI call.
Action: See surrounding messages for more information.
SQL*Loader-00531 OCI return status: still executing
Cause: The message describes the status code returned by an OCI call.
Action: See surrounding messages for more information.
SQL*Loader-00532 OCI return status: continue
Cause: The message describes the status code returned by an OCI call.
Action: See surrounding messages for more information.
SQL*Loader-00533 OCI return status: unknown, value is number
Cause: An unknown status was returned by an OCI call.
Action: See surrounding messages for more information.
SQL*Loader-00600 Specified max. bind size number bytes must be number 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 SQL*Loader 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-00601 For INSERT option, table must be empty. Error on table string
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-00602 Maximum converted length number of column string 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-00603 Maximum length number of column string 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-00604 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-00605 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-00606 Object string in INTO TABLE clause is not a local table
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-00607 partition not empty for INSERT option; table string, partition string
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.
SQL*Loader-00608 subpartition not empty for INSERT option; table string, subpartition string
Cause: An attempt was made to use the INSERT option on a non-empty subpartition.
Action: Empty the subpartition, or use the REPLACE or TRUNCATE option.
SQL*Loader-00620 Initial enclosure 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-00621 Field in data file exceeds maximum length
Cause: A field exceeded its maximum allowable length. The maximum length is either the length specified in the SQL*Loader 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-00622 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-00623 second enclosure string not present
Cause: The logical end of record or the end of a LOBFILE was reached before a second enclosure delimiter was found.
Action: Correct the datafile to include the missing delimiter.
SQL*Loader-00624 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-00625 Multibyte character error in control file.
Cause: Incomplete multi-byte character strings were found in the SQL*Loader control file.
Action: Edit the SQL*Loader control file to check that all multi-byte character data is valid.
SQL*Loader-00626 Character set conversion buffer overflow.
Cause: A conversion from the datafile character set to the client character set required more space than that allocated for the conversion buffer. The size of the conversion buffer is limited by the maximum size of a varchar2 column.
Action: The input record is rejected. The data will not fit into the column.
SQL*Loader-00627 Character set conversion graph not available.
Cause: A conversion from the datafile character set to the client character failed due to the conversion graph not being available.
Action: Contact Oracle Customer Support. Check NLSRTL installation.
SQL*Loader-00628 Character set conversion error.
Cause: A character set conversion error occurred.
Action: Contact Oracle Customer Support. Check NLSRTL installation. Provide a reproducible test case.
SQL*Loader-00640 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 SQL*Loader control file specifications against the log file; the field may be starting in the wrong place.
SQL*Loader-00641 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 SQL*Loader 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-00642 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.
SQL*Loader-00643 error executing INSERT statement for table string
Cause: A fatal error occurred while attempting to insert data into the table.
Action: Refer to the messages that follow for more information. If you specified SQL stings for any of your columns, verify that strings are correct. Specifically, check for balanced parenthesis and correct use of quotation marks. Another format error
SQL*Loader-00644 end of logical record found when reading length of varying length field
Cause: While attempting to read the length portion of a varying length field, then end of the logical record was reached.
Action: Verify that the SQL*Loader control file describes the data correctly and that the data in the datafile matches the description in the SQL*Loader control file.
SQL*Loader-00645 error converting character length field to a number
Cause: An error occurred while attempting to convert the characters containing the count portion of a VARCHARC or VARRAWC field.
Action: Verify that the count portion for the column has the correct value.
SQL*Loader-00700 Out of memory while performing essential allocations [number]
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-00702 Internal error - string
Cause: An internal error has occurred.
Action: Make a note of the message and contact Oracle Customer Support.
SQL*Loader-00703 Internal error: argument number
Cause: An internal error has occurred.
Action: Make a note of the message and the number, then contact Oracle Customer Support.
SQL*Loader-00704 Internal error: string [number]
Cause: An internal error has occurred.
Action: Make a note of the message and the number, then contact Oracle Customer Support.
SQL*Loader-00705 Internal error
Cause: An internal error has occurred.
Action: Contact Oracle Customer Support.
SQL*Loader-00706 Bad argument to ulerr [number].
Cause: An internal error has occurred.
Action: Contact Oracle Customer Support.
SQL*Loader-00707 Sql*Loader exiting with return code=[number].
Cause: An internal error has occurred.
Action: Contact customer support.
SQL*Loader-00901 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-00902 Error opening cursor: [number]
Cause: An internal error has occurred.
Action: Check the Oracle messages below this one in the log file and contact Oracle Customer Support.
SQL*Loader-00903 Database must be at least version number.number.number.number.number 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-00904 You cannot used 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-00905 Error parsing SQL statement for upi: [number]
Cause: This is a header message.
Action: Check the message below this one in the log file for more information.
SQL*Loader-00906 Error executing SQL statement for upi: [number]
Cause: An internal error has occurred.
Action: Check the message below this one in the log file for more information.
SQL*Loader-00908 Unable to lock table string due to ORACLE error number
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 wait and retry.
SQL*Loader-00909 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 Oracle8i Administrator's Guide details how to run the required scripts as user SYS for loading the required views.
SQL*Loader-00910 Error binding input variables for upi: [number]
Cause: This is a header message.
Action: Check the message below this one in the log file for more information.
SQL*Loader-00911 Error defining output variable(s) for upi: [number]
Cause: This is a header message.
Action: Check the message below this one in the log file for more information.
SQL*Loader-00913 Error fetching results of select statement (upi): [number]
Cause: This is a header message.
Action: Check the message below this one in the log file for more information.
SQL*Loader-00914 Error locking table string in exclusive mode.
Cause: The direct path 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-00915 Error closing cursor: [number]
Cause: This is a header message.
Action: Check the message below this one in the log file for more information.
SQL*Loader-00916 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-00918 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-00919 Error during upi fetch: [number]
Cause: An internal error has occurred.
Action: Check the message below this one in the log file for more information.
SQL*Loader-00925 Error while string
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-00926 OCI error while string for table string
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-00927 Table string 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-00929 Error parsing insert statement for table string.
Cause: The table's insert statement caused a parse error.
Action: Check all SQL strings that were used.
SQL*Loader-00930 Error parsing insert statement for table string column string.
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-00931 OCI error while binding variable for column string in table string
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-00932 Could not truncate table string.
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-00933 Specified file string not part of database
Cause: The specified file name to load the table is not a database file.
Action: Specify a valid datafile.
SQL*Loader-00934 Incorrect data file string specified for table string
Cause: A datafile name was given to load the table that is not a part of the tablespace in which the table resides.
Action: Specify a valid datafile.
SQL*Loader-00935 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-00936 Unable to lock table string partition/subpartition string due to ORACLE error number
Cause: Loader could not lock the partition/subpartition it needed.
Action: Have the holder of the lock relinquish it or retry the operation.
SQL*Loader-00937 parallel load requested and string 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-00938 partition load requested and string 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-00939 OCI error while string for table string partition string
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-00940 UPI error while setting NCHAR bind attributes for column string table string
Cause: An error occurred while setting the CHARSETFORM attribute of an NCHAR column.
Action: This is an internal error. Report to Oracle Customer Support.
SQL*Loader-00941 Error during describe of table string
Cause: An error occurred 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-00942 partition string not part of table string
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-00943 incorrect datafile string specified for table string partition string
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.
SQL*Loader-00944 error preparing insert statement for table string.
Cause: A call to OCIStmtPrepare for the table's insert statement returned an error.
Action: Refer to the message that follows for information about the error returned by OCIStmtPrepare. Make sure the syntax is correct for all SQL strings specified in the SQL*Loader control file.
SQL*Loader-00945 record size number too large for direct path
Cause: The maximum size of records in the datafile is larger than the maximum size supported by direct path, which is 65535
Action: Load the datafile using conventional path.
SQL*Loader-00946 OCI error while string for table string subpartition string
Cause: This is a header message.
Action: Check the following errors for more information. The table or subpartition referenced may not be accessible.
SQL*Loader-00947 subpartition load requested and string has enabled triggers or constraints
Cause: A request was made for a direct load of a single subpartition, 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-00948 subpartition string not part of table string
Cause: The specified subpartition is not part of the specified table.
Action: Check the subpartition and table names.
SQL*Loader-00949 incorrect datafile string specified for table string subpartition string
Cause: The specified datafile is not in the tablespace of the specified subpartition. Due to use of FILE=keyword on a subpartitioned table. When loading all subpartitions of a subpartitioned table, the subpartitions must be in the same tablespace. When loading a single subpartition, the tablespace of the subpartition being loaded must be the same as the tablespace in which the specified datafile file resides.
Action: When loading a single subpartition, make sure the tablespace of the subpartition being loaded is the same as the tablespace in which the specified datafile file resides.
SQL*Loader-00950 Error shipping data structures across 2-task
Cause: This is a header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00951 Error calling once/load initialization
Cause: This is a header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00952 Error calling once/data file initialization
Cause: This is a header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00953 Error shipping read buffer across 2-task
Cause: This is a header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00954 Error shipping index to read buffer across 2-task
Cause: This is a header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00955 Error calling col array build, block formatter
Cause: This is a header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00956 Error calling once/data file finishing
Cause: This is a header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00957 Error shipping text string across 2-task
Cause: This is a header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00958 Error popping data relocation address stack
Cause: This is a header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00959 Error shipping buffer across 2-task
Cause: This is a header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00961 Error calling once/load finishing
Cause: This is a header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00962 Error setting user-side Ctrl-C handler
Cause: This is a header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00963 Error clearing user-side Ctrl-C handler
Cause: This is a header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00965 Error number disabling constraint string on table string
Cause: This is a header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00966 Error number disabling all triggers on table string
Cause: This is a header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00969 Error performing file name translation on kernel side
Cause: File specified for parallel load is probably not a valid database file.
Action: Specify a valid database file.
SQL*Loader-02050 Multibyte character error.
Cause: Text specified by POSITION or terminated by newlines is invalid.
Action: Edit the SQL*Loader control file or the datafile to fix alignment of the column.
