Oracle Error Messages: 09/02/11

SQL*Loader-00350: Syntax error at line number.

SQL*Loader-00350: Syntax error at line number.

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 ,

Action: Compare the DDL syntax against the syntax diagrams in Oracle7 Server Utilities and make any necessary corrections.

SQL*Loader-00309: No SQL string allowed as part of string field specification

SQL*Loader-00309: No SQL string allowed as part of string field specification

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.

SQL*Loader-00308: %s SQL string of column string must be in double quotes.

SQL*Loader-00308: %s SQL string of column string must be in double quotes.

Cause: A SQL string was found that was not quoted or in single quotes.

Action: Use double quotes for the SQL string, rather than single quotes.

SQL*Loader-00307: Warning: conflicting lengths number and number specified for column string table string

SQL*Loader-00307: Warning: conflicting lengths number and number specified for column string table string

Cause: The SQL*Loader control file specifies two different lengths for the named column. There are three ways to specify the length of a field: --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.

Action: No action is necessarily required, because SQL*Loader uses only one of the lengths. Check the log file under the heading Len in the table-description section to see which length was used. Adjusting the SQL*Loader control file to produce uniform length specifications will remove the warning.

SQL*Loader-00306: Token longer than max allowable length of number chars

SQL*Loader-00306: Token longer than max allowable length of number chars

Cause: The SQL*Loader control file contains a single word or combination of characters (a token) that is longer than the maximum permissible value. The maximum possible value is shown. This error could result from missing spaces, so that multiple tokens are joined.

Action: Check that the proper SQL*Loader control file is being executed Separate tokens, if joined, or shorten the token.

SQL*Loader-00305: More than one end of file character encountered

SQL*Loader-00305: More than one end of file character encountered

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

Action: Remove the excess end-of-file characters.

SQL*Loader-00304: Illegal combination of non-alphanumeric characters

SQL*Loader-00304: Illegal combination of non-alphanumeric characters

Cause: The SQL*Loader control file contains a combination of non-alphanumeric characters that SQL*Loader does not recognize. For example, the combination = is recognized as not equal , but the combination = is not valid.

Action: Remove the unrecognized characters from the control file.

SQL*Loader-00303: Non-hex character encountered where hex char expected

SQL*Loader-00303: Non-hex character encountered where hex char expected

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

Action: Change it to the intended hexadecimal character.

SQL*Loader-00298: Filler field name is too long

SQL*Loader-00298: Filler field name is too long

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

Action: Specify at most 30 characters.

SQL*Loader-00297: Invalid syntax or bind variable in SQL string for column string.

SQL*Loader-00297: Invalid syntax or bind variable in SQL string for column string.

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.

Action: Fix the SQL string. See following error for more information.

SQL*Loader-00296: Bind variable string for column string is ambiguous.

SQL*Loader-00296: Bind variable string for column string is ambiguous.

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

Action: Fix the bind variable. If this bind variable consists of quotes, check that the quotes are used correctly. For example, the old quoting rule of bind variables consisting of full object attribute names was incorrect because it can lead to ambiguous column references. Let s say we have an expression LTRIM(: A.B.C ) . Using the old quoting rule, this bind variable can refer to object attribute columns A . B . C , A.B .C , and A . B.C . To avoid this confusion, use the new quoting rule for object attribute bind variables, which is to quote each attribute name independently as needed. In the preceding example, if the intended object attribute column is A.B.C , then the expression rewritten as LTRIM(:A.B.C) or LTRIM(:A . B . C ) will not lead to ambiguities.

SQL*Loader-00295: Warning: Table string, Column string - Quoting rule of object attribute bind variables has changed.

SQL*Loader-00295: Warning: Table string, Column string - Quoting rule of object attribute bind variables has changed.

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.

Action: This is only a warning message. Because the quoting rule of object attribute bind variables has changed, it is recommended that the control file be replaced with the new rule. With the new rule, a full object attribute bind variable name is not enclosed in its entirety in double quotes. Instead, each attribute name in the bind variable should be independently quoted as needed. Note that each attribute name is actually an identifier on its own and thus should follow the quoting rules for an identifier. For example, bind variable :A.B.C here consists of 3 attribute names (or identifiers): A , B , and C .

SQL*Loader-00294: invalid name % specified in TREAT AS clause

SQL*Loader-00294: invalid name % specified in TREAT AS clause

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.

Action: Verify that the type name has valid characters and is not too long. Also, ensure that all quoted strings are terminated.

SQL*Loader-00293: Missing XMLTYPE directive in control file for table string

SQL*Loader-00293: Missing XMLTYPE directive in control file for table string

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

Action: Add XMLTYPE directive to control file.

SQL*Loader-00292: ROWS parameter ignored when an XML, LOB or VARRAY column is loaded

SQL*Loader-00292: ROWS parameter ignored when an XML, LOB or VARRAY column is loaded

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.

Action: Remove the ROWS parameter from the command-line arguments.

SQL*Loader-00291: Invalid bind variable string in SQL string for column string.

SQL*Loader-00291: Invalid bind variable string in SQL string for column string.

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.

SQL*Loader-00290: PIECED keyword (on column string) allowed only for lob or long columns

SQL*Loader-00290: PIECED keyword (on column string) allowed only for lob or long columns

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.

SQL*Loader-00289: SQL string for column string occludes SQL string for column string.

SQL*Loader-00289: SQL string for column string occludes SQL string for column string.

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.

Action: Correct the control file so that only the column object or its attribute has a SQL string, but not both.

SQL*Loader-00288: Delimiters may not be specified for collections stored in SDF.

SQL*Loader-00288: Delimiters may not be specified for collections stored in SDF.

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 or 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, then you must use COUNT to indicate the number of elements in the secondary data file that are stored in the file.

SQL*Loader-00287: No control file name specified.

SQL*Loader-00287: No control file name specified.

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.

SQL*Loader-00286: ROWS parameter is not supported when loading an IOT.

SQL*Loader-00286: ROWS parameter is not supported when loading an IOT.

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.

SQL*Loader-00285: %s may be used only in conventional path.

SQL*Loader-00285: %s may be used only in conventional path.

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

Action: Use the conventional path load.

SQL*Loader-00284: Warning: Input data file string specified multiple times.

SQL*Loader-00284: Warning: Input data file string specified multiple times.

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 or BADDN or DISCARDFILE or DISCARDDN or DISCARDS.

SQLLoader client does not have knowledge of the given character set ID. Possible mis-match of NLS data on the client and server side. SQLLoader-00283: file processing string string ignored for INFILE *

SQL*Loader client does not have knowledge of the given character set ID. Possible mis-match of NLS data on the client and server side. SQL*Loader-00283: file processing string string ignored for INFILE *

Cause: The SQL*Loader control file specified INFILE * for a load data file along with an optional file processing string. This message is a warning that the file processing string will be ignored since SQLLDR will expect the data to have the same record format as the SQL*Loader control file.

Action: If the data in the SQL*Loader control file is in the same format as the rest of the SQL*Loader control file, then you don t need to do anything. Removing the file processing string will get rid of this error message. If the data in the

SQL*Loader-00282: Unable to locate character set handle for character set ID (number).

SQL*Loader-00282: Unable to locate character set handle for character set ID (number).

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

Action: The character set ID was obtained from the database server, the

SQL*Loader-00281: Warning: ROWS parameter ignored in parallel mode.

SQL*Loader-00281: Warning: ROWS parameter ignored in parallel mode.

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

Action: Remove the ROWS parameter from the command-line arguments or specify a non-parallel direct load to have save points performed.

SQL*Loader-00280: table string is a temporary table

SQL*Loader-00280: table string is a temporary table

Cause: The sqlldr utility does not load temporary tables. Note that if sqlldr did allow loading of temporary tables, the data would disappear after the load completed.

Action: Load the data into a non-temporary table.

SQL*Loader-00279: Only APPEND mode allowed when parallel load specified.

SQL*Loader-00279: Only APPEND mode allowed when parallel load specified.

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

Action: Change the SQL*Loader control file to use the APPEND keyword and re-invoke the parallel loader.

SQL*Loader-00278: Incorrect file specification for parallel load.

SQL*Loader-00278: Incorrect file specification for parallel load.

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

Action: Correct the filename and re-invoke parallel loader.

SQL*Loader-00277: Local file specification overrides global file specification.

SQL*Loader-00277: Local file specification overrides global file specification.

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

Action: This is only a warning message. Table level options take precedence over global options. Drop the table level options statement if this is not the intent.

SQLLoader control file. SQLLoader-00276: Local storage option overrides global storage.

SQL*Loader control file. SQL*Loader-00276: Local storage option overrides global storage.

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

Action: This is only a warning message. Table level options take precedence over global options. Drop the table level options statement if this is not the intent.

SQLLoader control file. SQLLoader-00275: Data is in control file but INFILE * has not been specified.

SQL*Loader control file. SQL*Loader-00275: Data is in control file but INFILE * has not been specified.

Cause: The INFILE specification was not entered in the SQL*Loader control file.

Action: If data in the SQL*Loader control file is to be read, specify INFILE * in the

SQLLoader control file. SQLLoader-00274: At least 2 read buffers have to be specified.

SQL*Loader control file. SQL*Loader-00274: At least 2 read buffers have to be specified.

Cause: Fewer than 2 read buffers have been specified.

Action: Specify at least 2 read buffers in the READBUFFERS statement, in the

SQL*Loader-00273: READBUFFERS may be used only in direct path.

SQL*Loader-00273: READBUFFERS may be used only in direct path.

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

Action: Use the direct path or remove the READBUFFERS specification from the

SQL*Loader-00272: Table level OPTIONS statement ignored.

SQL*Loader-00272: Table level OPTIONS statement ignored.

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

Action: Remove the OPTIONS statement from the SQL*Loader control file.

SQL*Loader-00271: Not a Parallel load. Table level OPTIONS statement ignored.

SQL*Loader-00271: Not a Parallel load. Table level OPTIONS statement ignored.

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

Action: Remove the OPTIONS statement from the SQL*Loader control file.

SQL*Loader-00270: TERMINATED BY EOF valid only for CHAR or RAW datatypes

SQL*Loader-00270: TERMINATED BY EOF valid only for CHAR or RAW datatypes

Cause: A field description in the SQL*Loader control file used the TERMINATED BY EOF option when the field was not a RAW or CHAR datatype.

Action: Modify the SQL*Loader control file to either remove the TERMINATED BY EOF clause or change the datatype for the field to be CHAR or RAW.

SQL*Loader-00269: Null string not allowed as clause comparison text.

SQL*Loader-00269: Null string not allowed as clause comparison text.

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

Action: Modify the clause to compare to at least one character.

SQLLoader control file. SQLLoader-00268: UNRECOVERABLE keyword may be used only in direct path.

SQL*Loader control file. SQL*Loader-00268: UNRECOVERABLE keyword may be used only in direct path.

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

Action: Use the direct path load or remove the keyword. (Conventional path loads are always recoverable).

SQL*Loader-00267: Control file must be first data file.

SQL*Loader-00267: Control file must be first data file.

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

Action: Move the INFILE * clause so that it is the first datafile declared in the

SQL*Loader-00266: Unable to locate character set handle for string.

SQL*Loader-00266: Unable to locate character set handle for string.

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

Action: Correct the character set name.

SQL*Loader-00265: Unable to get default character set name.

SQL*Loader-00265: Unable to get default character set name.

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

Action: Supply a character set name with the CHARACTERSET keyword.

SQL*Loader-00264: File mode token string parsed but ignored

SQL*Loader-00264: File mode token string parsed but ignored

Cause: An obsolete file mode token was used in the SQL*Loader control file. As of Release 1.1 of SQL*Loader, the file-processing options string is used to control file processing, rather than keywords like STREAM, RECORD, FIXED, and VARIABLE.

Action: No action required. This message is informational. Removing the obsolete keywords will eliminate the message without changing the way in which the datafile is processed.

SQL*Loader-00263: PIECED column string must be last specified column in table string

SQL*Loader-00263: PIECED column string must be last specified column in table string

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

Action: Remove the PIECED keyword or place the column last.

SQLLoader control file. SQLLoader-00262: PIECED keyword (on column string) allowed only when path is direct

SQL*Loader control file. SQL*Loader-00262: PIECED keyword (on column string) allowed only when path is direct

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

Action: Remove the PIECED keyword or use the direct path load.

SQL*Loader-00261: illegal use of TERMINATED BY for RAW field

SQL*Loader-00261: illegal use of TERMINATED BY for RAW field

Cause: The TERMINATED BY option cannot be used for loading data of type RAW from the data file. 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-00260: TERMINATED BY EOF option available only with LOBFILE option

SQL*Loader-00260: TERMINATED BY EOF option available only with LOBFILE option

Cause: The TERMINATED BY EOF option can be used only when describing data to be loaded from a LOBFILE. It cannot be specified at the table level and it cannot be for data in regular data files.

Action: Verify that you have specified the correct option for TERMINATED BY and verify that the TERMINATED BY option is specified for the correct fields.

SQL*Loader-00259: Could not escalate DDL share lock to exclusive on table string

SQL*Loader-00259: Could not escalate DDL share lock to exclusive on table string

Cause: This error occurs when another user has a parse lock on the table, for example, when another user is doing a select on the table. The parse lock should clear momentarily.

Action: Give the parse lock a chance to clear and then retry or else use the conventional path load.

SQL*Loader-00258: Maximum number of SORTED INDEXES (number) exceeded on table string

SQL*Loader-00258: Maximum number of SORTED INDEXES (number) exceeded on table string

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

Action: Reduce the number of indexes specified in the SORTED INDEX clause or use the conventional path load instead of the direct path load.

SQL*Loader-00257: TERMINATED BY EOF option not valid with ENCLOSED BY option

SQL*Loader-00257: TERMINATED BY EOF option not valid with ENCLOSED BY option

Cause: A field description in the SQL*Loader control file contains both the TERMINATED BY EOF and the ENCLOSED BY options. These options are mutually exclusive.

Action: Remove either or both of the clauses.

SQL*Loader-00256: SORTED INDEXES option allowed only for direct path

SQL*Loader-00256: SORTED INDEXES option allowed only for direct path

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

Action: Specify a direct path load with DIRECT=TRUE on the command line, remove the statement from the SQL*Loader control file, or

SQLLoader-00255: Log file for error recovery not used by SQLLoader

SQL*Loader-00255: Log file for error recovery not used by SQL*Loader

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

Action: No action required. This is an informational message.

SQL*Loader-00254: Cannot have DISCARDFILE specs here when multiple data files

SQL*Loader-00254: Cannot have DISCARDFILE specs here when multiple data files

Cause: The SQL*Loader 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.