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.

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.

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. Another is that the specified file name caused an overflow of the output buffer.

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. Another possible cause is that the specified file name caused an overflow of the output buffer.

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. Another possible cause is that the specified file name caused an overflow of the output buffer.

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. Another possible cause is that the specified file name caused an overflow of the output buffer.

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. Another possible cause is that the specified file name caused an overflow of the output buffer.

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

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

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

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

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

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

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.

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

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.

Cause: An internal error has occurred.

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

Cause: The command-line argument for the parallel file was entered incorrectly. One possible cause is that the specified file name caused an overflow of the output buffer.

Cause: The command-line argument _synchro is incorrect.

Cause: The command line argument for skip_unusable_indexes is incorrect.

Cause: The command line argument for skip_index_maintenance is incorrect.

Cause: The command line argument specified for bindsize was less than the value of readsize.

Cause: The command line argument specified for readsize was less than the value of bindsize.

Cause: The command line argument specified for readsize was less than 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.

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

Cause: An error occurred when attempting to start a session on the database.

Cause: The argument's value is inappropriate

Cause: The argument's value is inappropriate

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 its place.

Cause: The command line argument specified for external_tables was not TRUE or FALSE

Cause: Both options for direct path and exrernal tables were indicated. Only one of these can be applied at a time.

Cause: An invalid value was specified for the EXTERNAL_TABLE parameter.

Cause: The command line argument specified for RESUMABLE was not TRUE or FALSE.

Cause: The command line argument specified for RESUMABLE_NAME was not a valid string.

Cause: The command line argument specified for RESUMABLE_TIMEOUT was not a valid positive integer.

Cause: The command line argument specified for DATE_CACHE was not a valid positive integer.

Cause: External table mode and direct path mode were both specified.

Cause: The command line argument specified was not a valid boolean.

Cause: The command line argument specified was not -1, 0, or positive.

Cause: The NO_INDEX_ERRORS parameter was specified for a parallel load.

Cause: The command line argument specified for the TABLE parameter was not a valid string. It is also possible that the schema name or the table name overflowed the output buffer which allows for the maximum identifier size in the database character set.

Cause: A control file was specified along with the TABLE parameter.

Cause: Conflicting values were specified for the parallel setting. This could be caused by: 1) having PARALLEL=TRUE and DEGREE_OF_PARALLELISM=NONE(or 1) 2) PARALLEL=FALSE and DEGREE_OF_PARALLELISM being set to a value other than NONE or 1.

Cause: The argument's value was inappropriate.

Cause: The command line argument specified for the DATE_FORMAT parameter was not a valid string.

Cause: A control file was specified along with the DATE_FORMAT parameter.

Cause: The command line argument specified for the TERMINATED_BY parameter was not a valid string.

Cause: The command line argument specified for the TERMINATED_BY parameter was not a valid hexadecimal string.

Cause: The command line argument specified for the table-level NULLIF parameter was not a valid hexadecimal string.

Cause: The TERMINATED_BY parameter was specified without the TABLE parameter.

Cause: The command line argument specified for the ENCLOSED_BY parameter was not a valid string.

Cause: The command line argument specified for the ENCLOSED_BY parameter was not a valid hexadecimal string.

Cause: Both the ENCLOSED_BY parameter and the OPTIONALLY_ENCLOSED_BY parameter were specified.

Cause: The ENCLOSED_BY parameter was specified without the TABLE parameter.

Cause: The command line argument specified for the OPTIONALLY_ENCLOSED_BY parameter was not a valid string.

Cause: The command line argument specified for the OPTIONALLY_ENCLOSED_BY parameter was not a valid hexadecimal string.

Cause: Both the OPTIONALLY_ENCLOSED_BY parameter and the ENCLOSED_BY parameter were specified.

Cause: The OPTIONALLY_ENCLOSED_BY parameter was specified without the TABLE parameter.

Cause: The command line argument specified for the CHARACTERSET parameter was not a valid string.

Cause: A control file was specified along with the CHARACTERSET parameter.

Cause: The CHARACTERSET parameter was specified without the TABLE parameter.

Cause: The command line argument specified for the DEGREE_OF_PARALLELISM parameter was not a valid string.

Cause: An option was specified that is not supported for conventional path or direct path.

Cause: The command line argument specified for the TRIM parameter was not a valid string.

Cause: The command line argument specified for the CSV parameter was not a valid string.

Cause: The command line argument specified for the TIMESTAMP_FORMAT parameter was not a valid string.

Cause: A control file was specified along with the TIMESTAMP_FORMAT parameter.

Cause: The command line argument specified for the NULLIF parameter was not a valid string.

Cause: SQL/DS FORMAT clause is not supported.

Cause: The control file clause specified for CSV was neither CSV WITH EMBEDDED or CSV WITHOUT EMBEDDED.

Cause: A CSV format file with embedded record terminators was specified with a shift-based character set.

Cause: A control file was specified along with the NULLIF parameter.

Cause: The command line argument specified for the FIELD_NAMES parameter was not a valid string. You must specify FIRST, FIRST_IGNORE, ALL, ALL_IGNORE, or NONE.

Cause: A control file was specified along with the FIELD_NAMES parameter.

Cause: A field name in the FIELD NAMES record was empty.

Cause: One or more field names was not listed in the FIELD NAMES record. However, it was listed in the access parameter list for the external table.

Cause: The listed field was not found in the control file field list. The next error message lists the name of the data file where the error was found.

Cause: An error occurred while processing the FIELD NAMES record for the data file.

Cause: The data file listed in the next message was empty. Therefore, the FIELD NAMES FIRST FILE directive could not be processed.

Cause: The field name exceeded the maximum of 30 characters.

Cause: A field level ENCLOSED BY clause was specified with the CSV WITH EMBEDDED clause. All fields must use the same ENCLOSED BY or OPTIONALLY ENCLOSED BY clause for CSV files with embedded record terminators.

Cause: The table 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. The schema name or the table name may have been too long for a valid database identifier in the database character set.

Cause: The table name specified in the INTO TABLE clause was not recognized. The schema name or the table name may have been too long for a valid database identifier in the database character set.

Cause: The datafile name specified in INFILE statement was not recognized. It could be misspelled, or the length may exceed the maximum file specification allowed on the platform.

Cause: The bad file name specified in the BADFILE statement was not recognized. It could be misspelled, or the length may exceed the maximum file specification allowed on the platform.

Cause: The discard file name specified in the DISCARDFILE statement was not recognized. It could be misspelled, or the length may exceed the maximum file specification allowed on the platform.

Cause: A command-line parameter was specified that is supported only for express mode and not for loads which use a control file.

Cause: The value for the SDF_PREFIX parameter was not recognized or the value of the parameter was too long.

Cause: The table name specified for the exceptions table in the REENABLE disabled constraints clause was not recognized. The schema name or the table name may have been too long for a valid database identifier in the database character set.

Cause: The name specified for the partition or subpartition was not recognized. The name may have been too long for a valid database identifier in the database character set.

Cause: An invalid value was specified for the DEFAULTS parameter.

Cause: The DEFAULTS parameter was specified for a non-direct path load.

Cause: Multiple format masks were specified for the listed datetime data type at the table level for the listed table.

Cause: An unexpected error occurred while processing the datetime format mask.

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

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

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

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

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

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

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

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.

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

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.

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" data files.

Cause: The TERMINATED BY option cannot be used for loading data of type RAW from the data file. The only exception is when loading RAW data from LOBFILES. In that case, you may specify the TERMINATED BY EOF option.

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

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

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.

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

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

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

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

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

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.

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

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

Cause: The READBUFFERS specification was not entered as part of a direct path.

Cause: Fewer than 2 read buffers have been specified.

Cause: The INFILE specification was not entered 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.

Cause: A filename has been specified in the table level options statement and also in the global options statement.

Cause: The filename used to perform the parallel load was entered incorrectly.

Cause: INSERT, REPLACE, or TRUNCATE mode was used in a parallel load specification.

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.

Cause: Specifying save points using the ROWS parameter is not supported for parallel loads.

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

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.

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.

Cause: HIDDEN can only be specified in the conventional path load.

Cause: Specifying save points using the ROWS parameter is not supported when loading an IOT.

Cause: No control file name was provided at the control prompt.

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.

Cause: A SQL string has been associated with both a column object and one of its 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.

Cause: The PIECED keyword cannot be used for non lob or long columns.

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.

Cause: Command-line arguments contained a ROWS parameter. Specifying save points using the ROWS parameter is not supported when any table being loaded contains a LOB or a column stored as a LOB. XML and VARRAY columns may be stored as a LOB.

Cause: A table of sys.xmltype must specify the XMLTYPE directive.

Cause: The type name specified in a TREAT AS clause is invalid. It might contain characters that are not valid in the client character set or a quoted string might not be terminated or the name might be too long to contain a valid schema name and type name.

Cause: The quoting rule of bind variables consisting of full object attribute names changed. The old quoting rule is incorrect because it can lead to ambiguous column references. For backward compatibility, current load will continue unless ambiguous column references are detected.

Cause: A bind variable can only refer to one column in the control file. Current load could not continue due to ambiguous column references.

Cause: See following error message for more information. A SQL string cannot have quoted strings improperly terminated. A bind variable in a SQL string cannot have a length of 0, cannot exceed maximum length of 30 characters, and cannot be missing a double quote.

Cause: The specified filler field name exceeded the maximum of 30 characters.

Cause: Virtual columns were specified in the control file.

Cause: An error occurred while executing an ALTER SESSION statement to enable tracing. This message will be followed by the error returned from ALTER SESSION.

Cause: The size of a string literal is longer than the maximum number of bytes allowed for an ENCLOSED BY or TERMINATED BY string. This error can also occur if the string needs to be converted to the character set of the data file and the resulting string is too long.

Cause: A non-hex character was found in a hexadecimal string.

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.

Cause: The file contains multiple end-of-file marks.

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.

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: --with the POSITION keyword: POSITION(1:3) -- with the length specifier: CHAR(6) -- with the implied length of a datatype; for example, INTEGER -- 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.

Cause: A SQL string was found that was not quoted or in 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.

Cause: A string specified for interval partitioning was found that was not quoted or in single quotes.

Cause: SQL*Loader is connected to a database that is acting as the catalog database for a sharded database and the table identified by the message is a sharded table. SQL*Loader does not support loading sharded tables in a shard catalog database.

Cause: num 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*Loa er-350: Syntax error at line 28 -- Expecting column name, found keyword CHAR -- col3 ENCLOSED BY '"', CHAR ENCLOSED "'",

Cause: The named field contains a (start:end) clause in which end is less than 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.

Cause: The named column is not present in the given table.

Cause: The named column is specified more than once in a single INTO TABLE statement.

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.

Cause: When only generated data is loaded, a number to load must be given so SQL*Loader knows when to stop.

Cause: When all data is generated, no file is read, and there are no records to skip.

Cause: An internal error has occurred.

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.

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.

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.

Cause: More columns were specified for the table than the maximum number allowed by the database.

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.

Cause: There were no fields in the data file to be loaded for the table. Probably all fields were identified as FILLER fields.

Cause: The named column is identified as the target of a secondary data file (SDF) or LOBFILE clause. However, the column also gets it's 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.

Cause: The secondary data file clause for the field identified another field that doesn't exist in the table definition for the SQL*Loader control file.

Cause: Because the direct path bypasses SQL processing, the SQL string cannot be used.

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 theREF datatype in the SQL*Loader control file.

Cause: The datatype in the SQL*Loader control file for the column is cannot be used to load data in a varray.

Cause: The colummn needs to have it's data converted to another datatype before loading the data. The required conversion cannot be done by sqlldr.

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 data file to the datatype for the column in the database. This message should be followed with another message describing the conversion error.

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.

Cause: When building a varray from the data file, SQL*Loader encountered more varray elements than are allowed for the column.

Cause: A WHEN, OID or SID clause for the table refers to a field declared inside of a collection.

Cause: A clause, such as NULLIF or BFILE clause, for the column refers to a field declared inside of a collection.

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 data file. 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.

Cause: The field condition referenced a field which is either a nested table, varray, column object, LOB, expression, or BFILE field. Fields with these types cannot be referenced by other fields.

Cause: The count clause for a field references another field, but the referenced field is not a character or integer datatype.

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.

Cause: A row in a nested table was set to NULL. Nested tables cannot contain NULL fields.

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 make 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.

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.

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.

Cause: Loading LOBs and XML data within a nested table at the same time as the parent table is not supported.

Cause: A constant value was specified for the SETID of a nested table column. An error occured while translating the character constant into a SETID.

Cause: The value of the field named in the message is used to populate the column named in the messsage. Because column is a Set ID or an Object ID, the field needs to be converted. This message indicates that there was a conversion error. If the field is a character field, then the conversion error could be caused by too many or too few haxeadecimal charactersI. Also, one or more of the characters in the field might not be a valid hexadecimal character. If the field contains RAW data, then either too many or to few bytes were specified for the field.

Cause: An enabled constraint was present on a LOB column.

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.

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

Cause: The comparison text is too long. It can only be one character.

Cause: The comparison text is a whitespace character (blank or tab).

Cause: An attempt was made to retrieve a non-numeric value for a sequenced column.

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.

Cause: The datatype for the specified column is one that cannot be loaded with direct path.

Cause: An error occurred while attempting to write a LOB into a row.

Cause: The secondary data file that was in use for populating the LOB when an error occured.

Cause: The offset into the secondary data file that contains the start of the LOB that was being written when an error occured.

Cause: You specified a directive such as COUNT() or BFILE() in the SQL*Loader control file. This directive specifies a fixed number of arguments, but the SQL*Loader control file contains a different number of arguments.

Cause: The SQL*Loader control file specified a table column that does not exist.

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.

Cause: More than one argument was specified for an OID clause.

Cause: More than one argument was specified for a 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.

Cause: You specified a CONSTANT as an argument in an OID clause for an object table or in the SID clause for a nested table column. Since these columns must have unique values, SQL Loader does not allow the a constant to be specified for their values.

Cause: More than one non filler field specification is found in a collection field's member field list.

Cause: Nesting of one collection type field description within another is not allowed.

Cause: The data for the named column was 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 data file does not match the format described by 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.

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.

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 can't determine how to get the LOB for the next row.

Cause: The number of arguments in the REF directive for the column is incorrect.

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.

Cause: The HIDDEN keyword is only allowed for scalar fields.

Cause: A sql-string was specified as part of the description of the field that is inside a nested table or varray. Sql-strings cannot be used to load a field in a varrary or nested tables.

Cause: A VARRAY or NESTED TABLE was defined in the SQL Loader control file and all of the fields in the VARRAY or NESTED TABLE are generated by SQL Loader and do not come from a data file. SQL Loader requires a COUNT clause be specified so that it knows how many elements to add to the VARRAY or NESTED TABLE for each row.

Cause: The FILLER option was specified for a VARRAY or NESTED TABLE field in the SQL Loader control file. However, the type name specified for the field is not the name of a VARRAY or NESTED TABLE type.

Cause: There was no data specified in the control file, a LOB file, or a secondary data file for this object column.

Cause: The absolute position specification was used for inline collections. Specifying the absolute position for inline collections is not supported.

Cause: SQL*Loader could not open the named file.

Cause: SQL*Loader could not read the named file.

Cause: An attempt to open a LOBFILE or secondary data file failed.

Cause: SQL*Loader could not append the default extension to create the filename. The given name could be too long or contain illegal characters.

Cause: SQL*Loader could not open the file or could not read from it.

Cause: An attempt to read a secondary data file failed.

Cause: The the record format of the named LOBFILE or SDF file is incorrect.

Cause: The end of file was reached for a secondary data file or LOBFILE before the data for the current row was found.

Cause: The data found in the data file does not correspond to the record format 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.

Cause: SQL*Loader could not initialize the read functions.

Cause: An internal error has occurred.

Cause: SQL*Loader could not close the named file.

Cause: SQL*Loader could not get the elapsed time from the system.

Cause: SQL*Loader could not get the CPU time from the system.

Cause: The named file was found to be empty.

Cause: SQL*Loader could not break down the filename into its component parts.

Cause: SQL*Loader could not put the filename back together again from its components.

Cause: LFI failed to make a name object for the file.

Cause: LFI failed to create or initialize a file object for the file.

Cause: LFI failed to open the file.

Cause: Could not write to specified file.

Cause: An incomplete record was found at the end of the indicated datafile.

Cause: The message describes the status code returned by an OCI call.

Cause: The message describes the status code returned by an OCI call.

Cause: The message describes the status code returned by an OCI call.

Cause: The message describes the status code returned by an OCI call.

Cause: The message describes the status code returned by an OCI call.

Cause: The message describes the status code returned by an OCI call.

Cause: The message describes the status code returned by an OCI call.

Cause: The message describes the status code returned by an OCI call.

Cause: An unknown status was returned by an OCI call.

Cause: SQL*Loader could not find a file which matched the INFILE wildcard specification.

Cause: SQL*Loader could not find a file which matched the INFILE subdirectory search specification.

Cause: SQL*Loader could not find a file which matched any of the data parameter specifications or INFILE specifications.

Cause: SQL*Loader could not find a file which matched the data parameter wildcard specification.

Cause: SQL*Loader could not find a file which matched the data parameter subdirectory search specification.

Cause: SQL*Loader could not find a file which matched any of the data parameter specifications. Since there is no control file for express mode, there are no INFILE specifications.

Cause: An internal error occured while trying to initialize the file I/O component.

Cause: SQL*Loader does not have the previleges required to open the file.

Cause: The specified file cannot be found.

Cause: An error occurred while trying to open the file. No further information is available.

Cause: The processing option specified for the file cannot be processed.

Cause: Attempt to allocate the read buffer failed.

Cause: An attempt to allocate some memory to track I/O for the file failed.

Cause: SKIP parameter was specified with a linked-in file processor.

Cause: An error occured while closing the file.

Cause: An error occurred while reading the file.

Cause: End of file reached.

Cause: A record in the file is larder than the read buffer.

Cause: The length protion of a VAR record contains non-numeric data.

Cause: A hexadecimal literal that contains the record delimiter for the file does not contain a valid hexadecimal string.

Cause: an unexpected error occured while attempting to skip records.

Cause: An incomplete record was found at the end of file.

Cause: An error occured while attempting to build a name for a data file, bad file, discard file or log file.

Cause: Unexpected error occured while writing to a file. This message is followed by another message with more information about the error.

Cause: The value specified for the READSIZE parameter on the SQL Loader command line was larger than the maximum size allowed on the platform executing the SQL Loader command

Cause: The value specified for the BADFILE parameter contained something other than a directory specification (for example, it contained a file name). The INFILE specification had wildcards or the data command line parameter specification contained a comma-separated list or wildcards and the result was more than one data file. In that case, the BADFILE specification or the BAD command line parameter value should be a directory specification only and should not contain a file name.

Cause: The value specified for the DISCARDFILE parameter contained something other than a directory specification (for example, it contained a file name). The INFILE specification had wildcards or the data command line parameter specification contained a comma-separated list or wildcards and the result was more than one data file. In that case, the DISCARDFILE specification or the DISCARD command line parameter value should be a directory specification only and should not contain a file name.

Cause: SQL*Loader could not add "_%p" to the file name. The name specified or the derived name may be too long.

Cause: An error occurred while trying to open the directory (see accompanying error code).

Cause: Informational only.

Cause: Informational only.

Cause: An error occurred while trying to get the count of directory entries (see accompanying error code).

Cause: An error occurred while trying to read the directory (see accompanying error code).

Cause: An error occurred while trying to finish a search for files in a directory that match a wild card specification (see accompanying error code).

Cause: SQL*Loader could not use the external tables load method for the express mode load. Therefore SQL*Loader tried to use direct path for the load instead of external tables. See any previous messages for more information.

Cause: SQL*Loader could not remove "_%p" from the file name.

Cause: SQL*Loader was doing a direct path or conventional path load. SQL*Loader only supports LDRTRIM for direct path and conventional path. Therefore, LDRTRIM trimming was used for the load. You can get the equivalent of NOTRIM trimming if you use a control file and use the PRESERVE BLANKS clause.

Cause: DEGREE_OF_PARALLELISM was not supported by SQL*Loader for direct path and conventional path loads. Therefore, the DEGREE_OF_PARALLELISM setting was ignored for the load and treated as a value of NONE.

Cause: DEGREE_OF_PARALLELISM was defaulted to NONE by SQL*Loader because load=n was specified. This assures consistency in the records which get loaded with load=n.

Cause: The OID directive was specified but the table is not a type table. The OID directive can be specified only for type tables.

Cause: The SID directive was specified but the table is not a nested table. The SID directive can be specified only for nested tables.

Cause: The XMLTYPE directive was specified but the table is not an XML type table. The XMLTYPE directive can be specified only for XMLTYPE tables.

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

Cause: A non-empty table is being loaded with the INSERT option.

Cause: The named column cannot undergo the specified character set conversion and still be placed in a contiguous piece of memory on the system.

Cause: The named column cannot be put in a contiguous piece of memory on the system.

Cause: An error occurred while trying to commit changes to the database.

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.)

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.

Cause: An attempt was made to use the INSERT option on a non-empty partition.

Cause: An attempt was made to use the INSERT option on a non-empty subpartition.

Cause: SQL Loader adjusted the value it was using for the ROWS parameter to the new value reported. This is an informational message and not an error. SQL Loader will adjust the value of the ROWS parameter if the amount of memory specified by BINDSIZE is not large enough to hold data for the number of rows specified. SQL Loader will also change the value of the ROWS parameter for conventional path loads if the value is larger than 65534. Conventional path load can load at most 65534 rows at a time.

Cause: An attempt was made to load a system partitioned table with no partitioning clause specified in the SQL*Loader control file.

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.

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).

Cause: The logical record ended before all specified fields were found.

Cause: The logical end of record or the end of a LOBFILE was reached before a second enclosure delimiter was found.

Cause: No termination delimiter was found after the enclosed field ended.

Cause: Incomplete multi-byte character strings were found in the SQL*Loader control file.

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.

Cause: A conversion from the datafile character set to the client character failed due to the conversion graph not being available.

Cause: A character set conversion error occurred.

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.

Cause: Each byte in a packed decimal field contains two 4-bit nibbles. Each nibble must have a valid value.

Cause: A field specified as POSITION(*+n:y) had its relative start occur after the absolute position y.

Cause: A fatal error occured while attempting to insert data into the table.

Cause: While attempting to read the length portion of a varying length field, then end of the logical record was reached.

Cause: An error occurred while attempting to convert the characters containing the count portion of a VARCHARC or VARRAWC field.

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.

Cause: An error occurred while attempting to convert an integer to an Oracle number format.

Cause: A quoted string in the control file is missing a closing quote.

Cause: Encountered errors (for example, 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.

Cause: Encountered errors (for example, parsing errors in LOBFILE) while skipping LOBs.

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.

Cause: Encountered errors (for example, 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.

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 (4kb).

Cause: The table being loaded contains a column object which contains an XML attribute with a storage type of object-relational. This type of attribute cannot be loaded with direct path.

Cause: Use of a position specification was present in an external table load.

Cause: Due to memory use, multiple passes were used to load some partitions.

Cause: SQL*Loader could not allocate the memory it needs.

Cause: An internal error has occurred.

Cause: An internal error has occurred.

Cause: An internal error has occurred.

Cause: An internal error has occurred.

Cause: An internal error has occurred.

Cause: An unknown status was returned by a call to the sllf layer.

Cause: A nonsuccess status was returned by a call to the SLTS layer.

Cause: A direct path stream buffer was built but not loaded.

Cause: Address for little endian UTF16 data not in a valid buffer.

Cause: Address for big endian UTF16 data not in a valid buffer.

Cause: A nonsuccess status was returned by a call to the SLTS layer.

Cause: An option was specified that is not supported by External Table load.

Cause: At least two INTO TABLE clauses have different options set.

Cause: A numeric EXTERNAL type was specified with a DEFAULTIF clause which is not supported by external table load.

Cause: The specified field type is not supported by external table.

Cause: A sequence with an interval was specified which is not supported by external table load.

Cause: The specified option is not supported by external table or express mode load.

Cause: The osd string containing file processing options in the control file specified an unknown file processing option.

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 mesage.

Cause: An attempt to create a sequence needed for the load failed.

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.

Cause: An attempt to create the external table sued for the load failed.

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.

Cause: SQL Loader created a directory object as part of an external table load. An attempt to cleanup the directory object failed.

Cause: The EXTERNAL_TABLE parameter was specified for a multi-table load, and a WHEN clause for one of the tables contained a reference to a range of bytes in the record using POSITION syntax. 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 cannot be generated. Note that SQL*Loader will proceed as if GENERATE_ONLY was specified for the EXTERNAL_TABLE parameter.

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: User attempted on operation on an external table which is not supported.

Cause: A TREAT AS clause was specified in the INTO TABLE clause for an object table in the SQL*Loader control file and the EXTERNAL_TABLES command line parameter was set to either EXECUTE or GENERATE_ONLY. External tables can be used to load the data, but SQL*Loader does not generate the correct SQL statements to do this.

Cause: The column type was not supported by external table or express mode using the external table load method.

Cause: An attempt was made to load a primary key reference column.

Cause: An attempt was made to log on to Oracle in direct path load mode.

Cause: An internal error has occurred.

Cause: The direct path load mode is being used with an incompatible database.

Cause: The direct path mode is being used after SQL*Loader has been linked with a Version 5 database.

Cause: Header message.

Cause: An internal error has occurred.

Cause: Database views required for the direct path mode are not present.

Cause: Header message.

Cause: Header message.

Cause: Header message.

Cause: The direct path mode could not lock the named table.

Cause: Header message.

Cause: To do a direct path load 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.

Cause: The catalog is not loaded.

Cause: An internal error has occurred.

Cause: An internal error has occurred.

Cause: An OCI error has occurred.

Cause: The table's insert statement caused a parse error.

Cause: The named column's INSERT statement caused a parse error.

Cause: An OCI error has occurred.

Cause: Truncation of the table was attempted and failed.

Cause: The specified filename to load the table is not a database file.

Cause: A datafile name was given to load the table that is not a part of the tablespace in which the table resides.

Cause: An error was encountered because a required option was not found or was invalid.

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.

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.

Cause: Header message.

Cause: An error occured while setting the charsetform attribute of an NCHAR column.

Cause: Error while executing a describe of a select list on the given table. Check the error immediately preceding this error.

Cause: the specified partition is not part of the specified table

Cause: The specified datafile is not in the tablespace of the specified partition. Due to 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.

Cause: A call to OCIStmtPrepare for the table's insert statement returned an error.

Cause: The maximum size of records in the data file is larger than the maximum size supported by direct path, which is 65535

Cause: Header message.

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.

Cause: the specified subpartition is not part of the specified table

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.

Cause: Header message.

Cause: Header message.

Cause: Header message.

Cause: Header message.

Cause: Header message.

Cause: Header message.

Cause: Header message.

Cause: Header message.

Cause: Header message.

Cause: Header message.

Cause: Header message.

Cause: Header message.

Cause: Header message.

Cause: Header message.

Cause: Header message.

Cause: File specified for parallel load is probably not a valid database file.

Cause: An enabled check constraint existed on an XML column.

Cause: An attempt was made to load lob columns using parallel=true. This error will also be issued when loading columns stored as lobs (such as varrays and xml types)

Cause: Specifying save points using the ROWS parameter was not supported with NO_INDEX_ERRORS=TRUE.

Cause: Specifying save points using the ROWS parameter was not supported with PARTITION_MEMORY=n.

Cause: The database was not opened for read/write access. SQL*Loader requires that the database be opened for read/write access.

Cause: The load cannot continue. See the error message before this * message for the cause of the error.

Cause: Text specified by POSITION or terminated by newlines is invalid.

Cause: CSV format files did not have delimited fields. CSV format files must have all delimited fields so that SQL*Loader can process the fields.

Cause: Data files with a FIELD NAMES record did not have delimited fields. Data files with a FIELD NAMES record must have all delimited fields so that SQL*Loader can process the field names.

Cause: CSV format file was specified with INFILE * indicating that there was data in the control file.

Cause: The LOB Location Specifier field was not processed correctly.

Cause: The destination column for a LOB Location Specifier field was not a LOB data type.

Cause: The LOB Location Specifier contained an invalid offset or length.

Cause: The destination column for a LOB Location Specifier field was not a LOB data type.

Cause: The LOB Location Specifier length request exceeded the length of the lob file. The entire length requested could not be satisfied and will be less than the amount specified.

Cause: The LOB Location Specifier specified an offset in the LOB file which resulted in a seek failure.

Cause: An error occurred while attempting to alter the user session with the parameter specified.

Cause: The container map constraint was detected but was not verified or enforced during a direct path load.

Cause: The unique constraint was detected but was not verified or enforced for Application Root rows during a direct path load when the sharing level was extended data-linked.

Cause: Current session is not resumable.