Release 2 (9.2)
Part Number A96525-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
This chapter lists messages generated by the SQL*Loader utility. For more information about this utility, refer to Oracle9i Database Utilities.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: An internal error has occurred.
Action: Contact Oracle Support Services.
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.
Cause: The command-line argument for the parallel file was entered incorrectly.
Action: Check the command line argument and retry the operation.
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.
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!)
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.
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.
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.
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.
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.
Cause: An error occurred when attempting to start a session on the database.
Action: See the message that follows this message for information on the cause of the error.
Cause: The argument's value is inappropriate.
Action: Check the command line and retry.
Cause: The argument's value is inappropriate.
Action: Check the command line and retry.
Cause: The only valid options for the MULTITHREADING command-line argument are TRUE or FALSE. The argument could be misspelled or another argument (not identified by a keyword) could be in it's place.
Action: Check the command line and retry.
Cause: The command line argument specified for external_tables was not TRUE or FALSE.
Action: Check the command line and retry.
Cause: Both options for direct path and external tables were indicated. Only one of these can be applied at a time.
Action: Change at least one of the parameters to enable only one.
Cause: An invalid value was specified for the EXTERNAL_TABLE parameter.
Action: Specify one of the following values:
Cause: The command-line argument specified for RESUMABLE was not TRUE or FALSE.
Action: Check the command line and retry.
Cause: The command-line argument specified for RESUMABLE_NAME was not a valid string.
Action: Check the command line and retry.
Cause: The command-line argument specified for RESUMABLE_TIMEOUT was not a valid positive integer.
Action: Check the command line and retry.
Cause: The command-line argument specified for DATE_CACHE was not a valid positive integer.
Action: Check the command line and retry.
Cause: SQL/DS FORMAT clause is not supported.
Action: Remove the FORMAT command from the SQL*Loader control file or comment it out.
Cause: The SQL*Loader control file contains a WRKDDN statement. SQL*Loader ignores this clause. This is an informational message.
Action: No action required.
Cause: The SQL*Loader control file contains a SORTDEVT statement. SQL*Loader ignores this clause. This is an informational message.
Action: No action required.
Cause: The SQL*Loader control file contains a SORTNUM statement. SQL*Loader ignores this clause. This is an informational message.
Action: No action required.
Cause: The SQL*Loader control file contains a PART statement. SQL*Loader ignores this clause. This is an informational message.
Action: No action required.
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.
Cause: The SQL*Loader control file contains a LOG statement. SQL*Loader ignores this clause. This is an informational message.
Action: No action required.
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.
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.
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.
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.
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.
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.
Cause: The PIECED keyword cannot be used in a conventional path load.
Action: Remove the PIECED keyword or use the direct path load.
Cause: A column that is not the last column was specified as PIECED.
Action: Remove the PIECED keyword or place the column last.
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.
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.
Cause: SQL*Loader could not find the character set handle for the named character set.
Action: Correct the character set name.
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.
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).
Cause: A clause is being compared to a null string.
Action: Modify the clause to compare to at least one character.
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.
Cause: A table-level OPTIONS statement was specified for a non-parallel load.
Action: Remove the OPTIONS statement from the SQL*Loader control file.
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.
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.
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.
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.
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.
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.
Cause: The file name used to perform the parallel load was entered incorrectly.
Action: Correct the file name and re-invoke parallel loader.
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.
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.
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.
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.
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.
Cause: The same input datafile is loaded multiple times. This can occur if the INFILE keyword is placed out of order in the load syntax statement, which causes the filename of the first datafile loaded to default to the name of the control file with an extension or file type of DAT.
Action: Check that INFILE keyword is not placed after one of these - BADFILE/BADDN/DISCARDFILE/DISCARDDN/DISCARDS.
Cause: HIDDEN can only be specified in the conventional path load.
Action: Use the conventional path load.
Cause: Specifying save points using the ROWS parameter is not supported when loading an IOT.
Action: Remove the ROWS parameter from the command-line arguments.
Cause: No control file name was provided at the control prompt.
Action: Provide the name of a valid control file at the prompt or on the command line.
Cause: A TERMINATED BY or ENCLOSED BY clause was found along with an SDF (secondary data files) clause for a nested table or varray field.
Action: The TERMINATED BY and ENCLOSED BY clauses may be specified only if the nested table or VARRAY data is stored in the record in the main data file. If you are loading nested table or VARRAY data from a secondary data file, you must use COUNT to indicate the number of elements in the secondary data file that are stored in the file.
Cause: A SQL string has been associated with both a column object and one of it's attributes in the control file. Because the SQL string of the column object will replace the entire column object in the VALUE clause of the INSERT statement, the SQL string of the attribute is ignored. This could cause unexpected or incorrect values to be loaded.
Action: Correct the control file so that only the column object or it's attribute has a SQL string, but not both.
Cause: The PIECED keyword cannot be used for non lob or long columns.
Action: Remove the PIECED keyword or use lob or long column type.
Cause: A bind variable may not refer to a filler field or to a non-existent field. Also, when running in direct-path mode, a bind variable may not refer to field that represents a LOB stored in a secondary file or a collection.
Action: Remove the offending bind variable from the SQL string.
Cause: A non-hex character was found in a hexadecimal string.
Action: Change it to the intended hexadecimal character.
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.
Cause: The file contains multiple end-of-file marks.
Action: Remove the excess end-of-file characters.
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.
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.
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.
Cause: Particular field types do not allow SQL strings as part of their field specification (e.g. field corresponding to a LOB column). This was violated and needs to be corrected.
Action: Remove the SQL string from the particular field specification.
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 in Oracle9i Database Utilities and make any necessary corrections.
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.
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.
Cause: The named column is not present in the given table.
Action: Correct the column name or table name.
Cause: The named column is specified more than once in a single INTO TABLE statement.
Action: Remove the extraneous column specification.
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.
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.
Cause: When all data is generated, no file is read, and there are no records to skip.
Action: Remove the number to skip.
Cause: An internal error has occurred.
Action: Contact Oracle Support Services.
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.
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.
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.
Cause: More columns were specified for the table than the maximum number allowed by the database.
Action: Remove the extraneous columns.
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.
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.
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.
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.
Cause: Because the direct path bypasses SQL processing, the SQL string cannot be used.
Action: Remove the SQL string or use the conventional path.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: No attributes are to be loaded for a column object named in the control file. This can happen if all fields in the definition for the column object in the control are designated as FILLER fields.
Action: Either specify attributes to load for the column object or remove the column object from the control file.
Cause: Loading LOBs within a nested table at the same time as the parent table is not supported.
Action: Load the nested table with the LOB separately from the parent table.
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.
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.
Cause: The comparison text is too long. It can only be one character.
Action: Reduce the comparison text to one character.
Cause: The comparison text is a white space character (blank or tab).
Action: Change the comparison text to a non-white space character.
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.
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 Support Services and supply the following information: DDL for the table being loaded, and the SQL*Loader control file.
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.
Cause: An error occurred while attempting to write a lob into a row.
Action: See accompanying messages describing why the LOB could not be loaded, what actions SQL*Loader took (if any), and where the errors may be in order to reload.
Cause: This message identifies the secondary data file that was in use for populating the LOB when an error occurred.
Cause: This message identifies the offset into the secondary data file that contains the start of the LOB that was being written when an error occurred.
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.
Cause: The SQL*Loader control file specified a table column that does not exist.
Action: Check the name of the table column.
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.
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.
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.
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.
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.
Cause: More than one non filler field specification is found in a collection field's member field list.
Action: See the correct syntax in Oracle9i Database 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.
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.
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.
Cause: This message is always displayed after message 474.
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.
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.
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.
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.
Cause: The EXPRESSION keyword is followed by a required SQL string expression and is used to load a column with the result of the SQL string expression instead of with a value from the input data file. However, this capability is not allowed with elements of a collection.
Action: Remove the EXPRESSION keyword and associated SQL string from the collection element in the control file.
Cause: The HIDDEN keyword is only allowed for scalar fields.
Action: Remove the HIDDEN keyword from the non-scalar field in the control file.
Cause: SQL*Loader could not open the named file.
Action: Check the operating system messages below this one in the log file.
Cause: SQL*Loader could not read the named file.
Action: Check the operating system messages following this message in the log file.
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.
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.
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.
Cause: An attempt to read a secondary datafile failed.
Action: Check the operating system message that follows this message for more information.
Cause: The record format of the named LOBFILE or SDF file is incorrect.
Action: Fix the record formatting problems in the file.
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.
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.
Cause: A platform-specific error was returned during an operation. This message is used to display the text of the error.
Cause: The datafile has a physical record that is too long.
Action: Use CONCATENATE or CONTINUEIF. Break up the physical records.
Cause: SQL*Loader could not initialize the read functions.
Action: Check the errors below this message in the log file for more information.
Cause: An internal error has occurred.
Action: Contact Oracle Support Services.
Cause: SQL*Loader could not close the named file.
Action: Check the errors below this message in the log file for more information.
Cause: SQL*Loader could not get the elapsed time from the system.
Action: No action required.
Cause: SQL*Loader could not get the CPU time from the system.
Action: No action required.
Cause: The named file was found to be empty.
Action: Check that the intended file was referenced and that it is not empty.
Cause: SQL*Loader could not break down the file name into its component parts.
Action: Check the file name for illegal characters.
Cause: SQL*Loader could not put the file name back together again from its components.
Action: Check the file name for illegal characters.
Cause: LFI failed to make a name object for the file.
Action: Contact Oracle Support Services.
Cause: LFI failed to create or initialize a file object for the file.
Action: Contact Oracle Support Services.
Cause: LFI failed to open the file.
Action: Check for any possible operating system errors and/or potential memory problems.
Cause: Could not write to specified file.
Action: Check the following:
If all of these conditions are satisfied, then retry the operation.
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.
Cause: The message describes the status code returned by an OCI call.
Action: See surrounding messages for more information.
Cause: The message describes the status code returned by an OCI call.
Action: See surrounding messages for more information.
Cause: The message describes the status code returned by an OCI call.
Action: See surrounding messages for more information.
Cause: The message describes the status code returned by an OCI call.
Action: See surrounding messages for more information.
Cause: The message describes the status code returned by an OCI call.
Action: See surrounding messages for more information.
Cause: The message describes the status code returned by an OCI call.
Action: See surrounding messages for more information.
Cause: The message describes the status code returned by an OCI call.
Action: See surrounding messages for more information.
Cause: The message describes the status code returned by an OCI call.
Action: See surrounding messages for more information.
Cause: An unknown status was returned by an OCI call.
Action: See surrounding messages for more information.
Cause: SQL*Loader does not have the privileges required to open the file.
Action: Verify that the correct file was specified and that the file has the appropriate permissions.
Cause: The specified file cannot be found.
Action: verify that the correct name exists and whether the file is in the intended location.
Cause: An error occurred while trying to open the file. No further information is available.
Action: Verify that the file is accessible.
Cause: The processing option specified for the file cannot be processed.
Action: Verify that the processing options specified for the file contain legal syntax for the platform where SQL*Loader is running.
Cause: Attempt to allocate the read buffer failed.
Action: If possible, try specifying a smaller size for the read buffer.
Cause: An attempt to allocate some memory to track I/O for the file failed.
Action: Contact Oracle Support Services.
Cause: SKIP parameter was specified with a linked-in file processor.
Action: Do not use the SKIP parameter in this case.
Cause: An error occurred while closing the file.
Action: Contact Oracle Support Services.
Cause: An error occurred while reading the file.
Action: Make sure the file is still accessible.
Cause: End of file reached.
Cause: A record in the file is larger than the read buffer.
Action: Verify that the file is not corrupt. If not, try specifying a larger size for the read buffer.
Cause: The length portion of a VAR record contains non-numeric data.
Action: Fix the data in the file.
Cause: A hexadecimal literal that contains the record delimiter for the file does not contain a valid hexadecimal string.
Action: Verify that the correct hexadecimal value was specified in the processing options for the file.
Cause: an unexpected error occurred while attempting to skip records.
Action: This message should be followed by another message giving more specific information about the error.
Cause: The space needed to contain a single row is longer than the specified bind size. The value used for the bind size will be increased to handle the larger size.
Action: No action is required. This message will go away if the new value in the error message is specified for the bind size.
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.
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.
Cause: The named column cannot be put in a contiguous piece of memory on the system.
Action: Specify a shorter data column.
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.
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.
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.
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.
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.
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.
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 default maximum length (255 bytes).
Action: Check for missing delimiters and/or shorten the field.
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.
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.
Cause: No termination delimiter was found after the enclosed field ended.
Action: Supply the missing termination delimiter.
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.
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.
Cause: A conversion from the datafile character set to the client character failed due to the conversion graph not being available.
Action: Contact Oracle Support Services. Check NLSRTL installation.
Cause: A character set conversion error occurred.
Action: Contact Oracle Support Services. Check NLSRTL installation. Provide a reproducible test case.
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.
Cause: Each byte in a packed 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.
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.
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
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.
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.
Cause: Encountered errors (for example parsing errors in LOBFILE) while loading LOBs. The row will remain in the table and its LOB column will be initialized to empty. Loading of other records will continue.
Action: Correct the data file (see accompanying messages) and reload.
Cause: An error occurred while attempting to convert an integer to Oracle number format.
Action: Verify that the integer field in the data file is a valid integer. If the INTEGER(N) syntax was used, then verify that the specified length is valid.
Cause: A quoted string in the control file is missing a closing quote.
Action: Insert the closing quote as appropriate.
Cause: Encountered errors (for example, such as parsing errors in LOBFILE) while loading LOBs using direct path. The row will remain in the table and its LOB column may not be complete. Loading of other records will continue.
Action: Correct the data file (see accompanying messages) and reload.
Cause: Encountered errors (for example, such as parsing errors in LOBFILE) while skipping LOBs.
Action: Correct the data file (see accompanying messages) and reload.
Cause: Each byte of a zoned decimal field must have a valid value based on the character set encoding used. ASCII-based zoned decimals must follow the formats specified in the VAX Architecture Reference Manual. EBCDIC-based zoned decimals must follow the formats specified in the ESA/390 Principles of Operations, version 8.1.
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.
Cause: Encountered errors (for example, such as parsing errors in LOBFILE) while loading LOBs into an XML column. The row will remain in the table and its XML column will be initialized to null. Loading of other records will continue.
Action: Correct the data file (see accompanying messages) and reload.
Cause: A variable length field (with a leading length subfield) exceeded its maximum allowable length. The maximum length is either the length specified in the SQL*Loader control file, or, the default if not specified (4 KB).
Action: Shorten the field and its length.
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. If using direct path, try lowering the columnarrayrows option (see log file for current default value).
Cause: An internal error has occurred.
Action: Make a note of the message and contact Oracle Support Services.
Cause: An internal error has occurred.
Action: Make a note of the message and the number, then contact Oracle Support Services.
Cause: An internal error has occurred.
Action: Make a note of the message and the number, then contact Oracle Support Services.
Cause: An internal error has occurred.
Action: Contact Oracle Support Services.
Cause: An internal error has occurred.
Action: Contact Oracle Support Services.
Cause: An internal error has occurred.
Action: Contact Oracle Support Services.
Cause: An unknown status was returned by a call to the sllf layer.
Action: Contact Oracle Support Services.
Cause: A nonsuccess status was returned by a call to the SLTS layer.
Action: Contact Oracle Support Services.
Cause: A direct path stream buffer was built but not loaded.
Action: Contact Oracle Support Services.
Cause: Address for little endian UTF16 data not in a valid buffer.
Action: Contact Oracle Support Services.
Cause: Address for big endian UTF16 data not in a valid buffer.
Action: Contact Oracle Support Services.
Cause: An option was specified that is not supported by External Table load.
Action: Do not specify the unsupported option or do not use External Table load.
Cause: At least two INTO TABLE clauses have different options set.
Action: Set the options to be the same or do the loads separately.
Cause: A numeric EXTERNAL type was specified with a DEFAULTIF clause and that is not supported by External Table Load.
Action: Remove the clause if possible or do not use External Table Load.
Cause: The specified field type is not supported by External Table Load.
Action: Remove the specified field type or do not use External Table Load.
Cause: A sequence with an interval is specified and is not supported by External Table Load.
Action: Remove the interval from the sequence, or the sequence itself, or do not use External Table Load.
Cause: The specified option is not supported by External Table Load.
Action: Remove the specified option or do not use External Table Load.
Cause: The osd string containing file processing options in the control file specified an unknown file processing option.
Action: Verify the correct options are specified for the platform being used.
Cause: An INSERT statement used to load a table from an external table or a temporary internal table failed. The statement that failed is shown immediately preceding this message.
Action: See subsequent messages for more information about the error.
Cause: An attempt to create a sequence needed for the load failed.
Action: See messages that follow this one for information about the failure.
Cause: A sequence needed to be dropped either because SQL*Loader found a sequence with the same name it is trying to create or because SQL*Loader is cleaning up from sequences it created at the beginning of the load.
Action: See messages that follow this one for information about why the attampt to drop the sequence failed.
Cause: An attempt to create the external table sued for the load failed.
Action: See messages that follow for more information about the failure.
Cause: An error occurred when trying to drop an external table. Note that the table may have been left from a previous load.
Cause: An error was encountered trying to create a temporary internal table. The internal table is used only when loading multiple tables from the same data file. The internal table is loaded once and the target tables are loaded from the internal table.
Cause: An error was encountered trying to drop a temporary internal table. The internal table is used only when loading multiple tables from the same data file. The internal table is loaded once and the target tables are loaded from the internal table. The internal table may have been left from a previous build.
Cause: No existing directory object was found in the database for the directory containing the file. Since all files loaded by external tables must be in a directory named by a directory object, SQL*Loader tried to create a directory object for the file.
Action: See error messages that follow this message for more information.
Cause: SQL*Loader created a directory object as part of an external table load. An attempt to cleanup the directory object failed.
Action: See messages following this one for more information about the error.
Cause: The EXTERNAL_TABLE parameter was specified for a multi-table load, and a WHEN clause for one of the tables contains a reference to a range of bytes in the record. SQL*Loader uses the WHEN clause from the control file to generate the WHERE clause in the INSERT statement. If the WHERE clause contains a reference to a range of bytes in the table, then a valid WHERE clause can not be generated. Note that SQL*Loader will proceed as if GENERATE_ONLY was specified for the EXTERNAL_TABLE parameter.
Action: Modify the control file to only use field references in the WHEN clause. Note that this may require creating a filler field. Another alternative is to create one control file for each table to be loaded and load the table separately.
Cause: SQL Loader is not able to execute the SQL statements it generated for loading the data using external tables. See previous messages for more information.
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.
Cause: An internal error has occurred.
Action: Check the Oracle messages below this one in the log file and contact Oracle Support Services.
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.
Cause: The direct path mode is being used after SQL*Loader has been linked with a Version 5 database.
Action: Use the conventional path.
Cause: This is a header message.
Action: Check the message below this one in the log file for more information.
Cause: An internal error has occurred.
Action: Check the message below this one in the log file for more information.
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.
Cause: Database views required for the direct path mode are not present.
Action: The Oracle9i Database Administrator's Guide details how to run the required scripts as user SYS for loading the required views.
Cause: This is a header message.
Action: Check the message below this one in the log file for more information.
Cause: This is a header message.
Action: Check the message below this one in the log file for more information.
Cause: This is a header message.
Action: Check the message below this one in the log file for more information.
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.
Cause: This is a header message.
Action: Check the message below this one in the log file for more information.
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.
Cause: The catalog is not loaded.
Action: Logon as user SYS and load the Oracle catalog and the views in the script ULVIEW.SQL.
Cause: An internal error has occurred.
Action: Check the message below this one in the log file for more information.
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.
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.
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.
Cause: The table's insert statement caused a parse error.
Action: Check all SQL strings that were used.
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.
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.
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.
Cause: The specified file name to load the table is not a database file.
Action: Specify a valid datafile.
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.
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.
Cause: Loader could not lock the partition/subpartition it needed.
Action: Have the holder of the lock relinquish it or retry the operation.
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.
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.
Cause: This is a header message.
Action: Check the following errors for more information. The table or partition referenced may not be accessible.
Cause: An error occurred while setting the CHARSETFORM attribute of an NCHAR column.
Action: This is an internal error. Report to Oracle Support Services.
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.
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.
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.
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.
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.
Cause: This is a header message.
Action: Check the following errors for more information. The table or subpartition referenced may not be accessible.
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.
Cause: The specified subpartition is not part of the specified table.
Action: Check the subpartition and table names.
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.
Cause: This is a header message.
Action: Check the error(s) below it for more information.
Cause: This is a header message.
Action: Check the error(s) below it for more information.
Cause: This is a header message.
Action: Check the error(s) below it for more information.
Cause: This is a header message.
Action: Check the error(s) below it for more information.
Cause: This is a header message.
Action: Check the error(s) below it for more information.
Cause: This is a header message.
Action: Check the error(s) below it for more information.
Cause: This is a header message.
Action: Check the error(s) below it for more information.
Cause: This is a header message.
Action: Check the error(s) below it for more information.
Cause: This is a header message.
Action: Check the error(s) below it for more information.
Cause: This is a header message.
Action: Check the error(s) below it for more information.
Cause: This is a header message.
Action: Check the error(s) below it for more information.
Cause: This is a header message.
Action: Check the error(s) below it for more information.
Cause: This is a header message.
Action: Check the error(s) below it for more information.
Cause: This is a header message.
Action: Check the error(s) below it for more information.
Cause: This is a header message.
Action: Check the error(s) below it for more information.
Cause: File specified for parallel load is probably not a valid database file.
Action: Specify a valid database file.
Cause: The load cannot continue. See the error message before this message for the cause of the error.
Action: See the action for the error message that precedes this one.
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.
Cause: Current session is not resumable.
Action: Must specify RESUMABLE=TRUE to enable resumable session in order for the RESUMABLE_NAME and RESUMABLE_TIMEOUT parameters to take effect.
Cause: There is a limit on the maximum size of the record which can be written to the bad or discard file. SQL*Loader encountered a record that exceeded this limit.
Action: See the next message which follows this message to know which record exceeded the limit. Modify that record, if necessary, and try to load again.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
