12C ORA-错误汇总18 ORA-57000 to ORA-65535 EXP-00000 to EXP-00114 IMP-00000 to IMP-00402 SQL*Loader-0010

ORA-57000: TimesTen IMDB error: string
Cause: An error occurred during a TimesTen operation.
Action: Look up the error code in the TimesTen error documentation to diagnose.
31-2 Oracle Database Error Messages


ORA-60001 to ORA-65535 2 3
ORA-60001: adding (string) blocks to save undo segment in tablespace string with
MAXSIZE (string)
Cause: Save undo for the offline tablespace at segment MAXSIZE.
Action: Check the storage parameters for the system tablespace. The tablespace
needs to be brought back online so the undo can be applied.
ORA-60002: adding (string) blocks to temporary segment in tablespace string with
MAXSIZE (string)
Cause: Extending a temporary segment violated MAXSIZE limit.
Action: Increase the MAXSIZE limit and retry command.
ORA-60003: adding (string) blocks to table string.string partition string with
MAXSIZE (string)
Cause: Extending a table partition violated MAXSIZE limit.
Action: Increase the MAXSIZE limit and retry command.
ORA-60004: adding (string) blocks to table string.string with MAXSIZE (string)
Cause: Extending a table violated MAXSIZE limit.
Action: Increase the MAXSIZE limit and retry command.
ORA-60005: adding (string) blocks to cluster string.string with MAXSIZE (string)
Cause: Extending a cluster violated MAXSIZE limit.
Action: Increase the MAXSIZE limit and retry command.
ORA-60006: adding (string) blocks to index string.string partition string with
MAXSIZE (string)
Cause: Extending an index partition violated MAXSIZE limit.
Action: Increase the MAXSIZE limit and retry command.
ORA-60007: adding (string) blocks to index string.string subpartition string with
MAXSIZE (string)
Cause: Extending an index subpartition violated MAXSIZE limit.
Action: Increase the MAXSIZE limit and retry command.
ORA-60008: adding (string) blocks to index string.string with MAXSIZE (string)
Cause: Extending an index violated MAXSIZE limit.
Action: Increase the MAXSIZE limit and retry command.
32-2 Oracle Database Error Messages
ORA-60009: adding (string) blocks to LOB segment string.string partition string
with MAXSIZE (string)
Cause: Extending a LOB segment violated MAXSIZE limit.
Action: Increase the MAXSIZE limit and retry command.
ORA-60010: adding (string) blocks to LOB segment string.string with MAXSIZE
(string)
Cause: Extending a LOB segment violated MAXSIZE limit.
Action: Increase the MAXSIZE limit and retry command.
ORA-60011: adding (string) blocks to lob segment string.string subpartition string
with MAXSIZE (string)
Cause: Extending a LOB segment violated MAXSIZE limit.
Action: Increase the MAXSIZE limit and retry command.
ORA-60012: adding (string) blocks to table string.string subpartition string with
MAXSIZE (string)
Cause: Extending a table subpartition violated MAXSIZE limit.
Action: Increase the MAXSIZE limit and retry command.
ORA-60013: invalid MAXSIZE storage option value
Cause: Invalid value was specified for MAXSIZE storage clause.
Action: Correct the value and retry command.
ORA-60014: invalid MAXSIZE storage option value
Cause: Minimum of 1M should have been specified against the MAXSIZE storage
clause.
Action: Correct the value and retry command.
ORA-60015: invalid RETENTION storage option value
Cause: Value of MIN retention should have been nonzero.
Action: Correct the value and retry command.
ORA-60016: Operation not supported on SECUREFILE segment
Cause: The operation to ALTER FREELIST/RETENTION was not supported on
SECUREFILE segment.
Action: Check the LOB type and reissue the statement.
ORA-60018: adding string blocks to rollback segment string with MAXSIZE (string)
Cause: Extending a rollback segment violated MAXSIZE limit.
Action: Increase the MAXSIZE limit and retry command.
ORA-60019: Creating initial extent of size string in tablespace of extent size string
Cause: Creation of SECUREFILE segment failed due to small tablespace extent
size.
Action: Create tablespace with larger extent size and reissue command.
ORA-60025: Event for temp segment cleanup used for temp lobs
Cause: Temp LOB segments used for temporary LOBs are deleted only on session
exit which may lead to large amounts of memory being held across multiple
sessions.
ORA-60001 to ORA-65535 32-3
Action: Setting this event will cause temporary LOB segments to be freed when
there are no active temporary LOBs in the session. Setting this event will have a
significant performance impact as it can cause temporary lob segments to be
allocated and deleted many times during a session rather than once per session.
Use this event only when temporary LOB segment memory use is an issue.
ORA-60072: adding (string) blocks to heat map segment with MAXSIZE (string)
Cause: Extending the heat map segment violated the MAXSIZE limit.
Action: Increase the MAXSIZE limit.
ORA-60073: Heat map segment cannot be created
Cause: SYSAUX tablespace has uniform extent allocation and the extent size is
not a multiple of megabyte.
Action: Re-create SYSAUX tablespace with autoallocate extent management
policy or use the uniform extent size which is a multiple of megabyte.
ORA-62001: value for parameter cannot contain a comma
Cause: Parameter value contained a comma.
Action: Remove the comma from the parameter value.
ORA-62007: Encountered a value of unsupported type or size for XPath (string)
Cause: Encountered a value of unsupported type in a SQL/XML DML operator.
SQL/XML operators, such as UPDATEXML, expect value operands of type
VARCHAR2 and XMLTYPE. XML DML replication is not supported for
SQL/XML DML operators with values of unsupported types or very large values
of supported types.
Action: Rewrite the UPDATE statement using XQuery update or set event 19027
level 1 to dump XML Document as against XMLDiff in redo log.
ORA-62008: Cannot rewrite a newer version of XML redo diff (encountered: string,
supported: string)
Cause: Encountered a newer version of XML redo diff that is not supported.
Action: Use RDBMS version that supports rewrite of given version of XML redo
diff.
ORA-62009: An attempt to encode invalid XML character string in supplemental log
has occurred.
Cause: An attribute was being populated or updated with characters which are
not valid for XML and therefore could not be supplementally logged.
Action: Store the desired value in a RAW or BLOB attribute.
ORA-62500: function is not allowed outside of MATCH_RECOGNIZE clause
Cause: The function was specified outside of the MATCH_RECOGNIZE clause.
This function is only allowed in the MATCH_RECOGNIZE clause.
Action: Rewrite the SQL statement.
ORA-62501: invalid value specified for bounded quantifier in MATCH_
RECOGNIZE clause
Cause: The specified lower bound or upper bound value was greater than
UB4MAXVAL. The lower bound value must be non-negative. The upper bound
value must be strictly positive. The upper bound value must be greater than or
equal to the lower bound value.
Action: Choose an appropriate value and retry the operation.
32-4 Oracle Database Error Messages
ORA-62502: invalid variable name
Cause: The specified variable name was invalid. Variable names are not allowed
to be "^", "$", or "*".
Action: Choose an appropriate variable name and retry the operation.
ORA-62503: illegal variable definition
Cause: The specified variable definition was invalid. Variables defined in the
DEFINE clause must be in the PATTERN clause. Variables defined in the SUBSET
clause cannot be in the PATTERN clause. Variables cannot be defined twice either
in the SUBSET clause or the DEFINE clause.
Action: Choose an appropriate variable and retry the operation.
ORA-62504: illegal variable reference
Cause: The referenced variable was invalid. Variables referenced in the SUBSET
clause must be in the PATTERN clause. Variables referenced in the DEFINE clause,
the MEASURES clause, and the AFTER MATCH SKIP TO must be in the
PATTERN clause or defined in the SUBSET clause.
Action: Choose an appropriate variable and retry the operation.
ORA-62505: expression needs to be aliased
Cause: The expression was not aliased. MEASURES clause items have to be
aliased.
Action: Choose an appropriate variable and retry the operation.
ORA-62506: illegal nesting of operators in MATCH_RECOGNIZE clause
Cause: An attempt was made to nest aggregates/FIRST/LAST/PREV/NEXT.
Aggregates/FIRST/LAST/PREV/NEXT cannot be nested. The only exception
allowed is PREV/NEXT(FIRST/LAST()).
Action: Modify the query and retry the operation.
ORA-62507: illegal use of MATCH_NUMBER or CLASSIFIER in MATCH_
RECOGNIZE clause
Cause: An attempt was made to use MATCH_NUMBER or CLASSIFIER in the
MATCH_RECOGNIZE clause. CLASSIFIER and MATCH_NUMBER can only be
used in the MEASURES clause. CLASSIFIER can only be used if the query is ALL
ROWS PER MATCH. CLASSIFIER and MATCH_NUMBER cannot be used inside
aggregates/FIRST/LAST/PREV/NEXT.
Action: Modify the query and retry the operation.
ORA-62508: illegal use of aggregates or navigation operators in MATCH_
RECOGNIZE clause
Cause: An attempt was made to define aggregates/FIRST/LAST/PREV/NEXT
over multiple variables. Aggregates/FIRST/LAST/PREV/NEXT cannot be
defined over multiple variables.
Action: Modify the query and retry the operation.
ORA-62509: illegal use of RUNNING or FINAL in MATCH_RECOGNIZE clause
Cause: An attempt was made to use RUNNING or FINAL in MATCH_
RECOGNIZE. RUNNING or FINAL can only be used on aggregate/FIRST/LAST.
FINAL aggregate/FIRST/LAST is not allowed in the DEFINE clause.
Action: Modify the query and retry the operation.
ORA-60001 to ORA-65535 32-5
ORA-62510: Correlated subqueries are not allowed in MATCH_RECOGNIZE
clause.
Cause: An attempt was made to use correlated subqueries in the MATCH_
RECOGNIZE clause. Correlated subqueries are currently not allowed in the
MATCH_RECOGNIZE clause.
Action: Modify the query and retry the operation.
ORA-62511: Correlation variables are not allowed in MATCH_RECOGNIZE clause.
Cause: An attempt was made to use correlation variables in the MATCH_
RECOGNIZE clause. Correlation variables are currently not allowed in the
MATCH_RECOGNIZE clause.
Action: Modify the query and retry the operation.
ORA-62512: This aggregate is not yet supported in MATCH_RECOGNIZE clause.
Cause: An unsupported aggregate was specified in the MATCH_RECOGNIZE
clause. Only COUNT, SUM, AVG, MIN, and MAX are currently supported in the
MATCH_RECOGNIZE clause. Distinct aggregates are currently not supported in
the MATCH_RECOGNIZE clause.
Action: Modify the query and retry the operation.
ORA-62513: Quantified subpatterns that can have empty matches are not yet
supported.
Cause: There were empty matches for the quantified subpattern in the PATTERN
clause. Quantified subpatterns are currently required to match one or more rows.
Action: Modify the query and retry the operation.
ORA-62514: AFTER MATCH SKIP TO variable is not bounded in the match found.
Cause: AFTER MATCH SKIP TO variable was not bound in the match found due
to pattern operators such as |, *, ?, and so on.
Action: Modify the query and retry the operation.
ORA-62515: Exclusion syntax cannot be used with WITH UNMATCHED ROWS.
Cause: An attempt was made to use exclusion syntax with WITH UNMATCHED
ROWS. Exclusion syntax {- -} cannot be used with WITH UNMATCHED ROWS.
Action: Modify the query and retry the operation.
ORA-62516: The PARTITION BY, ORDER BY, or MEASURES clause is too large for
MATCH_RECOGNIZE.
Cause: The number of items in PARTITION BY, ORDER BY, or MEASURES clause
exceeded the maximum allowed. There cannot be more than UB2MAXVAL
elements in PARTITION BY, ORDER BY, or MEASURES clause.
Action: Modify the query and retry the operation.
ORA-62517: Next match starts at the same point last match started.
Cause: AFTER MATCH SKIP TO option repositioned the next match at the start
of the previous one resulting in an infinite loop.
Action: Modify the query and retry the operation.
ORA-62518: MATCH_RECOGNIZE pattern is too large.
Cause: MATCH_RECOGNIZE pattern was too large. More than UB2MAXVAL
elements in alternation, concatenation, or permute, or more than UB4MAXVAL
states in the state machine are currently not supported. Permute with more than 7
32-6 Oracle Database Error Messages
elements or bounded quantifier bound greater than 200 are also currently not
supported.
Action: Modify the query and retry the operation.
ORA-62519: Subquery inside MATCH_RECOGNIZE cannot contain MATCH_
RECOGNIZE.
Cause: An attempt was made to use a subquery containing a MATCH_
RECOGNIZE clause inside a MATCH_RECOGNIZE clause. Subqueries containing
MATCH_RECOGNIZE clauses are currently not allowed in the MATCH_
RECOGNIZE clause.
Action: Modify the query and retry the operation.
ORA-62520: illegal offset for MATCH_RECOGNIZE navigation operators
Cause: An attempt was made to use something other than a constant or a bind
variable as the offset for MATCH_RECOGNIZE navigation operators FIRST,
LAST, PREV, or NEXT. Offset for MATCH_RECOGNIZE navigation operators
have to be constants or bind variables.
Action: Modify the query and retry the operation.
ORA-62521: MATCH_RECOGNIZE is not supported on lateral views
Cause: An attempt was made to use MATCH_RECOGNIZE on a lateral view,
which is not supported.
Action: Modify the query and retry the operation.
ORA-62550: Invalid SQL ROW LIMITING expression was specified.
Cause: The SQL ROW LIMITING expression contained components other than
literals, binds, correlation variables, or subqueries.
Action: Modify the SQL ROW LIMITING expression and retry the operation.
ORA-63000: operation disallowed: data file string is being moved
Cause: The specified data file was being moved.
Action: Wait for the move operation to complete and retry the command.
ORA-63001: file error during move operation
Cause: The move operation encountered an error for the moved data file. The
error might be caused by file going offline or by an I/O error. See alert or trace
files in all instances for further information.
Action: Retry the move command.
ORA-63002: a data file copy that is not current
Cause: An obsolete copy of a data file left from a data file move operation was
used for the CREATE CONTROLFILE command or file header read.
Action: Pass a valid file or perform a media recovery on the file.
ORA-63003: a half-done data file copy
Cause: A half-done copy of a data file created from a previous data file move
operation was used for the CREATE CONTROLFILE command or file header
read.
Action: Check file headers and pass only valid files.
ORA-63004: Database names in file headers are inconsistent: string and string.
Cause: Differring database names were found in database file headers.
ORA-60001 to ORA-65535 32-7
Action: Check that correct and valid data files are used.
ORA-63997: file size refresh failed
Cause: An operating system error or device error occurred when retrieving the
file's size.
Action: Remedy the operating system or device errors mentioned in the error
stack and then perform crash recovery.
ORA-63998: undo tablespace file suffered media failure
Cause: An undo tablespace file was detected as inaccessible due to media failure.
Action: Restore accessibility to the file mentioned in the error stack and restart the
instance.
ORA-63999: data file suffered media failure
Cause: A data file was detected as inaccessible due to media failure.
Action: Restore accessibility to the file mentioned in the error stack and restart the
instance.
ORA-64000: specified path already exists
Cause: The pathname of a new item specified in a DBFS API operation already
exists.
Action: Specify a valid, new pathname for the operation.
ORA-64001: invalid parent directory in specified path
Cause: The pathname of an item specified in a DBFS API operation has one or
more invalid parent components.
Action: Specify a valid pathname with valid parent components for the operation.
ORA-64002: specified path is invalid
Cause: The pathname of an item specified in a DBFS API operation is invalid.
Action: Specify a valid pathname for the operation.
ORA-64003: an unsupported operation was invoked
Cause: The current DBFS API operation is unsupported by a provider.
Action: Use the provider feature set to invoke only supported operations.
ORA-64004: an invalid combination of arguments was specified
Cause: The current DBFS API operation specifies an invalid combination of
arguments for the specified pathname(s) and operation.
Action: Specify a valid combination of pathname(s) and arguments.
ORA-64005: access control checks failed
Cause: The current DBFS API operation failed access control checks for the
pathname(s) being accessed.
Action: Specify valid pathname(s) and principal for the operation, or take
store-specific actions to enable access.
ORA-64006: lock conflict in current operation
Cause: A DBFS API locking operation could not be completed due to conflicts in
the locking protocol.
Action: Follow the proper lock/unlock protocol according to the provider feature
set.
32-8 Oracle Database Error Messages
ORA-64007: invalid store specified
Cause: The current operation specifies an invalid store name.
Action: Specify a valid store name for the operation.
ORA-64008: invalid mount-point specified
Cause: The current operation specifies an invalid mount-point.
Action: Specify a valid mount-point for the operation.
ORA-64009: invalid provider specified
Cause: The current operation refers to an invalid or incomplete or
non-conformant store provider package.
Action: Specify a valid, complete, and conformant (per "dbms_dbfs_content_spi")
store provider package.
ORA-64010: cannot modify store via read-only mount
Cause: The current operation attempts to modify a store via a read-only mount
(or specifies a read-only store).
Action: Specify a valid modifiable store/mount for the operation.
ORA-64011: cross store operation
Cause: The current operation attempts to span 2 or more different stores and
cannot be implemented entirely by the DBFS API.
Action: Split the operation, at the application-level, into multiple sub-operations
to implement the same overall functionality.
ORA-64012: specified path is a directory
Cause: The current operation specifies a path that is a directory element, when a
non-directory element is expected.
Action: Specify a path of the proper type for the operation.
ORA-64013: specified path is not a directory
Cause: The current operation specifies a path that is not a directory element,
when a directory element is expected.
Action: Specify a path of the proper type for the operation.
ORA-64014: directory not empty
Cause: The current operation specifies a directory element that is not empty as
required.
Action: Specify an empty directory element.
ORA-64101: Cannot alter both a structured and an unstructured component of an
XMLIndex in the same ALTER INDEX statement.
Cause: An attempt was made to alter the unstructured component and structured
component of an XMLIndex at the same time.
Action: Use separate ALTER INDEX statements to change an unstructured
component and a structured component of an XMLIndex.
ORA-64102: Cannot create an XMLIndex with a structured component on a CLOB
column within the object-relational storage model.
Cause: An attempt was made to create an XMLIndex with a structured
component on a CLOB column within the object-relational storage model.
ORA-60001 to ORA-65535 32-9
Action: Only unstructured XML indexes can be created on a CLOB column within
the object-relational storage model.
ORA-64103: Cannot create an XMLIndex on an object-relational XML type table or
column.
Cause: An attempt was made to create an XMLIndex on an XML type table or
column that uses the object-relational storage model.
Action: The object-relational storage model does not support an XMLIndex.
ORA-64104: Column name already used by internal column of the structured
component of the XMLIndex.
Cause: An attempt was made to use a column name already in use by an internal
column of the structured component of the XMLIndex.
Action: Chose another column name.
ORA-64105: Cannot create domain index on XMLIndex internal tables.
Cause: An attempt was made to create a domain index on an internal table of an
XMLIndex.
Action: Create the domain index on the base table.
ORA-64106: Incorrect use of comma(,) punctuation in COLUMN definitions.
Cause: An attempt was made to define COLUMNS with incorrect use of comma
punctuation.
Action: Properly separate COLUMN definitions with comma punctuation.
ORA-64107: The XMLIndex has been successfully altered but the metadata could
not be updated.
Cause: An internal error occured when updating the index metadata. The dbms_
metadata.get_ddl function may return improper metadata.
Action: contact Oracle Support Services.
ORA-64108: Cannot truncate a table that has an XMLIndex whose internal table has
been indexed using Oracle Text.
Cause: An attempt was made to truncate a table that has an XMLIndex whose
internal table has been indexed using Oracle Text.
Action: Drop the Oracle Text index on the XMLIndex internal table.
ORA-64109: XMLIndex: problems encountered during the dropping of statistics
Cause: See associated error message.
Action: Correct the error and retry command.
ORA-64110: XMLIndex: problems encountered during the gathering of statistics
Cause: See associated error message.
Action: Correct the error and retry command.
ORA-64111: XMLIndex: problems encountered during EXPORT
Cause: See associated error message.
Action: Correct the error and retry command.
ORA-64112: XMLIndex: problems encountered during IMPORT
Cause: See associated error message.
Action: Correct the error and retry command.
32-10 Oracle Database Error Messages
ORA-64113: XMLIndex: XDB.XDB$XIDX_IMP_T still has bad data for
"string"."string"
Cause: See associated error message.
Action: Ask the DBA to delete all the rows that belong to the given schema_
name.index_name from the system table XDB.XDB$XIDX_IMP_T."
ORA-64115: XMLIndex Exchange Partition: the table has no XMLIndex
Cause: The non-partitioned table had no XMLIndex.
Action: None
ORA-64116: XMLIndex Exchange Partition: incompatible XPath subsets
Cause: The XMLIndexes on the two tables had different path subsets.
Action: Correct the error and retry the command.
ORA-64117: XMLIndex Exchange Partition: incompatible modes for asynchronous
DML
Cause: The XMLIndexes on the two tables had different deferred DML modes.
Action: Correct the error and retry the command.
ORA-64118: XMLIndex Exchange Partition: incompatible unstructured components
Cause: One of the XMLIndexes had no unstructured component.
Action: Correct the error and retry the command.
ORA-64119: XMLIndex Exchange Partition: incompatible structured components
Cause: One of the XMLIndexes had no structured component.
Action: Correct the error and retry the command.
ORA-64120: XMLIndex Exchange Partition: incompatible structured components
Cause: The XMLIndexes had different structured components.
Action: Correct the error and retry the command.
ORA-64121: XMLIndex DDL: failure of the internal "string"
Cause: See associated error message.
Action: Correct the error and retry command.
ORA-64122: XMLIndex DDL: failure of the recursive "string"
Cause: See associated error message.
Action: Correct the error and retry command.
ORA-64123: XMLIndex DDL: failure of a recursive DDL
Cause: See associated error message.
Action: Correct the error and retry command.
ORA-64124: XMLIndex: failure during the setting of an event
Cause: See associated error message.
Action: Correct the error and retry command.
ORA-64125: XMLIndex: failure during the resetting of an event
Cause: See associated error message.
Action: Correct the error and retry command.
ORA-60001 to ORA-65535 32-11
ORA-64126: XMLIndex Table Function: failure at the start of the function
Cause: See associated error message.
Action: Examine the error messages and take appropriate action.
ORA-64127: XMLIndex Table Function: failure at the beginning of the function
Cause: See associated error message.
Action: Examine the error messages and take appropriate action.
ORA-64128: XMLIndex Table Function: failure during the function evaluation
Cause: See associated error message.
Action: Examine the error messages and take appropriate action.
ORA-64129: XMLIndex Table Function: failure at the end of the function
Cause: See associated error message.
Action: Examine the error messages and take appropriate action.
ORA-64130: XMLIndex: invalid namespace mapping "string"
Cause: Namespace mapping was invalid. The syntax is XMLNS="string".
Action: Check the namespace string, correct the error and retry command.
ORA-64131: XMLIndex Metadata: failure during the looking up of the dictionary
Cause: See associated error message.
Action: Correct the error and retry command.
ORA-64132: XMLIndex Metadata: failure during the updating of the dictionary
Cause: See associated error message.
Action: Correct the error and retry command.
ORA-64133: XMLIndex DML: failure of the internal "string"
Cause: See associated error message.
Action: Correct the error and retry command.
ORA-64134: XMLIndex DML: failure of the recursive "string"
Cause: See associated error message.
Action: Correct the error and retry command.
ORA-64135: XMLIndex DML: failure of a recursive DML
Cause: See associated error message.
Action: Correct the error and retry command.
ORA-64136: XMLIndex Asynchronous DML: synchronization failure
Cause: See associated error message.
Action: Correct the error and retry command.
ORA-64137: Cannot drop an XMLIndex whose internal table has been indexed
using Oracle Text.
Cause: An attempt was made to drop an XMLIndex whose internal table has been
indexed using Oracle Text.
Action: Drop the Oracle Text index on the XMLIndex internal table.
32-12 Oracle Database Error Messages
ORA-64138: Cannot drop groups from an XMLIndex whose internal table has been
indexed using Oracle Text.
Cause: An attempt was made to drop groups from an XMLIndex whose internal
table has been indexed using Oracle Text.
Action: Drop the Oracle Text index on the XMLIndex internal table.
ORA-64139: The type of VIRTUAL column is not XMLTYPE
Cause: An attempt was made to create an XML index with VIRTUAL column not
of XMLTYPE.
Action: Specify the type of VIRTUAL column to be XMLTYPE.
ORA-64140: missing chaining XMLTABLE for VIRTUAL column in the index
Cause: An attempt was made to create an XML index with VIRTUAL column but
without required chaining XMLTABLE.
Action: Specify a chaining XMLTABLE after VIRTUAL column.
ORA-64141: Can only have a single XMLType column when a table is shared.
Cause: An attempt was made to create a shared table with more than one
columns.
Action: Specify a correct shared table definition with only one XMLType column.
ORA-64142: Shared tables must have same semantics for truncation.
Cause: An attempt was made to create shared tables with inconsistent semantics
for truncation. Either all shared tables should have or should not have
(TRUNCATE) keyword.
Action: Be consistent with (TRUNCATE) keyword while defining shared tables.
ORA-64143: Can only share an existing XMLIndex table with an XMLTYPE column.
Cause: An attempt was made to share a table without an XMLTYPE column.
Action: Drop the group containing the XMLIndex table without an XMLTYPE
column and re-create the group with new definition.
ORA-64144: Shared tables must have equivalent paths.
Cause: An attempt was made to share a table with different paths.
Action: Specify a correct shared table definition with appropriate paths.
ORA-64145: This XMLIndex rewrite failed
Cause: One of the rewrites being tried by XMLIndex engine failed.
Action: None. This error is for understanding the trace file of XMLIndex rewrite.
ORA-64146: Nonblocking alter XMLIndex error
Cause: Internal error.
Action: None
ORA-64147: Invalid use of NONBLOCKING COMPLETE or ABORT.
Cause: NONBLOCKING COMPLETE or ABORT is only allowed for XMLIndex
that is being modified using NONBLOCKING ADD_GROUP or ADD_COLUMN.
Action: None
ORA-64148: Cannot complete nonblocking alter index operation.
ORA-60001 to ORA-65535 32-13
Cause: NONBLOCKING COMPLETE is only allowed for XMLIndex that is being
modified using NONBLOCKING ADD_GROUP or ADD_COLUMN and there are
no pending rows left.
Action: Call DBMS_XMLINDEX.PROCESS_PENDING to finish pending work.
ORA-64149: Invalid alter XMLIndex operation.
Cause: An attemp was made to alter an XMLIndex that is already being modified
using NONBLOCKING ADD_GROUP or ADD_COLUMN. Only
NONBLOCKING COMPLETE or ABORT alter index operations are allowed. Also,
NONBLOCKING operation is not allowed with alter index rebuild.
Action: Call DBMS_XMLINDEX.PROCESS_PENDING to finish pending work
and then execute NONBLOCKING COMPLETE to successfully finish existing
NONBLOCKING operation. Execute NONBLOCKING ABORT to cancle existing
NONBLOCKING operation.
ORA-64151: Invalid use of DBMS_XMLINDEX.PROCESS_PENDING.
Cause: DBMS_XMLINDEX.PROCESS_PENDING was called on an index that was
not modified using NONBLOCKING ADD_GROUP or ADD_COLUMN.
Action: None
ORA-64152: There are no pending rows to process.
Cause: DBMS_XMLINDEX.PROCESS_PENDING was called on an index that
does not have any pending rows to process.
Action: Execute NONBLOCKING COMPLETE operation to complete the
nonblocking alter index.
ORA-64201: unregistered LOB value encountered
Cause: The LOB value associated with the input locator did not exist in client-side
reference tables.
Action: This is an internal error. Contact Oracle Support Services.
ORA-64202: remote temporary or abstract LOB locator is encountered
Cause: Local database encountered a temporary or abstract LOB created on a
remote database. Remote access to temporary or abstract LOB is not supported.
Action: Avoid remote queries that return a temporary or abstract LOB.
ORA-64203: Destination buffer too small to hold CLOB data after character set
conversion.
Cause: An attempt was made to convert CLOB to CHAR, where the LOB size was
bigger than the buffer limit for CHAR types or the CHAR buffer was not big
enough to hold all data after character set conversion.
Action: Do one of the following:
* Make the LOB smaller before performing the conversion. for example, by using
SUBSTR on CLOB
* Use DBMS_LOB.SUBSTR to convert CLOB to CHAR.
ORA-64204: encountered partial multibyte character
Cause: The requested operation could not complete because a partial multibyte
character was found at the end of the input.
Action: Ensure that the input buffer ends with a complete multibyte character and
retry the operation.
32-14 Oracle Database Error Messages
ORA-64205: Cannot use other triggering events along with LOGICAL LOB
UPDATE event
Cause: An attempt was made to use other triggering events (such as INSERT,
DELETE and UPDATE) with the LOGICAL LOB UPDATE event.
Action: Create multiple triggers instead of sharing a trigger for multiple events.
ORA-64206: Cannot create INSTEAD OF LOGICAL LOB UPDATE trigger
Cause: INSTEAD OF LOGICAL LOB UPDATE trigger was not allowed.
Action: None
ORA-64207: Invalid LOGICAL LOB UPDATE trigger definition
Cause: The LOGICAL LOB UPDATE trigger could not be created on a non-LOB
column of a table. The column name has to be specified while creating the trigger.
Only one column name can be specified while creating the trigger.
Action: Specify LOGICAL LOB UPDATE trigger with a valid definition.
ORA-64208: FOR EACH ROW clause is required for before or after LOGICAL LOB
UPDATE triggers
Cause: An attempt was made to create a before or after LOGICAL LOB UPDATE
trigger without a FOR EACH ROW clause.
Action: Specify a FOR EACH ROW clause for a before/after LOGICAL LOB
UPDATE trigger.
ORA-64209: WHEN clause is not allowed for LOGICAL LOB UPDATE triggers
Cause: WHEN clause was specified for a LOGICAL LOB UPDATE trigger.
Action: Remove the WHEN clause when creating a LOGICAL LOB UPDATE
trigger.
ORA-64210: Cannot reference a trigger of a different type
Cause: The LOGICAL LOB UPDATE trigger did not follow other LOGICAL LOB
UPDATE triggers. Non-LOGICAL LOB UPDATE triggers cannot follow LOGICAL
LOB UPDATE triggers.
Action: None
ORA-64211: Cannot access other columns within a LOGICAL LOB UPDATE trigger
body
Cause: An attempt was made to access an invalid column. A LOGICAL LOB
UPDATE trigger can only access ROWID column and the column for which it was
specified. Access to other columns is not allowed.
Action: Remove references to other columns within a LOGICAL LOB UPDATE
trigger body.
ORA-64212: Cannot create a LOGICAL LOB UPDATE trigger on a view
Cause: A LOGICAL LOB UPDATE trigger could not be created on view.
Action: None
ORA-64213: Cannot create a compound LOGICAL LOB UPDATE trigger with
statement level actions
Cause: A compound LOGICAL LOB UPDATE trigger could not contain statement
level actions.
Action: None
ORA-60001 to ORA-65535 32-15
ORA-64214: Cannot create a crossedition LOGICAL LOB UPDATE trigger
Cause: Crossedition LOGICAL LOB UPDATE triggers were not supported.
Action: None
ORA-64215: PL/SQL subprogram 'string' for internal use only
Cause: An attempt was made to use a subprogram that is for internal Oracle
development use only.
Action: Do not use this unsupported subprogram. Refer to Oracle documentation
for available subprograms.
ORA-64300: Invalid compression level specified
Cause: The specified archive compression level value was invalid. Valid values
are LOW or HIGH.
Action: Choose a valid level and retry the operation.
ORA-64307: Exadata Hybrid Columnar Compression is not supported for
tablespaces on this storage type
Cause: An attempt was made to use Exadata Hybrid Columnar Compression on
unsupported storage.
Action: Create this table in a tablespace residing on Oracle Exadata, Oracle's Sun
ZFS or Pillar Axiom storage or use a different compression type.
ORA-64308: hybrid columnar compressed table cannot have column with LONG
data type
Cause: One of the following was attempted:
- Create a hybrid columnar compressed table with a LONG data type.
- Alter an existing table with a LONG data type to be hybrid columnar
compressed.
- Add a LONG data type column to a hybrid columnar compressed table.
Action: LONG data types are not supported with hybrid columnar compressed
tables. Create table without LONG column or change table to not be hybrid
columnar compressed. If adding a column, do not use LONG data type. If
modifying attributes of a column to change data type to LONG, the table cannot
be hybrid columnar compressed.
ORA-64309: Hybrid Columnar Compression with row-level locking is not
supported for tablespaces on this storage type.
Cause: An attempt was made to use Hybrid Columnar Compression with
row-level locking on an unsupported storage type.
Action: Create this table in a tablespace residing on Oracle Exadata storage or use
a different compression type.
ORA-64350: only one INMEMORY clause may be specified
Cause: INMEMORY was specified more than once.
Action: Specify each desired INMEMORY clause option only once.
ORA-64364: In-memory column store on Oracle RAC is only supported on
Oracle-engineered systems.
Cause: An attempt was made to use the in-memory column store feature with
Oracle RAC on an unsupported system.
32-16 Oracle Database Error Messages
Action: Disable Oracle RAC before attempting to use the in-memory column store
in this environment or use an Oracle-engineered system.
ORA-64367: In-memory column store FastStart tablespace is offline.
Cause: The FastStart feature was enabled but its tablespace was offline.
Action: Disable FastStart or bring the FastStart tablespace online.
ORA-64368: In-memory FastStart is only supported on Oracle-engineered systems.
Cause: An attempt was made to use the in-memory column store FastStart feature
on an unsupported system.
Action: Use FastStart on an Oracle-engineered system.
ORA-64369: In-memory FastStart Oracle Call Interface (OCI) error string
Cause: An OCI error occurred when enabling or disabling FastStart.
Action: Mannually correct the problem.
ORA-64401: This manageability package is only supported on Oracle RDBMS
versions 10.2, 11.1, and 11.2.
Cause: Package installation invoked on database version that was not 10.2, 11.1 or
11.2..
Action: Use Oracle databaseversion 10.2, 11.1, or 11.2.
ORA-64402: Invalid input. XMLSchema is null.
Cause: XMLSchema was not provided to the procedure or function call..
Action: Provide an XMLSchema.
ORA-64403: Input cannot be null
Cause: An input parameter was null.
Action: Provide input paramter.
ORA-64404: Input string cannot exceed 30 characters
Cause: An input string was provided whose length exceeded 30 character.
Action: Provide a shorter input string.
ORA-64405: No matching elements found. Zero annotations were applied.
Cause: The parameters provided to annotate the XMLSchema did not match any
entities in the XMLSchema.
Action: Correct the parameters.
ORA-64406: No matching elements found. Zero annotations were removed.
Cause: The parameters provided to annotate the XMLSchema did not match any
entities in the XMLSchema.
Action: Correct the parameters.
ORA-64407: Annotation maps to multiple elements.
Cause: The parameters provided to annotate the XMLSchema matched to
multiple entities in the XMLSchema.
Action: .
ORA-64408: Name for collection table too long.
Cause: The name for the collection table exceeded 25 characters.
Action: Reduce the length of the name of the collection table.
ORA-60001 to ORA-65535 32-17
ORA-64409: XPath could not be mapped to exactly one table.
Cause: XPath could not be mapped to existing table.
Action: Check input parameters.
ORA-64410: Invalid XPath.
Cause: The XPath string provided to the procedure was not valid.
Action: Check XPath string.
ORA-64411: Invalid collection table specified by XPath.
Cause: An invalid collection table was specified by the XPath string.
Action: Check XPath string.
ORA-64412: Procedure called on XML table with BINARY storage model.
Cause: The procedure renameCollectionTable did not work on binary storage
model.
Action: .
ORA-64413: Cannot disable constraints/indexes for non-global schemas owned by
other users or a non schema based table/column.
Cause: An attempt was made to disable constraints or indexes for non-global
schemas owned by other users or a non schema based table/column.
Action: Use an OR schema based table/column or change users to disable
constraints or indexes.
ORA-64414: Cannot enable constraints/indexes for non-global schemas owned by
other users or a non schema based table/column.
Cause: An attempt was made to enable constraints or indexes for schemas owned
by other users or for a non schema based table/column.
Action: Use an OR schema based table/column or change users to enable
constraints or indexes.
ORA-64415: Error in namespace declaration.
Cause: The namespace declaration was invalid.
Action: Correct namespace declaration.
ORA-64416: Table does not exist.
Cause: The tab_name parameter provided the name of a table that did not exist..
Action: Correct the tab_name parameter.
ORA-64417: Column does not exist in table.
Cause: The col_name parameter provided the name of a column that did not exist
in the given table.
Action: Correct the col_name parameter.
ORA-64418: Column not of XMLType.
Cause: The col_name parameter provided the name of a column that was not an
XMLType column.
Action: Correct the col_name parameter.
ORA-64419: Name for collection table already exists.
Cause: The name for the collection table could not be used because it already
exists.
32-18 Oracle Database Error Messages
Action: Use another name for collection table.
ORA-64420: Table not of XMLType.
Cause: The table_name parameter provided the name of a table that was not an
XMLType table.
Action: Correct the table_name parameter or provide the name of an XMLType
column in the table.
ORA-64477: Multiple token tables are not supported.
Cause: An attempt was made to create a new token table. If encountered during
an import, a critical patch was possibly missing on the export database.
Action: Use the default token table. If encountered during an import, apply the
appropriate patch on the export database and try the export and import again.
ORA-64600: duplicate or conflicting PARTITION or NOPARTITION specifications
Cause: The specifications were either a duplicate of each other or were conflicting.
Action: Remove the duplicate or conflicting specification.
ORA-64601: duplicate RESTART specified
Cause: The specified RESTART was a duplicate.
Action: Remove the duplicate specification.
ORA-64620: duplicate user tablespace specification
Cause: An attempt was made to create more than one user tablespace during
database creation.
Action: Modify the command to contain only one user tablespace.
ORA-64621: SQL statement length (string) exceeds maximum allowed length
(string)
Cause: An attempt was made to issue a SQL statement that exceeded the
maximum allowed length of a statement.
Action: Modify the SQL statement or the views to which it refers to fit within the
maximum length or split the SQL statement.
ORA-64700: Recovery Appliance is shutting down
Cause: The Recovery Appliance was in the process of shutting down. This
message is recorded in the incident log for the Recovery Appliance. When the
shutdown completes, the incident is marked as FIXED.
Action: Wait for the Recovery Appliance to complete its shutdown.
ORA-64701: storage location string can no longer honor its reservations.
Cause: The specified storage location did not contain enough space to fulfill the
reservations of all of the databases assigned to it. This error will be seen if a
storage location lost part of its disk space and was in the process of being repaired.
Action: Either shrink the reservations for the databases contained within the
storage location or add additional disk space to the storage location.
ORA-64702: error repairing container files for storage location string: string
Cause: An error was returned while trying to rebuild or repair the container files
used to store data from protected databases.
Action: The subsequent error will identify the error that needs to be addressed
before the Recovery Appliance can be repaired.
ORA-60001 to ORA-65535 32-19
ORA-64703: resource error detected
Cause: A task needed to be interrupted because it detected a resource limitation
such as insufficient temporary table space or a snapshot being too old. It will be
retried once the contention for the resource decreases. The secondary messages
will identify the resource that has been exhausted.
Action: If this error occurs rarely, no user action is required. If the condition
becomes persistent, the Recovery Appliance administrator should increase the
resource that is exhausted.
ORA-64705: no destination in "string" at column string
Cause: The storage destination contained a syntax error.
Action: Correct the syntax error and retry the operation.
ORA-64708: more than one polling_location in "string" at column string
Cause: More than one polling_location was specified. Only one polling_location is
allowed.
Action: Specify only one polling destination directory and retry the operation.
ORA-64709: ASM polling_location is not supported in "string" at column string
Cause: The polling_location specified an ASM-based location. Only
non-ASM-based polling_locations are supported.
Action: Specify one non-ASM polling destination and retry the operation.
ORA-64711: storage destination do not reference an ASM diskgroup
Cause: The storage destination referenced a non-ASM storage location. Only
ASM-based storage destinations are allowed. The operation has been rolled back.
Action: Correct the syntax error and retry the operation.
ORA-64713: requested size string for string was too small; already using string
Cause: The size requested for the storage destination was smaller than its current
size.
Action: Increase the requested size and retry the operation.
ORA-64714: requested size string for string was larger than total available space
string
Cause: The size requested for the storage destination was larger than its current
used space plus its currect free space.
Action: Decrease the requested size and retry the operation.
ORA-64715: redundancy type "string" for diskgroup string is invalid
Cause: The redundancy type for the specified diskgroup was not one of
{NORMAL | HIGH | EXTERN}.
Action: Correct the redundancy type of the diskgroup and retry the operation.
ORA-64716: storage location string allocation size string does not equal diskgroup
string allocation size string
Cause: The minimum allocation size of the specified storage location was not the
same as the specified diskgroup allocation unit size.
Action: Specify a different diskgroup or a different storage location and retry the
operation.
32-20 Oracle Database Error Messages
ORA-64717: network chunk size string is not a multiple of diskgroup string
allocation size string
Cause: The configured network chunk size was not a multiple of the specified
diskgroup allocation unit size.
Action: Specify a different diskgroup or reconfigure the network chunk size and
retry the operation.
ORA-64718: diskgroup string allocation size string is not a power of two
Cause: The diskgroup allocation unit size was not a power of two.
Action: Specify a different diskgroup and retry the operation.
ORA-64719: diskgroup string allocation size string is less than two megabytes string
Cause: The diskgroup allocation unit size was less than two megabytes.
Action: Specify a different diskgroup and retry the operation.
ORA-64720: no containers were created for storage location string
Cause: No storage was allocated and initialized for the specified storage location.
Action: Specify a different diskgroup for the storage location, increase the size of
the diskgroup, or reduce the size of the storage location and retry the operation.
ORA-64721: reserved space string is less than the minimum reservation string
Cause: No storage was allocated and initialized for the specified storage location.
Action: Specify a different diskgroup for the storage location, increase the size of
the diskgroup, or reduce the size of the storage location and retry the operation.
ORA-64722: number of drives must be greater than zero
Cause: The specified number of tape drives was NULL or was less than or equal
to zero.
Action: Specify a number of tape drives greater than 0 and retry the operation.
ORA-64723: number of drives reserved for restore operations must be greater than
or equal to zero
Cause: The number of tape drives reserved for restore operations was NULL or
was less than zero.
Action: Specify a number of tape drives reserved for restore operations greater
than or equal to zero and retry the operation.
ORA-64724: number of restore drives string too large; must be less than string
Cause: The number of tape drives reserved for restore operations was at least as
large as the total number of drives available. The number of tape drives reserved
for restore operations must be at least one less than the total number of drives
available.
Action: Specify a number of tape drives reserved for restore operations less than
the total number of drives available and retry the operation.
ORA-64725: number of streams must be greater than zero
Cause: The number of streams was less than or equal to zero.
Action: Specify a number of streams greater than zero and retry the operation.
ORA-64726: number of streams string too large; must be no larger than string
ORA-60001 to ORA-65535 32-21
Cause: The number of streams was larger than the total number of drives
available. The number of streams must be no larger than the total number of
drives available.
Action: Reduce the number of available streams and retry the operation.
ORA-64727: number of copies string not in the range 1 through 4
Cause: The number of copies was either NULL or not in the range 1 through 4
inclusive.
Action: Specify a number of copies in the range 1 through 4 and retry the
operation.
ORA-64728: replication server name length string is too long
Cause: The replication server name was longer than 128 characters.
Action: Specify a replication server name shorter than 128 characters and retry the
operation.
ORA-64729: replication server proxy port string must be greater than zero
Cause: The replication server proxy port number was less than or equal to zero.
Action: Specify a replication server proxy port number greater than zero and retry
the operation.
ORA-64730: replication server proxy URL provided but proxy port is NULL
Cause: A replication server proxy URL was provided but a proxy port number
was not. If either a proxy URL or a proxy port are specified, both must be
specified.
Action: Specify both a replication server URL and a replication server proxy port
number and retry the operation.
ORA-64731: replication server proxy port provided but proxy URL is NULL
Cause: A replication server proxy port number was provided but a proxy URL
was not. If either a proxy URL or a proxy port are specified, both must be
specified.
Action: Specify both a replication server URL and a replication server proxy port
number and retry the operation.
ORA-64732: HTTP server not configured at replication host
Cause: The HTTP server at the replication host site has not been configured.
Action: Configure the HTTP server at the replication host site and retry the
operation.
ORA-64733: unable to move individual backup piece with BP_KEY string; not a
KEEP backup
Cause: An attempt was made to move an individual backup piece, but the backup
set of which this backup piece was a member was not a KEEP backup.
Action: Specify a backup piece key that is a member of a KEEP backup set and
retry the operation.
ORA-64735: unknown incarnation detected at Recovery Appliance, need catalog
resync
Cause: A new archived log or backup set belonging to the new incarnation was
received at Recovery Appliance.
32-22 Oracle Database Error Messages
Action: Using RMAN, connect to the Recovery Appliance as a recovery catalog,
primary database as target database and perform the resynchronization operation
using the RESYNC CATALOG RMAN command. If this error occurred at
downstream of the Recovery Appliance (in a replicated Recovery Appliance
setup), the reconcile operation fixes this error automatically when the same error is
fixed at the upstream Recovery Appliance.
ORA-64736: Task ID string of type string has been interrupted string times.
Cause: The specified task was restarted an unexpected number of times. Tasks get
interrupted when there is competition for resources. This is only a warning. It does
not necessarily indicate a problem with the Recovery Appliance.
Action: If these problems persist for long periods, contact Oracle Support
Services.
ORA-64737: unable to copy a full backup for database string because of missing
data files
Cause: While creating a full database backup to tape or to a Recovery Appliance,
level 0 backups of one or more data files were missing.
Action: Query the RA_SBT_TEMPLATE_MDF view to determine the data files for
which backups are missing. If using the "incremental forever" backup strategy,
perform a level-0 incremental backup for the given database and retry the
operation.
ORA-64738: guaranteed copy suspended for database string
Cause: One of the following operations was performed resulting in the database
using more than its allotted disk space:
- UPDATE_DB lowering the DISK_SPACE_RESERVE value.
- UPDATE_PROTECTION_POLICY setting the guaranteed_copy parameter to
YES
- DELETE_SBT_LIBRARY where backup data for the given database existed. New
backup requests may be stalled until the system can recompute the safety of
allowing additional backup data or backup data may be lost.
Action: This event can be avoided by ensuring backups are written to tape in a
timely manner. Conversely, one should avoid the activities listed in the Cause
statement when backups are not being written to tape in a timely manner.
ORA-64739: RECOVERY_WINDOW_GOAL is lost for database string
Cause: The recovery window goal in the protection policy indicates a desire to be
able to restore and recover to any point in time within that range. This is not
possible given the current set of backups. Possible reasons are missing archive log
backups, missing data file backups or lack of reserved disk space.
Action: Ensure that backups are done regularly. Ensure that your disk reserved
space value is set high enough to support your goals. Query RA_DATABASE view
for DISK_RESERVED_SPACE and RECOVERY_WINDOW_SPACE parameters
and compare these two parameters to ensure enough space has been provisioned
to meet your goals. However, you may use the DBMS_RA.UPDATE_
PROTECTION_POLICY procedure to increase the DISK_RESERVED_SPACE
value to ensure additional backups are saved. Also, check for KEEP backups
consuming space on the disk and decide if they should be moved to tape or other
disk storage.
ORA-64740: Backups from database string have not been seen for more than
UNPROTECTED_WINDOW period
ORA-60001 to ORA-65535 32-23
Cause: An UNPROTECTED_WINDOW parameter in protection policy has been
specified and the Recovery Appliance has not received sufficient archive log
backups or data file backups from the given target database for at least that period.
Action: Ensure that backups are being performed in a timely manner and that, if
set up, redo logs or backups are being sent to the Recovery Appliance.
ORA-64741: Scheduler string running task string of type string did not stop after
string requests.
Cause: The specified Recovery Appliance scheduler process could not be stopped.
Action: If these problems persist for long periods, contact Oracle Support
Services.
ORA-64744: Argument string is null, invalid, or out of range.
Cause: The argument was expecting a non-null, valid value but the argument
value passed in was null, invalid, or out of range.
Action: Check your program and correct the caller of the routine to not pass a
null, invalid or out-of-range argument value.
ORA-64745: Name length is string characters; maximum length is string characters.
Cause: The length of the name exceeded the limit.
Action: Specify a shorter name and retry the operation.
ORA-64746: Name contains invalid characters.
Cause: The name incorrectly started with "_", "-", ":" or digits or contained
non-alphanumeric characters. Verify that all other double quotation marks, if any,
in the string are adjacent pairs of double quotation marks. Double quotation marks
must not be used in the middle of the name.
Action: Change the name and exclude the invalid characters.
ORA-64747: Name contains invalid character "string" at the position [string].
Cause: The name incorrectly started with "_", "-", ":" or digits or contained
non-alphanumeric characters. Verify that all other double quotation marks, if any,
in the string are adjacent pairs of double quotation marks. Double quotation marks
must not be used in the middle of the name.
Action: Change the name and exclude the invalid characters.
ORA-64750: Instance string is unable to access string.
Cause: The Recovery Appliance was unable to find a file that is required for its
operation.
Action: Ensure that the file system of the specified file is available on the specified
instance.
ORA-64751: Replication setup error during string. replication server:string
database:string.
Cause: The Recovery Appliance was unable to complete the configuration and
setup of replication for the database specified.
Action: Validate that the downstream replication server is properly configured
and all network communication paths are valid.
ORA-64752: storage unavailable for new redo or backups for database string
Cause: There was a failure while backing up redo or copying backups from a
polling location. This condition may be due to one of the following reasons:
32-24 Oracle Database Error Messages
* An individual backup piece exceeded the database protection policy DISK_
RESERVE_SPACE value. * Guaranteed_copy is enabled but not enough data has
been spooled to tape. * Misconfiguration of the storage location size.
Action: Check for the value of DISK_RESERVED_SPACE and storage location
uses.
ORA-64753: Incorrect object type specified; specified string, expected string
Cause: An incorrect object type was given to an API command.
Action: Use the object-specific API. For example, use 'resume_replication_server'
instead of 'resume_sbt_library'.
ORA-64754: unable to perform operation with associated tape or replication objects
Cause: An attempt to execute 'update_db' or 'update_protection_policy' and
change storage locations with a replication server or tape job associated with the
protection policy failed.
Action: Create a temporary protection policy that has the same storage location as
the current protection policy with the tape and replication attributes of the target
protection policy, Update to the temporary protection policy then finally update to
the target protection policy.
ORA-64755: failed to delete database string; the Recovery Appliance is not running
Cause: An attempt was made to delete a database, but the Recovery Appliance
has been deactivated by the administrator.
Action: Have the Recovery Appliance administrator execute DBMS_
RA.STARTUP_RECOVERY_APPLIANCE and retry the delete_db() operation.
ORA-64756: failed to delete database string; error completing delete job
Cause: The database could not be deleted because the background delete job
failed unexpectedly.
Action: Contact Oracle Support Services for additional information.
ORA-64757: unable to restore backup piece with BP_KEY string
Cause: An attempt was made to restore the specified backup piece which resulted
in an error. An explanation of the error appears in the following messages.
Action: Verify the correctness of the backup piece. If it is corrupt, either delete it
or replace it.
ORA-65000: missing or invalid pluggable database name
Cause: A valid pluggable database name was not present where required.
Action: Reissue the statement with a valid pluggable database name.
ORA-65001: missing or invalid administrative user name
Cause: A valid administrative user name was not present where required by the
syntax of CREATE PLUGGABLE DATABASE statement.
Action: Reissue the CREATE PLUGGABLE DATABASE statement with a valid
administrative user name.
ORA-65002: missing or invalid administrative user password
Cause: A valid administrative user password was not present where required by
the syntax of CREATE PLUGGABLE DATABASE statement.
Action: Reissue the CREATE PLUGGABLE DATABASE statement with a valid
administrative user password.
ORA-60001 to ORA-65535 32-25
ORA-65003: missing or invalid XML file name
Cause: A valid XML file name was not present where required by the syntax of
CREATE PLUGGABLE DATABASE statement.
Action: Reissue the CREATE PLUGGABLE DATABASE statement with a valid
XML file name.
ORA-65004: missing or invalid database link name
Cause: A valid database link name was not present where required by the syntax
of CREATE PLUGGABLE DATABASE statement.
Action: Reissue the CREATE PLUGGABLE DATABASE statement with a valid
database link name.
ORA-65005: missing or invalid file name pattern for file - string
Cause: Either source or replacement file name pattern was missing or invalid in a
SOURCE_FILE_NAME_CONVERT or FILE_NAME_CONVERT clause.
Action: Correct the SOURCE_FILE_NAME_CONVERT or FILE_NAME_
CONVERT clause and reissue the statement.
ORA-65006: missing or invalid ENABLE PLUGGABLE DATABASE clause
Cause: An ENABLE PLUGGABLE DATABASE clause was not present where
required by the syntax of CREATE DATABASE statement.
Action: Reissue the CREATE DATABASE statement with a valid ENABLE
PLUGGABLE DATABASE clause.
ORA-65007: duplicate ENABLE PLUGGABLE DATABASE clause
Cause: A duplicate ENABLE PLUGGABLE DATABASE clause was specified in a
CREATE DATABASE statement.
Action: Reissue the CREATE DATABASE statement with a valid ENABLE
PLUGGABLE DATABASE clause.
ORA-65008: missing or invalid SEED clause
Cause: A SEED clause was not present where required by the syntax of CREATE
DATABASE statement.
Action: Reissue the CREATE DATABASE statement with a valid SEED clause.
ORA-65010: maximum number of pluggable databases created
Cause: User attempted to create more than supported number of pluggable
databases.
Action: Avoid creating too many pluggable databases.
ORA-65011: Pluggable database string does not exist.
Cause: User attempted to specify a pluggable database that does not exist.
Action: Check DBA_PDBS to see if it exists.
ORA-65012: Pluggable database string already exists.
Cause: User attempted to create a pluggable database with a name that already
exists.
Action: Check DBA_PDBS to see if the name exists.
ORA-65013: invalid CONTAINER clause
Cause: An invalid CONTAINER clause was encountered.
Action: Reissue the DDL statement with a valid CONTAINER clause.
32-26 Oracle Database Error Messages
ORA-65014: invalid SHARING clause
Cause: An invalid SHARING clause was encountered.
Action: Reissue the DDL statement with a valid SHARING clause.
ORA-65015: missing or invalid container name
Cause: A valid container name was not present where required by the syntax of
ALTER SESSION SET CONTAINER or ALTER USER ... SET|ADD|REMOVE
CONTAINER_DATA statement.
Action: Reissue the statement with a valid container name.
ORA-65016: FILE_NAME_CONVERT must be specified
Cause: Data files, and possibly other files, needed to be copied as a part of
creating a pluggable database. However, Oracle Managed Files (OMF) was not
enabled, PDB_FILE_NAME_CONVERT was not defined, and there was a failure
to specify the FILE_NAME_CONVERT clause.
Action: Enable OMF or define PDB_FILE_NAME_CONVERT system parameter
before issuing CREATE PLUGGABLE DATABASE statement, or specify FILE_
NAME_CONVERT clause as a part of the statement.
ORA-65017: seed pluggable database may not be dropped or altered
Cause: User attempted to drop or alter the Seed pluggable database which is not
allowed.
Action: Specify a legal pluggable database name.
ORA-65018: FILE_NAME_CONVERT or NOCOPY must be specified
Cause: Oracle Managed Files (OMF) was not enabled and PDB_FILE_NAME_
CONVERT was not defined. The FILE_NAME_CONVERT or the NOCOPY clause
was not specified as a part of creating a pluggable database using data files.
Action: Enable OMF or define PDB_FILE_NAME_CONVERT system parameter
before issuing CREATE PLUGGABLE DATABASE statement, or specify FILE_
NAME_CONVERT clause or NOCOPY as a part of the statement.
ORA-65019: pluggable database string already open
Cause: An attempt was made to open a pluggable database that was already
opened.
Action: Check the OPEN_MODE column in V$PDBS view.
ORA-65020: pluggable database string already closed
Cause: An attempt was made to close a pluggable database that was already
closed.
Action: Check the OPEN_MODE column in V$PDBS view.
ORA-65021: illegal use of SHARING clause
Cause: A SHARING clause was encountered in unexpected context.
Action: Do not use SHARING clause outside of Oracle-supplied scripts.
ORA-65022: CONTAINER clause already specified
Cause: A statement contained multiple CONTAINER clauses.
Action: Eliminate redundant CONTAINER clauses.
ORA-65023: active transaction exists in container string
ORA-60001 to ORA-65535 32-27
Cause: A statement attempted to create a new transaction in the current container
while there was an active transaction in another container.
Action: Switch to the container with the active transaction and commit, rollback
or detach the active transaction before attempting to issue any statement that will
attempt to create a new transaction in another container.
ORA-65024: Pluggable database string is not open.
Cause: An operation was attempted on a pluggable database that was not open.
Action: Open the pluggable database using appropriate open mode.
ORA-65025: Pluggable database string is not closed on all instances.
Cause: An operation was attempted on a pluggable database that was not closed
on all Oracle RAC instances.
Action: Close the pluggable database on all instances and retry the operation.
ORA-65026: XML metadata file error : string
Cause: An error occurred while trying to parse or write to the XML metadata file.
Action: Check that the XML metadata file exists and is readable.
ORA-65027: XML metadata file error while getting node or value for (string - string)
Cause: An error occurred while trying to parse the XML metadata file.
Action: Check and correct the XML metadata file.
ORA-65028: Unable to open plugin data file at path string
Cause: Error occurred while trying to open the datafile.
Action: Check that the datafile exists at the path.
ORA-65029: a Local User may not grant or revoke a Common Privilege or Role
Cause: A Local User issued a GRANT or REVOKE statement specifying
CONTAINER=ALL, which is illegal.
Action: Remove CONTAINER=ALL from the statement.
ORA-65030: one may not grant a Common Privilege to a Local User or Role
Cause: A Common User issued a GRANT statement specifying
CONTAINER=ALL and naming a Local User or Role as a grantee, which is illegal.
Action: If trying to grant a Local Privilege, remove CONTAINER=ALL from the
statement. If trying to grant a Common Privilege, remove Local Users and Roles
from the list of grantees.
ORA-65031: one may not revoke a Common Privilege from a Local User or Role
Cause: A Common User issued a REVOKE statement specifying
CONTAINER=ALL and naming a Local User or Role as a grantee, which is illegal.
Action: If trying to revoke a Local Privilege, remove CONTAINER=ALL from the
statement. If trying to revoke a Common Privilege, remove Local Users and Roles
from the list of grantees.
ORA-65032: a Local Role may only be granted or revoked within the current
Container
Cause: A user issued a GRANT or REVOKE statement specifying
CONTAINER=ALL and listing a Local Role among roles to be granted or revoked,
which is illegal.
32-28 Oracle Database Error Messages
Action: If trying to revoke a Local Role, remove CONTAINER=ALL from the
statement. If trying to revoke Common Privileges and/or Roles, remove Local
Roles from the list of roles being granted or revoked.
ORA-65033: a common privilege may not be granted or revoked on a local object
Cause: A GRANT or REVOKE statement was issued specifying
CONTAINER=ALL and naming a local object on which privileges are to be
granted or revoked, which is illegal.
Action: Remove CONTAINER=ALL from the statement.
ORA-65034: PDB describe output file not specified
Cause: User attempted to describe a pluggable database without specifying an
output XML file location.
Action: Specify an output file location for describe
ORA-65035: unable to create pluggable database from string
Cause: The pluggable database had ongoing or active transactions that need to be
recovered.
Action: Open the pluggable database in read/write mode before cloning again so
that transaction recovery can be performed.
ORA-65036: pluggable database string not open in required mode
Cause: Attempted to perform an operation on a pluggable database in incorrect
open mode.
Action: Open the pluggable database in the mode required for this operation
ORA-65037: a common privilege may not be granted or revoked on a local user
Cause: A GRANT or REVOKE statement was issued specifying
CONTAINER=ALL and naming a local user on which privileges are to be granted
or revoked, which is illegal.
Action: Remove CONTAINER=ALL from the statement.
ORA-65039: container identifier column missing or is of unexpected type in a
definition of a CONTAINER_DATA object
Cause: Table or view whose definition contained a CONTAINER_DATA clause
lacked a column used to identify a container to which data belongs or the column
was of unexpected type.
Action: Correct the statement and reenter.
ORA-65040: operation not allowed from within a pluggable database
Cause: An operation was attempted that can only be performed in the root
container.
Action: Switch to the root container to perform the operation.
ORA-65041: CONTAINER_DATA attribute for this user cannot be modified
Cause: An attempt was made to modify CONTAINER_DATA attribute for user
SYS or SYSBACKUP which is disallowed.
Action: Do not attempt to modify CONTAINER_DATA attribute for users SYS or
SYSBACKUP.
ORA-65042: name is already used by an existing container
Cause: The name was already used by another container.
ORA-60001 to ORA-65535 32-29
Action: Specify a valid name.
ORA-65043: TABLESPACE keyword expected
Cause: TABLESPACE keyword was missing.
Action: Specify a TABLESPACE keyword.
ORA-65044: missing or invalid option following STORAGE keyword
Cause: An option other than MAXSIZE or MAX_SHARED_TEMP_SIZE was
specified.
Action: Specify only legal options.
ORA-65045: pluggable database not in a restricted mode
Cause: An operation was attempted on a pluggable database that was not in
restricted mode.
Action: Open the pluggable database in a restricted mode.
ORA-65046: operation not allowed from outside a pluggable database
Cause: An operation was attempted that can only be performed from within a
pluggable database.
Action: Switch to a pluggable database to perform the operation.
ORA-65047: object string.string is invalid or compiled with errors in CDB$ROOT
Cause: An attempt was made to issue a metadata link ddl for an object that was
invalid or compiled with errors in CDB$ROOT.
Action: Check the validity of the object in CDB$ROOT.
ORA-65048: error encountered when processing the current DDL statement in
pluggable database string
Cause: An error was encountered when executing a statement in one of the
pluggable databases.
Action: Examine the cause of failure in the pluggable database.
ORA-65049: creation of local user or role is not allowed in CDB$ROOT
Cause: An attempt was made to create a local user or role in CDB$ROOT.
Action: If trying to create a common user or role, specify CONTAINER=ALL.
ORA-65050: Common DDLs only allowed in CDB$ROOT
Cause: An attempt was made to issue a Common DDL in a pluggable database.
Action: Switch to CDB$ROOT and issue the Common DDL there.
ORA-65051: missing valid container identifier
Cause: A valid container identifer was not specified.
Action: Specify a valid container identifier.
ORA-65052: statement involves operations with different container scope
Cause: An attempt was made to combine one operation that applies to all
containers with another that only applies to the local container into one statement.
Action: Execute the operations in separate statements.
ORA-65053: A global user cannot change the container in the session.
Cause: An attempt was made by a global user to change the container using the
ALTER SESSION SET CONTAINER statement.
32-30 Oracle Database Error Messages
Action: This operation is not allowed for global users.
ORA-65054: Cannot open a pluggable database in the desired mode.
Cause: An attempt was made to open a pluggable database in a mode
incompatible with that of the CDB.
Action: Open the CDB in a compatible mode first and retry the operation.
ORA-65056: CONTAINER_DATA attribute is not used in a pluggable database.
Cause: User connected to a pluggable database attempted to modify a
CONTAINER_DATA attribute which is illegal.
Action: User connected to a pluggable database may only see rows of
CONTAINER_DATA objects on which he has been granted appropriate privilege
and which pertain to that pluggable database or to the CDB as a whole. Ability to
see this data is not controlled by CONTAINER_DATA attribute, which is only
used to control ability to see rows pertaining to certain Containers while
connected to CDB$ROOT in a CDB.
ORA-65057: CONTAINER_DATA attribute must always include the current
container
Cause: User issuing ALTER USER ... SET|REMOVE CONTAINER_DATA = ...
statement attempted to exclude the current container from a CONTAINER_DATA
attribute.
Action: Ensure that a CONTAINER_DATA attribute always includes the current
container.
ORA-65058: object-specific CONTAINER_DATA attribute may only be specified
for a CONTAINER_DATA object
Cause: Object referenced in an ALTER USER statement modifying an
object-specific CONTAINER_DATA attribute is not a CONTAINER_DATA table or
view.
Action: Ensure that an object referenced in the statement is a CONTAINER_DATA
table or view.
ORA-65059: duplicate container name in CONTAINER_DATA clause
Cause: Duplicate references to a name of some container was encountered in a
CONTAINER_DATA clause.
Action: Ensure that no container name appears more than once.
ORA-65060: CONTAINER_DATA attribute is not set
Cause: User attempted to add container(s) to an object-specific CONTAINER_
DATA attribute which has not been explicitly set or has been set to DEFAULT or
remove containers from a CONTAINER_DATA attribute which has not been
explicitly set or has been set to DEFAULT.
Action: Avoid adding containers to object-specific CONTAINER_DATA attribute
which has not been explicitly set or has been set to DEFAULT or removing
containers from a CONTAINER_DATA attribute which has not been explicitly set
or has been set to DEFAULT.
ORA-65061: some of specified containers do not belong to the CONTAINER_DATA
attribute
Cause: User attempted to remove from a CONTAINER_DATA attribute
container(s) which do not belong to it.
ORA-60001 to ORA-65535 32-31
Action: Do not attempt to remove from a CONTAINER_DATA attribute
container(s) which do not belong to it.
ORA-65062: CONTAINER_DATA attribute is set to ALL
Cause: User attempted to add/remove container(s) to/from a CONTAINER_
DATA attribute whose current value is ALL, which is not supported.
Action: Do not attempt to add/remove container(s) to/from a CONTAINER_
DATA attribute whose current value is ALL.
ORA-65063: CONTAINER_DATA clause has already been specified
Cause: The CONTAINER_DATA clause was specified twice.
Action: Specify only one CONTAINER_DATA clause.
ORA-65064: incorrect contents of XML metadata file
Cause: The contents of the XML metadata file were different from the actual file
properties.
Action: Check and correct the XML metadata file.
ORA-65065: A local user or role can only be altered within the current container
Cause: The ALTER USER or ALTER ROLE statement was issued specifying
CONTAINER=ALL and listing a local user or role among the users or roles to be
altered, which is illegal.
Action: If trying to alter a local user or role, specify CONTAINER=CURRENT. If
trying to alter common users or roles, remove local users or roles from the list of
roles being altered.
ORA-65066: The specified changes must apply to all containers
Cause: An attempt was made to apply the specified changes to the current
container.
Action: Specify CONTAINER=ALL.
ORA-65067: DEFAULT ROLE clause referencing a local role can only apply to the
current container
Cause: An attempt was made to reference a local role across all containers using
the DEFAULT ROLE clause.
Action: If you are trying to set a local role as the default role, specify
CONTAINER=CURRENT. If trying to set common roles as the default roles,
remove local roles from the list of roles referenced in the DEFAULT ROLE clause.
ORA-65068: cannot define a trigger that fires after a pluggable database is
unplugged
Cause: An attempt was made to create a trigger that fires after a pluggable
database has been unplugged. This type of trigger is not supported.
Action: Do not attempt to create a trigger that fires after a pluggable database has
been unplugged.
ORA-65069: AFTER DB_ROLE_CHANGE triggers cannot be defined on a
pluggable database
Cause: An attempt was made to create a pluggable database trigger that fires after
a role change occurs from a standby database to primary or vice versa. This type of
trigger is not supported.
Action: Do not specify AFTER DB_ROLE_CHANGE when creating a trigger on a
pluggable database.
32-32 Oracle Database Error Messages
ORA-65070: AFTER CLONE trigger can only be created on a pluggable database
Cause: An attempt was made to create an AFTER CLONE trigger on a schema or
a database. This type of trigger is not supported.
Action: Do not specify AFTER CLONE when creating a trigger on a schema or a
database.
ORA-65071: BEFORE UNPLUG trigger can only be created on a pluggable database
Cause: An attempt was made to create a BEFORE UNPLUG trigger on a schema
or a database. This type of triggers is not supported.
Action: Do not specify BEFORE UNPLUG when creating a trigger on a schema or
a database.
ORA-65072: user must be connected to a pluggable database on which a trigger is
being created
Cause: An attempt was made to create a database event trigger on a pluggable
database while not connected to a pluggable database. This is not supported.
Action: Connect to the pluggable database on which a database event trigger
needs to be created before attempting to create such a trigger.
ORA-65073: cannot define a trigger that fires before a pluggable database is cloned
Cause: An attempt was made to create a trigger that fires before a pluggable
database has been cloned. This type of trigger is not supported.
Action: Do not attempt to create a trigger that fires before a pluggable database
has been cloned.
ORA-65074: editions not supported for common users
Cause: An attempt was made to support editions for common users.
Action: Do not attempt to enable editions for common users.
ORA-65080: cannot determine pluggable database name
Cause: An attempt was made to map the database ID to the pluggable database
name.
Action: Contact Oracle Support Services.
ORA-65081: database or pluggable database is not open in read only mode
Cause: An operation was attempted on a database or pluggable database that is
not open in read only mode
Action: Open the database or pluggable database in read only mode and then
retry the operation.
ORA-65082: cannot add any more pluggable databases: limit of string exceeded
Cause: There was no more room in the control file for adding pluggable
databases.
Action: Recreate the control file.
ORA-65083: pluggable database (PDB) shutdown in progress
Cause: The pluggable database is in the middle of shutdown abort
Action: Retry the operation later.
ORA-65084: object string.string does not exist in root
Cause: An attempt was made to create a common object that does not exist in
root.
ORA-60001 to ORA-65535 32-33
Action: Invoke the script using catcon.pl to create the object in all containers.
ORA-65085: cannot open pluggable database in read-only mode
Cause: The pluggable database has been created and not opened.
Action: The pluggable database needs to be opened in read/write or restricted
mode first.
ORA-65086: cannot open/close the pluggable database
Cause: The pluggable database has been unplugged.
Action: The pluggable database can only be dropped.
ORA-65087: Oracle-supplied operation not allowed from within a pluggable
database
Cause: An operation in an Oracle-supplied script was attempted that can only be
performed in the root container.
Action: Confirm that the operation is needed in the root container, and switch to
the root container to perform the operation.
ORA-65088: database open should be retried
Cause: An inconsistency between the control file and the data dictionary was
found and fixed during the database open. The database open needs to be
executed again.
Action: Retry the database open.
ORA-65089: pluggable database is not clean
Cause: The pluggable database was not open anywhere but was not marked as
clean yet.
Action: Wait until the cleanup is done and retry.
ORA-65090: operation only allowed in a container database
Cause: User attempted an operation that is only allowed in a CDB
Action: Connect to a CDB to perform this operation
ORA-65091: operation on string not allowed in a pluggable database
Cause: An undo tablespace or rollback segment operation was attempted that can
only be performed in the root container.
Action: Switch to the root container to perform the undo tablespace or rollback
segment operation.
ORA-65092: system privilege granted with a different scope to 'string'
Cause: An attempt to revoke a system privilege that was granted with a different
scope has been made. The user tried to either revoke a common privilege in the
current container or to revoke a local privilege in a container database (CDB).
Action: Specify the correct value for the CONTAINER clause.
ORA-65093: multitenant container database not set up properly
Cause: An attempt was made to open a multitenant container database without
the correct parameter set for a multitenant container database in the initialization
parameter file.
Action: Set the 'enable_pluggable_database=true' parameter for the multitenant
container database in the initialization parameter file and restart the database.
32-34 Oracle Database Error Messages
ORA-65094: invalid local user or role name
Cause: An attempt was made to create a local user or role with a name that was
not valid for local users or roles. In addition to the usual rules for user and role
names, local user and role names cannot start with C## or c##.
Action: Specify a valid local user or role name.
ORA-65095: invalid common object name
Cause: An attempt was made to create a common object with a name that was not
valid for common objects. In addition to the usual rules for object names, common
object names must consist only of ASCII characters.
Action: Specify a valid common object name.
ORA-65096: invalid common user or role name
Cause: An attempt was made to create a common user or role with a name that
was not valid for common users or roles. In addition to the usual rules for user
and role names, common user and role names must start with C## or c## and
consist only of ASCII characters.
Action: Specify a valid common user or role name.
ORA-65097: Invalid argument supplied to CDB$VIEW function
Cause: CDB$VIEW may be applied to a valid table name of the form
<owner>.<tablename>
Action: Correct the statement
ORA-65098: Datatype not supported with CDB$VIEW function
Cause: Column with unsupported datatype was selected from a CDB View.
Action: Remove the column from the select list
ORA-65099: Operation cannot be performed when the CDB is not open
Cause: An operation was attemped inside a pluggable database that requires the
container database (CDB) to be open. *Aciton: Open the CDB and then reissue the
operation.
Action: None
ORA-65100: missing or invalid path prefix - string
Cause: Path prefix was missing or invalid.
Action: Correct the PATH_PREFIX clause and reissue the statement.
ORA-65101: container database set up incorrectly
Cause: An attempt was made to use a non container database control file to
startup a container database (CDB).
Action: Create a new control file for the CDB.
ORA-65102: missing or invalid instance name
Cause: A valid instance name was not present where required by the syntax of a
ALTER PLUGGABLE DATABASE statement.
Action: Reissue the statement with a valid instance name.
ORA-65103: UPGRADE cannot be specified for PDBs being open in READ ONLY
mode
ORA-60001 to ORA-65535 32-35
Cause: ALTER PLUGGABLE DATABASE ... OPEN UPGRADE was specified, but
the root is open READ ONLY, so the specified PDBs will also be opened READ
ONLY, and UPGRADE cannot be specified for PDBs being opened READ ONLY.
Action: Reissue the statement without specifying UPGRADE or reopen the root in
READ WRITE mode and then reissue the statement.
ORA-65104: operation not allowed on an inactive pluggable database
Cause: The pluggable database status was INACTIVE. It was still being created or
there was an error during the create operation.
Action: Wait until the status is changed to CREATED or, in case of errors, drop the
pluggable database and re-create it.
ORA-65105: SYSTEM data file for pluggable database #string not found
Cause: Data files were not specified in a CREATE CONTROLFILE statement in
the SYSTEM tablespace of a pluggable database.
Action: Locate the data files and resubmit the CREATE CONTROLFILE
statement.
ORA-65106: Pluggable database #string (string) is in an invalid state.
Cause: Data files were not specified in a CREATE CONTROLFILE statement of a
pluggable database.
Action: Drop the pluggable database or locate the data files and resubmit the
CREATE CONTROLFILE statement.
ORA-65107: Error encountered when processing the current task on instance:string
Cause: An error was encountered when executing a pluggable database task on
one of the Oracle RAC instances.
Action: Examine the cause of failure on the instance.
ORA-65108: invalid use of a cursor belonging to another container
Cause: An attempt was made to use a cursor that was parsed or executed in a
different container.
Action: Check if there are any incorrect uses of the SET CONTAINER statement.
Parse, execute, fetch, and close a cursor only all in the same container.
ORA-65109: operation not allowed in CDB$ROOT
Cause: An operation was attempted that is not supported in the Container
Database root.
Action: Switch to a pluggable database to perform the operation.
ORA-65110: Invalid instance name specified
Cause: An attempt was made to use an invalid or inactive instance name in the
instance clause to alter the state of a pluggable database.
Action: Specify a valid and active instance name.
ORA-65111: Cannot relocate to the same instance
Cause: An attempt was made to relocate a pluggable database to the current
instance.
Action: Specify an instance which is different then the current instance.
ORA-65112: pluggable database string not closed on all instances of the standby
database
32-36 Oracle Database Error Messages
Cause: Media recovery stopped because the pluggable database was either
unplugged, dropped or renamed on the primary database.
Action: Close the pluggable database on all instances and restart the recovery.
ORA-65113: value of MAX_PDB_STORAGE property for the PDB is too low
Cause: The value of MAX_PDB_STORAGE specified in the ALTER or CREATE
PLUGGABLE DATABASE statement is less than the current space usage of data
files and temporary files of the container.
Action: Specify a higher value for MAX_PDB_STORAGE.
ORA-65114: space usage in container is too high
Cause: Space usage in the current container exceeded the value of MAX_PDB_
STORAGE for the container.
Action: Specify a higher value for MAX_PDB_STORAGE using the ALTER
PLUGGABLE DATABASE statement.
ORA-65115: CDB resource plan string has more than string PDB directives.
Cause: An attempt was made to create or update the specified multitenant
container database (CDB) resource plan to use more than the supported number of
directives.
Action: Remove the directives for pluggable databases (PDBs) that are not active
on this database.
ORA-65116: incompatible database character set
Cause: The database character set of the container database was not a superset of
the database character set of the pluggable database being plugged in.
Action: Plug the pluggable database into a container database having a
compatible database character set.
ORA-65117: CONTAINER clause may only be specified when connected to a
container database
Cause: The CONTAINER clause was specified when not connected to a container
database (CDB).
Action: Reenter the statement without the CONTAINER clause.
ORA-65118: operation affecting a pluggable database cannot be performed from
another pluggable database
Cause: An attempt was made to perform an operation affecting a pluggable
database while connected to a different pluggable database.
Action: Connect to the desired pluggable database and perform the operation.
ORA-65119: incompatible national character set
Cause: The national character set of the container database was not the same as
the national character set of the pluggable database being plugged in.
Action: Plug the pluggable database into a container database having the same
national character set.
ORA-65120: illegal character set ID in XML metadata file
Cause: The XML metadata file for the pluggable database being plugged in
contained a database or national character set ID that was not valid for the
container database. This can happen if the XML file is manually modified, if it is
corrupted on disk, or if the set of supported character sets differs between the
container database and the source database of the pluggable database because a
ORA-60001 to ORA-65535 32-37
user-defined character set has not been installed in the Oracle Home directory of
the container database.
Action: If you have manually modified the XML metadata file of the pluggable
database, restore the original file or re-create the pluggable database from its
source database. Manual modifications of the XML file are not supported. If the
pluggable database uses a user-defined character set, make sure the character set is
installed in the Oracle Home directory of the container database. Otherwise,
contact Oracle Support Services.
ORA-65121: ALTER SESSION SET CONTAINER not allowed from this client
Cause: Clients earlier than Oracle Database 12c Release 1 do not support this
feature.
Action: Upgrade the client to Oracle Database 12c Release 1 or later.
ORA-65122: Pluggable database GUID conflicts with the GUID of an existing
container.
Cause: While creating a pluggable database, the GUID conflicted with the GUID
of an existing container in the container database.
Action: Retry creating the pluggable database or consider using the AS CLONE
clause for CREATE PLUGGABLE DATABASE if plugging in a copy of another
pluggable database.
ORA-65123: cannot perform a SET CONTAINER operation in this context
Cause: An attempt was made to set the container inside a context where such an
operation is prohibited.
Action: Do not set the container from inside a system trigger or a DML context.
ORA-65125: valid XML file name is required
Cause: An attempt was made to provide a file name that did not have an XML
extension.
Action: Specify an XML file.
ORA-65126: pluggable database string cannot be unplugged.
Cause: The pluggable database was not closed cleanly and there are active
transactions that need to be recovered.
Action: Open the pluggable database in read/write mode before unplugging
again so that transaction recovery can be performed.
ORA-65127: PDB recover output file not specified
Cause: An attempt was made torecover a pluggable database (PDB) without
specifying an output XML file location.
Action: Specify an output file location for recovery.
ORA-65128: PDB recover data file name not specified
Cause: An attempt was made to recover a pluggable database (PDB) without
specifying a data file location.
Action: Specify a data file location for recovery.
ORA-65129: Pluggable database string cannot be relocated.
Cause: The pluggable database was already opened on all instances.
Action: Close the pluggable database without RELOCATE clause or close the
pluggable database on another instance.
32-38 Oracle Database Error Messages
ORA-65130: cannot relocate more than one pluggable database.
Cause: An attempt was made to relocate more than one pluggable database.
Action: RELOCATE pluggable database one at a time.
ORA-65131: The feature string is not supported in a pluggable database.
Cause: An attempt was made to use a feature that is not supported in a pluggable
database.
Action: Do not use this feature in a pluggable database.
ORA-65134: endian mismatch
Cause: The endian of the container database was not the same as the endian of the
pluggable database being plugged in.
Action: Plug the pluggable database into a container database having the same
endian.
ORA-65135: cannot perform ALTER SESSION SET CONTAINER operation in this
context
Cause: An ALTER SESSION SET CONTAINER operation was attempted in a
context where such an operation is prohibited.
Action: Do not perform the ALTER SESSION SET CONTAINER operation from a
session that can be migrated or a session from an OCI connection pool.
ORA-65136: SPFILE name cannot be specified for a pluggable database
Cause: An attempt was made to specify an SPFILE name for a pluggable
database.
Action: Remove the SPFILE name and retry the operation in the pluggable
database.
ORA-65137: Pluggable database string is in the middle of Pluggable Database
RESETLOGS operation.
Cause: The pluggable database is in the middle of a Pluggable Database (PDB)
RESETLOGS operation.
Action: If possible, recover the Container Database further so that this Pluggable
database is not in the middle of a PDB RESETLOGS operation. Another alternative
is to perform PDB point-in-time recovery. A message is logged in the alert log
indicating SCN and time until which the pluggable database can be point-in-time
recovered.
ORA-65138: Data file string of pluggable database string belongs to an orphan PDB
incarnation.
Cause: Either the specified data file was restored from a backup that was taken
during a period of time that was discarded by a RESETLOGS operation, or Oracle
could not identify which pluggable database incarnation the file belongs to. The
alert log contains more information.
Action: Restore a backup of this file that belonged to either the current or a prior
incarnation of the pluggable database. If you are using RMAN to restore, RMAN
will automatically select a correct backup.
ORA-65139: Mismatch between XML metadata file and data file string for value of
string (string)
Cause: Either the XML metadata file or the data file was corrupt.
ORA-60001 to ORA-65535 32-39
Action: Verify that the XML metadata file and the data file are consistent as of the
point when the unplug was done and retry the operation.
ORA-65140: invalid common profile name
Cause: An attempt was made to create a common profile with a name that is not
valid for common profiles. Common profile names must start with C## or c## and
consist only of ASCII characters.
Action: Specify a valid common profile name.
ORA-65141: invalid local profile name
Cause: An attempt was made to create a local profile with a name that is not valid
for local profiles. Local profile names cannot start with C## or c##.
Action: Specify a valid local profile name.
ORA-65142: A local profile can be altered only within the current container
Cause: An attempt was made to alter a local profile using an ALTER PROFILE
statement with the CONTAINER=ALL clause.
Action: If attempting to alter a local profile, ensure that you are connected to the
correct container and optionally specify CONTAINER=CURRENT.
ORA-65143: creation of local profiles is not allowed in CDB$ROOT
Cause: An attempt was made to create a local profile in CDB$ROOT.
Action: If attempting to create a common profile, do not specify
CONTAINER=CURRENT.
ORA-65144: ALTER SYSTEM DISABLE RESTRICTED SESSION is not permitted
Cause: An attempt was made to disable a restricted session while an unresolved
error existed in PDB_PLUG_IN_VIOLATIONS.
Action: Resolve all of the errors before trying to disable a restricted session.
ORA-65145: FORCE open of a pluggable database on more than one instance is not
supported
Cause: An attempt was made to FORCE open a pluggable database on more than
one instance.
Action: Retry the FORCE open of the pluggable database one instance at a time.
ORA-65146: account cannot be unlocked in a PDB while it is locked in the root
Cause: An attempt was made to unlock a common user account in a pluggable
database (PDB) which was locked in the root of the container database.
Action: Ensure that a common user account is not locked in the root before
attempting to unlock it in a PDB.
ORA-65147: DB_UNIQUE_NAME specified without SPFILE scope
Cause: An attempt was made to specify a DB_UNIQUE_NAME in an ALTER
SYSTEM statement without SCOPE=SPFILE.
Action: Use DB_UNIQUE_NAME only with SCOPE=SPFILE.
ORA-65148: cannot FORCE open a pluggable database to or from upgrade mode
Cause: An attempt was made to FORCE open a pluggable database to or from
upgrade mode.
Action: Close the pluggable database first and retry the operation.
32-40 Oracle Database Error Messages
ORA-65149: PDB name conflicts with existing service name in the CDB or the PDB
Cause: An attempt was made to create a pluggable database (PDB) whose name
conflicts with the existing service name in the container database (CDB) or the
PDB.
Action: Choose a different name for the PDB.
ORA-65150: unable to start the instance
Cause: An attempt was made to start an instance as a container or a non-container
database when atleast one of the other instances was started in a different mode.
Action: Start the instance in the same mode as all the other instances.
ORA-65151: invalid tablespace name specified
Cause: An attempt was made to use an invalid tablespace name or a mandatory
tablespace name (SYSTEM or SYSAUX) in the USER_TABLESPACES clause when
creating a pluggable database.
Action: Specify a valid tablespace name.
ORA-65152: cannot bring datafile online
Cause: An attempt was made to bring online one or more datafiles belonging to a
pluggable database that is disabled for recovery.
Action: Issue the ALTER PLUGGABLE DATABASE ENABLE RECOVERY
statement first and retry the operation.
ORA-65153: cannot bring tablespace online
Cause: An attempt was made to bring online a tablespace that was either missing
in the plug XML file or excluded when the pluggable database was created.
Action: Drop and recreate the tablespace to bring it online.
ORA-65154: specified logging attribute for the pluggable database is same as the
current attribute value
Cause: An attempt was made to change the default logging attribute to be the
same as the current attribute value for the pluggable database.
Action: Change the logging attribute to a different value.
ORA-65155: missing or invalid source file directory string
Cause: Source file directory was missing or invalid.
Action: Correct the SOURCE_FILE_DIRECTORY clause and reissue the
statement.
ORA-65156: pluggable database version string not allowed
Cause: An attempt was made to plug in a pluggable database with an
incompatible version of the multitenant container database.
Action: Plug in a pluggable database with a compatible version of the multitenant
container database.
ORA-65157: SOURCE_FILE_NAME_CONVERT and SOURCE_FILE_DIRECTORY
cannot be specified together
Cause: SOURCE_FILE_NAME_CONVERT and SOURCE_FILE_DIRECTORY
clauses were both specified.
Action: Use either the SOURCE_FILE_NAME_CONVERT or the SOURCE_FILE_
DIRECTORY clause and reissue the statement.
ORA-60001 to ORA-65535 32-41
ORA-65158: could not find a matching file for - string
Cause: A matching file was not found in the directory specified with the
SOURCE_FILE_DIRECTORY clause.
Action: Correct the SOURCE_FILE_DIRECTORY clause or check that the file
exists in the directory and reissue the statement.
ORA-65159: invalid service name specified
Cause: An attempt was made to use an invalid service name in the services
clause.
Action: Specify a valid service name.
ORA-65160: invalid cleanup task ID
Cause: An attempt was made to pass an invalid cleanup task ID to the DBMS_
PDB.CLEANUP_TASK function.
Action: Specify a valid cleanup task ID.
ORA-65161: Unable to create pluggable database with no data
Cause: An attempt was made to clone a pluggable database which contains some
clustered tables or index organized tables or advanced queue tables.
Action: Retry the clone operation after dropping all such objects from the source
pluggable database.
ORA-65162: The password has expired.
Cause: The user's account expired and the password needs to be changed by
connecting to the root of the multitenant container database
Action: Change the password or contact the DBA.
ORA-65164: database is in NOARCHIVELOG mode
Cause: The database was in NOARCHIVELOG mode when pluggable database
(PDB) shutdown abort was attempted.
Action: Set the database to ARCHIVELOG mode by issuing the ALTER
DATABASE ARCHIVELOG command.
ORA-65165: missing or invalid path for file creation string
Cause: The path specified in CREATE_FILE_DEST clause was missing or invalid.
Action: Correct the CREATE_FILE_DEST clause and reissue the statement.
ORA-65166: cannot run noncdb_to_pdb.sql if PDB's version differs from CDB's
Cause: An attempt was made to run noncdb_to_pdb.sql when the version of the
pluggable database (PDB) was different from the version of the multitenant
container database (CDB).
Action: Upgrade the PDB before running noncdb_to_pdb.sql
ORA-65167: cannot run noncdb_to_pdb.sql if container database is in upgrade
mode
Cause: An attempt was made to run noncdb_to_pdb.sql when the multitenant
container database (CDB) was in upgrade mode.
Action: Open the CDB in non-upgrade mode.
ORA-65168: missing PFILE name
Cause: An operation involving PFILE was issued in a pluggable database without
specifying the PFILE name
32-42 Oracle Database Error Messages
Action: Specify a valid PFILE name and retry the operation in the pluggable
database.
ORA-65169: error encountered while attempting to copy file string
Cause: An error was encountered while attempting to copy the file while creating
a pluggable database.
Action: Check additional error messages for the cause of the failure to copy the
file, and resolve the issue accordingly.
ORA-65170: XML file string already exists
Cause: An attempt to create an XML file failed because a file with that name
already exists.
Action: Use a different XML file name.
ORA-65171: invalid value for DB_BLOCK_CHECKING parameter
Cause: An attempt was made to specify a value of FALSE or OFF for the DB_
BLOCK_CHECKING parameter in a pluggable database (PDB), when the value of
DB_BLOCK_CHECKING parameter in the multitenant container database (CDB)
is neither FALSE nor OFF. If the CDB has enabled the DB_BLOCK_CHECKING
parameter, then the PDB cannot disable the DB_BLOCK_CHECKING parameter.
Action: Specify a value other than FALSE or OFF for the DB_BLOCK_
CHECKING parameter in the PDB.
ORA-65172: cannot run noncdb_to_pdb.sql unless pluggable database is an
unconverted non-container database
Cause: An attempt was made to run 'noncdb_to_pdb.sql' on a pluggable database
(PDB) that was not an unconverted non-container database.
Action: 'noncdb_to_pdb.sql' is not necessary for this PDB.
ORA-65173: privilege granted with a different scope to 'string'
Cause: An attempt to revoke a privilege that was granted with a different scope
has failed. The user tried to either revoke a common privilege in the current
container or to revoke a local privilege in a multitenant container database (CDB).
Action: Specify the correct value for the CONTAINER clause.
ORA-65174: invalid or conflicting name in service string found in the pluggable
database
Cause: The service name or network name in the specified service is invalid or it
conflicts with an existing service name or network name in the container database.
Action: Use an appropriate SERVICE_NAME_CONVERT clause and reissue the
statement.
ORA-65175: cannot grant SYSDBA privilege locally in the root
Cause: An attempt was made to grant SYSDBA privilege locally in the root of a
multitenant container database (CDB).
Action: While connected to the root, SYSDBA privilege can only be granted
commonly.
ORA-65176: system tablespace block size (string) does not match configured block
sizes
Cause: The block size of the system tablespace of the pluggable database to be
plugged in did not match the block sizes configured in the container database.
ORA-60001 to ORA-65535 32-43
Action: Configure the appropriate cache for the block size of the system
tablespace using the DB_<n>K_CACHE_SIZE parameter (where <n> is 2, 4, 8, 16,
or 32).
ORA-65177: cannot create common user with the same name as local user
Cause: An attempt was made to create a common user with the same name as an
existing local user.
Action: Specify a different user name.
ORA-65178: invalid logging mode specified for the pluggable database
Cause: An attempt was made to either enable a conflicting logging mode or to
disable a logging mode when it was not enabled.
Action: Check the current logging modes in DBA_PDBS for the pluggable
database and specify a valid mode.
ORA-65179: cannot keep datafiles for a pluggable database that is not unplugged
Cause: An attempt was made to drop a pluggable database without specifying the
INCLUDING DATAFILES clause, and the pluggable database has not been
unplugged.
Action: Unplug the pluggable database before dropping the pluggable database
or use the INCLUDING DATAFILES clause in the DROP PLUGGABLE
DATABASE statement.
ORA-65180: duplicate file name encountered - string
Cause: An attempt was made to issue a CREATE PLUGGABLE DATABASE
statement with a duplicate source or target file name for the source file name
mentioned in the message. This could be caused by incorrect SOURCE_FILE_
NAME_CONVERT or FILE_NAME_CONVERT clause.
Action: Use an appropriate SOURCE_FILE_NAME_CONVERT or FILE_NAME_
CONVERT clause to ensure that there are no duplicate source or target file names
and then reissue the statement.
ORA-65181: invalid argument supplied to CONTAINERS function
Cause: An attempt was made to create a multitenant container database (CDB)
view with an invalid table or view name.
Action: Specify a valid table or view name of the form <owner>.<table_name |
view_name>.
ORA-65182: unable to modify the state of pluggable database string
Cause: An attempt was made to modify the state of a pluggable database which is
currently in the middle of a state transition.
Action: Retry the operation later.
ORA-65183: FORCE open of a PDB on only a few instances where its open on is not
allowed
Cause: An attempt was made to FORCE open a pluggable database on only a few
Oracle RAC instances where it is currently open.
Action: Retry the FORCE open and include all Oracle instances where the PDB is
open
ORA-65184: encountered data files belonging to different PDBs
Cause: An attempt was made to invoke DBMS_PDB.RECOVER() by specifying
data files or a directory name containing data files belonging to different PDBs.
32-44 Oracle Database Error Messages
Action: Check the paths provided to DBMS_PDB.RECOVER() and retry the
operation.
ORA-65185: could not find data file belonging to SYSTEM tablespace
Cause: An attempt was made to invoke DBMS_PDB.RECOVER() by specifying
data files or a directory name containing data files where no data file belonging to
SYSTEM tablespace was found. SYSTEM tablespace is critical to recover a PDB.
Action: Check the paths specified to dbms_pdb.recover() and ensure that it at
least contains data files belonging to SYSTEM tablespace.
ORA-65400: Table does not have CLUSTERING clause associated with it
Cause: User attempts to modify clustering clasue on a table that that does not
have one.
Action: Create CLUSTERING clause on the table first.
ORA-65402: invalid option on CLUSTERING clause
Cause: Invalid option on CLUSTERING clause. Only [YES | NO ] ON LOAD or
[YES | NO ] ON DATA MOVEMENT are valid.
Action: Correct the option on the CLUSTERING clause.
ORA-65403: invalid usage of CLUSTERING clause
Cause: Invalid usage of CLUSTERING clause. The clause can be specified only for
CREATE/ATLER TABLE/SNAPSHOT/MATERIALIZED VIEW
Action: Don't use CLUSTERING clause in this statement
ORA-65404: CLUSTERING clause specified more than once on a table
Cause: A table can have only one clustering clause. The clasue was specified
multiple times.
Action: Correct the statement to use only one CLUSTERING clause.
ORA-65405: CLUSTERING clause cannot be used with existing table options
Cause: CLUSTERING clause conflicts with other clasues on the table. Custering
cannot be used on IOT, CLUSTERED, GLOBAL TEMPORARY TABLE,
EXTERNAL TABLE.
Action: Correct the statement so clustering clause does not conflict with other
clauses.
ORA-65406: invalid option on CLUSTERING clause
Cause: CLUSTERING was not followed by BY [LINEAR |
MULTIDIMENSIONAL] ORDER.
Action: Correct the option on the CLUSTERING clause.
ORA-65407: CLUSTERING clause already exists on the table
Cause: Add CLUSTERING clause was specified on a table with an existing
clustering clause.
Action: If table has clustering, you can only change ON LOAD or ON DATA
MOVEMENT options. To change other options, you must first drop the clause.
ORA-65408: CLUSTERING clause has too many columns in BY ORDER
Cause: More than 10 columns were specified in the BY ORDER subclause. You
can have at most 10 columns in the BY ORDER subclause.
ORA-60001 to ORA-65535 32-45
Action: Lower the number of columns in the BY ORDER subclause to a value of
10 or less.
ORA-65409: CLUSTERING clause has too many MULTIDIMENSIONAL columns
or groups
Cause: More than 40 columns were specified in the MULTIDIMENSIONAL
ORDER subclause.You can have at most 40 columns in the MULTIDIMENSIONAL
ORDER subclause.
Action: Lower the number of columns in the BY MULTIDIMENSIONAL ORDER
subclause to a value of 40 columns or less or 4 groups or less.
ORA-65410: CLUSTERING clause can have only scalar columns
Cause: A non-scalar column was specified in the BY LINEAR or
MULTIDIMENSIONAL ORDER subclause. Also, virtual or hidden columns are
not allowed.
Action: Specify only scalar columns in the BY [LINEAR |
MULTIDIMENSIONAL] ORDER subclause.
ORA-65411: CLUSTERING clause does not exist
Cause: An attempt was made to modify or drop a CLUSTERING clause in a table
that had no CLUSTERING clause associated with it.
Action: Do not attempt to modify a nonexistent CLUSTERING clause.
ORA-65412: invalid option on ALTER TABLE .. CLUSTERING ..
Cause: You have specified an invalid option on ALTER TABLE...CLUSTERING.
For example, you specified DROP and ADD CLUSTERING in one statement.
Action: Correct the statement.
ORA-65413: cannot resolve referenced object in the CLUSTERING clause
Cause: An object was referenced in the CLUSTERING clause that could not be
resolved to a base table reference.
Action: The CLUSTERING clause can refer to base tables only.
ORA-65414: column resolves to multipe tables in the CLUSTERING clause
Cause: A column resolved to multiple tables in the CLUSTERING clause.
Action: Correct the statement. The column should resolve to only one table. Need
to qualify by table name.
ORA-65415: wrong join condition in the CLUSTERING clause
Cause: The CLUSTERING clause had an OR condition and the individual join
condition on the base table columns was not an equijoin.
Action: Correct the statement. Make sure that join conditions are equijoins and
there are no OR conditions, or no expressions in the join.
ORA-65416: multiple mimension tables in the CLUSTERING clause
Cause: Joins in the CLUSTERING referenced a dimension table more than once.
Action: Correct the statement. Remove one of the references.
ORA-65417: illegal dimenstion table in the CLUSTERING clause
Cause: The dimension table in the CLUSTERING clause was illegal. Dimension
table cannot be GLOBAL TEMPORARY TABLE or EXTERNAL TABLE.
32-46 Oracle Database Error Messages
Action: Rewrite the statement so it does not use an illegal option on the
dimension table.
ORA-65418: primary or unique Key constraint missing in CLUSTERING join
Cause: The join between the fact and dimension tables in the CLUSTERING
clause did not have a primary or unique key constraint on the dimension table.
Action: Add a primary or unique key constraint to the join columns on the
dimension table.
ORA-65419: columns in a clustering group come from different tables
Cause: Columns in the clustering group did not come from the same table. For
example: .. CLUSTERING BY ..( (t1.c1, t2.c2), (t2.c1, t2.c2) ). Clustering group
(t1.c1, t2.c2) must contain references to only one table.
Action: Restructure the clustering group so it contains only references to a single
table.
ORA-65420: columns in a join condition in the CLUSTERING clause are not
compatible
Cause: The data type of columns in the join condition of CLUSTERING clause
were not compatible. They must be of the same type.
Action: Select a compatible data type for the join conditions in the CLUSTERING
clause.
ORA-65421: The CLUSTERING clause is defined on columns that are to be
modified
Cause: An ALTER TABLE MODIFY COLUMN command was issued on a column
on which a CLUSTERING clause exists.
Action: Drop the CLUSTERING clause before attempting to modify the column.
ORA-65422: The CLUSTERING clause already has a zonemap defined on it
Cause: An ALTER TABLE MODIFY CLUSTERING command was issued with the
WITH MATERIALIZED ZONEMAP option but the table already had zonemap
define on it.
Action: Drop the zonemap associated with the base table before attempting to
add zonemap using the CLUSTERING clause.
ORA-65423: The CLUSTERING clause does not have a zonemap associated with it
Cause: An ALTER TABLE MODIFY CLUSTERING command was issued with the
WITHOUT MATERIALIZED ZONEMAP option but the table did not have
zonemap associated with the CLUSTERING clause.
Action: Do not use the ALTER TABLE MODIFY CLUSTERING WITHOUT
ZONEMAP.
ORA-65424: CLUSTERING clause has too many joins
Cause: More than 4 joins were specified in the CLUSTERING clause. You can
have at most 4 joins to the dimension tables.
Action: Reduce the number of joins to 4 or less.
ORA-65425: CLUSTERING clause not supported for table stored in tablespace of
this storage type
Cause: An attempt was made to define clustering on a table stored in non-Oracle
Exadata storage.
ORA-60001 to ORA-65535 32-47
Action: Create this table in a tablespace residing on Oracle Exadata storage or
remove the CLUSTERING clause.
ORA-65426: Non-scalar data type is used for a clustering column
Cause: Oracle cannot perform data clustering because an attempt was made to
populate a clustering column with non-scalar data values, or a clustering column
defaulted to non-scalar values was omitted.
Action: Use only scalar data type for the clustering columns, or disable data
clustering with NO_CLUSTERING hint.
ORA-65451: Advanced index compression is not supported for tablespaces on this
storage type.
Cause: An attempt was made to use advanced index compression on an
unsupported storage type.
Action: Drop and re-create the index with a compression option that is supported
on the current storage type.
ORA-65455: family string is invalid
Cause: An invalid family was used to specify a parameter value.
Action: Use a valid family.
ORA-65456: family string is not valid in string instance
Cause: The specified family could not be used in the current instance type.
Action: Remove the family from the environment variable ORACLE_FAMILY.
ORA-65457: family string is not valid in string instance
Cause: The specified family could ot be used in the current instance type.
Action: Use a family that is valid for this instance to set the initialization
parameter.
ORA-65458: maximum length of parameter qualifier exceeded
Cause: Too many characters were specified in the parameter qualifier in the
initialization parameter file.
Action: Change the parameter qualifier to a valid SID or family.
ORA-65459: family used with a specific system identifier (SID)
Cause: A SID was used with FAMILY.
Action: Use FAMILY without a SID.
ORA-65460: family string is invalid
Cause: An invalid family was specified for this instance in ORACLE_FAMILY.
Action: Use a valid family in ORACLE_FAMILY.
ORA-65461: invalid parameter name specified with CONTAINER clause set to ALL
Cause: The CONTAINER clause was set to ALL in the ALTER SYSTEM SET
statement for a non-PDB modifiable parameter.
Action: Retry the ALTER SYSTEM SET statement without the CONTAINER
clause.
ORA-65466: family 'string' contains an illegal character or is too long
32-48 Oracle Database Error Messages
Cause: The specified family contained an illegal character or the family specified
was too long, which cannot occur in an SPFILE setting. Illegal characters include
*,#"'=() and whitespace.
Action: Use a family that does not contain a special character or whitespace.
Check platform-specific documentation for the maximum length of family.
ORA-65500: could not modify DB_UNIQUE_NAME, resource exists
Cause: DB_UNIQUE_NAME could not be modified, because a database resource
identified by DB_UNIQUE_NAME existed in the cluster. To modify DB_
UNIQUE_NAME, any resource it identifies must first be removed.
Action: Remove the database resource identified by DB_UNIQUE_NAME before
modifying DB_UNIQUE_NAME.
ORA-65501: locator from string container cannot be used in container string for this
operation
Cause: In a pluggable database environment, an attempt was made to modify a
LOB using a locator which belongs to a different container.
Action: Switch back to the original container.
ORA-65502: cannot access temporary LOB data
Cause: The database did not open.
Action: Open the database before accessing LOB data.
ORA-65535: Oracle client cannot handle error code exceeding 65535. Actual error
code and message follow:
Cause: Oracle server encountered an error whose error code exceeded 65535.
Older Oracle clients (prior to version 12) cannot handle error codes larger than
65535.
Action: Actual Oracle error code and error message are a part of the error
message for ORA-65535. Upgrade Oracle client to version 12 client libraries or
higher.


EXP-00000 to EXP-00114
EXP-00000: Export terminated unsuccessfully
Cause: Export encountered an Oracle error.
Action: Look up the accompanying Oracle message in the ORA message chapters
of this manual, and take appropriate action.
EXP-00001: data field truncation - column length=number, buffer size=number
actual size=number
Cause: Export could not fit a column in the data buffer.
Action: Record the given size parameters and the accompanying messages and
report this as an Export internal error to customer support. (Part of the table has
been exported. Export will continue with the next table.)
EXP-00002: error in writing to export file
Cause: Export could not write to the export file, probably because of a device
error. This message is usually followed by a device message from the operating
system.
Action: Take appropriate action to restore the device.
EXP-00003: no storage definition found for segment(number, number)
Cause: Export could not find the storage definitions for a cluster, index, or table.
Action: Record the accompanying messages and report this as an Export internal
error to customer support.
EXP-00004: invalid username or password
Cause: An invalid username or password was specified.
Action: Retry with a valid username and password.
EXP-00005: all allowable logon attempts failed
Cause: Attempts were repeatedly made to log on with an invalid username or
password.
Action: Shut down the utility, then restart and retry with a valid username and
password.
EXP-00006: internal inconsistency error
Cause: Export's data structure was corrupted.
Action: Record the accompanying messages and report this as an Export internal
error to customer support.
EXP-00007: dictionary shows no columns for string.string
33-2 Oracle Database Error Messages
Cause: Export failed to gather column information from the data dictionary. The
table may have been dropped.
Action: Retry the export and, if this error recurs, report it as an Export internal
error to customer support.
EXP-00008: ORACLE error number encountered
Cause: Export encountered the referenced Oracle error.
Action: Look up the Oracle message in the ORA message chapters of this manual
and take appropriate action.
EXP-00009: no privilege to export string's table string
Cause: An attempt was made to export another user's table. Only a database
administrator can export another user's tables.
Action: Ask your database administrator to do the export.
EXP-00010: string is not a valid username
Cause: An invalid username was specified.
Action: Shut down the utility, then restart and retry with a valid username.
EXP-00011: string.string does not exist
Cause: Export could not find the specified table.
Action: Retry with the correct table name.
EXP-00012: string is not a valid export mode
Cause: An invalid export mode was specified.
Action: Retry with a valid export mode.
EXP-00013: respond with either 'Y', 'N', RETURN or '.' to quit
Cause: An invalid response was entered.
Action: Enter any of the responses shown in the message.
EXP-00014: error on row number of table string
Cause: Export encountered an Oracle error while fetching rows.
Action: Look up the accompanying Oracle message in the ORA message chapters
of this manual and take appropriate action.
EXP-00015: error on row number of table string, column string, datatype number
Cause: Export encountered an error while fetching or writing the column. An
accompanying message gives more information.
Action: Correct the error and try again.
EXP-00016: ORACLE error encountered while reading default auditing options
Cause: Export encountered an Oracle error while reading the default auditing
options (those for updates, deletes, and so on).
Action: Look up the accompanying Oracle message in the ORA message chapters
of this manual and take appropriate action.
EXP-00017: feature "string" is needed, but not present in database
Cause: The command entered requires the specified feature. Either that feature is
not installed, or the row describing the feature is missing from table V$OPTION
Action: Reinstall Oracle with the feature specified in the message.
EXP-00000 to EXP-00114 33-3
EXP-00018: datatype (number) for column string, table string.string is not supported
Cause: Export does not support the referenced datatype.
Action: Retry with an acceptable datatype (CHAR, NUMBER, DATE, LONG, or
RAW).
EXP-00019: failed to process parameters, type 'EXP HELP=Y' for help
Cause: Invalid command-line parameters were specified.
Action: Check the online help screen for the set of valid parameters, then retry.
EXP-00020: failed to allocate memory of size number
Cause: Export failed to allocate the necessary memory.
Action: Decrease the export buffer size so that less memory is required, or
increase the runtime memory size for Export.
EXP-00021: can only perform incremental export in Full Database mode
Cause: USER or TABLE mode was specified when doing an incremental export.
Action: Specify FULL database mode (FULL=Y) and retry.
EXP-00022: must be SYS or SYSTEM to do incremental export
Cause: The privileges needed to do an incremental export do not exist. Only a
data base administrator can do incremental exports.
Action: Ask the database administrator to do the incremental export.
EXP-00023: must be a DBA to do Full Database or Tablespace export
Cause: The privileges needed to do a FULL database export do not exist. Only a
database administrator can do a FULL database export.
Action: Ask the database administrator to do the FULL database export.
EXP-00024: Export views not installed, please notify your DBA
Cause: The necessary Export views were not installed.
Action: Ask the database administrator to install the required Export views.
EXP-00025: dictionary shows no column for constraint string.number
Cause: Export failed to gather column information about the referenced constraint
from the data dictionary. The constraint may have been altered.
Action: Retry the export and, if this error recurs, report it as an Export internal
error to customer support.
EXP-00026: conflicting modes specified
Cause: Conflicting export modes were specified.
Action: Specify only one parameter and retry.
EXP-00027: failed to calculate ORACLE block size
Cause: Export failed to calculate the Oracle block size.
Action: Report this as an Export internal error to customer support.
EXP-00028: failed to open string for write
Cause: Export failed to open the export file for writing. This message is usually
followed by device messages from the operating system.
Action: Take appropriate action to restore the device.
EXP-00029: Incremental export mode and consistent mode are not compatible
33-4 Oracle Database Error Messages
Cause: Both consistent and incremental exports were specified.
Action: None. Consistent mode is turned off.
EXP-00030: Unexpected End-Of-File encountered while reading input
Cause: Encountered an End-Of-File while reading the user input.
Action: If input to export is being redirected, check the file for errors.
EXP-00031: Arraysize not in valid range. Using arraysize=number
Cause: The arraysize value specified is not in the valid range.
Action: None
EXP-00032: Non-DBAs may not export other users
Cause: Only database administrators can export to other users. A non- database
administrator attempted to specify owner=user where exporter is not the user.
Action: Request that this operation be performed by the database administrator.
EXP-00033: Could not find environment character set
Cause: The environment character set is missing or incorrectly specified.
Action: Ensure that the environment character set is correctly specified and is
present.
EXP-00034: error on rowid: file# number block# number slot# number
Cause: Identifies the rowid on which an error occurred.
Action: This is an information message. No action is required.
EXP-00035: QUERY parameter valid only for table mode exports
Cause: You specified the QUERY parameter in an export command, but you are
not performing a table mode export. The QUERY parameter cannot be used for a
user mode export, a full export, nor a point in time recovery export.
Action: If you want to select a subset of rows for a table, you must export the table
independently with a table mode export. Issue a table mode export command that
specifies the table name and the query you want to execute during export.
EXP-00036: Object number non-existent in dictionary
Cause: The specified object could not be found in the dictionary. The object might
have been dropped during the export
Action: The object no longer exists; no action is needed.
EXP-00037: Export views not compatible with database version
Cause: The Export utility is at a higher version than the database version and is
thereby incompatible.
Action: Use the same version of Export utility as the database.
EXP-00038: Bad Hash cluster id in clu$
Cause: The function id in clu$ is not a legal number. Clu$ has become corrupted.
Action: Contact Worldwide Support
EXP-00039: export file string must be on a disk
Cause: On some platforms, export can read files from tape. This message is
displayed if the first file in an export file set was on disk and you specified a tape
device for a second or subsequent file.
EXP-00000 to EXP-00114 33-5
Action: Verify that you have specified the correct file name for the export file.
Remember that all export files can be either on disk or all files can be on tape, but
not mixed both tape and disk.
EXP-00040: Dump file and log file must be different
Cause: The dump file and log file cannot be the same file.
Action: Specify different file names for the dump file and the log file, then retry
the operation.
EXP-00041: INCTYPE parameter is obsolete
Cause: Export encountered the INCTYPE parameter when parsing Export
options. Incremental Exports are no longer supported.
Action: Consult the Oracle Backup and Recovery guide. Export will attempt to
continue.
EXP-00042: Missing NLS_CHARACTERSET/NLS_NCHAR_CHARACTERSET in
props$
Cause: A value for NLS_CHARACTERSET/NLS_NCHAR_CHARACTERSET
was not entered in the props$ table"
Action: internal error.
EXP-00043: Invalid data dictionary information in the row where column "string" is
"string" in table string
Cause: The export utility retrieved invalid data from the data dictionary.
Action: Contact Oracle Worldwide Suport.
EXP-00044: must be connected 'AS SYSDBA' to do Point-in-time Recovery or
Transportable Tablespace import
Cause: The user must log in 'as SYSDBA' to perform transportable tablespace
imports or Point-In-Time Recovery imports.
Action: Ask your database adminstrator to perform the Transportable Tablespace
import or the Tablespace Point-in-time Recovery import.
EXP-00045: Cannot export SYSTEM Tablespace for Point-in-time Recovery or
Transportable Tablespace
Cause: SYSTEM tablespace cannot be part of recovery set or transportable
tablespace set.
Action: Contact Oracle Wordwide Support.
EXP-00046: Tablespace named string does not exist
Cause: The specified tablespace does not exist in dictionary.
Action: Contact Oracle Wordwide Support.
EXP-00047: Missing tablespace name(s)
Cause: Tablespace name(s) were not supplied
Action: Provide tablespace name(s)
EXP-00048: Cannot export SYSAUX Tablespace for Point-in-time Recovery or
Transportable Tablespace
Cause: SYSAUX tablespace cannot be part of recovery set or transportable
tablespace set.
Action: Contact Oracle Wordwide Support.
33-6 Oracle Database Error Messages
EXP-00049: string option is not compatible with Point-in-time Recovery or
Transportable Tablespace Export
Cause: An option was specified incompatible with Point-in-time Recovery or
Transportable Tablespace Export.
Action: Retry the Export without the displayed option.
EXP-00050: Cannot perform Partition Export "string" on non-partitioned table
"string"
Cause: The table specified in this Partition Export is not a partitioned table.
Action: Use Table mode, or specify a non-partitioned table.
EXP-00051: "string" - given partition or subpartition name is not part of "string"
table
Cause: The specified partition or subpartition name is not in the specified table.
Action: Check if the correct table, partition or subpartition name was specified.
EXP-00052: error on row number of partition string
Cause: Export encountered the referenced Oracle error while fetching rows.
Action: Look up the Oracle message in the ORA message chapters of this manual
and take appropriate action.
EXP-00053: unable to execute QUERY on table string because the table has inner
nested tables
Cause: You specified the QUERY parameter on a table that has one or more inner
nested tables. The QUERY parameter cannot be specified on tables that have inner
nested tables.
Action: Export the entire table by omitting the QUERY parameter.
EXP-00054: error on row number of subpartition string
Cause: Export encountered the referenced Oracle error while fetching rows.
Action: Look up the Oracle message in the ORA message chapters of this manual
and take appropriate action.
EXP-00055: string.string is marked not exportable
Cause: An object was marked as non-exportable in the NOEXP$ table.
Action: Consult your database administrator.
EXP-00057: Failure to initialize parameter manager
Cause: The parameter manager failed in intialization.
Action: Record the messages that follow and report this to Oracle Wordwide
Support as an Export internal bug.
EXP-00058: Password Verify Function for string profile does not exist
Cause: Cannot find the function for the profile.
Action: Check if the profile was created properly.
EXP-00059: error converting an object type's identifier to characters
Cause: An invalid length of an object type identifier prevented its conversion.
Action: Contact Oracle Worldwide Support
EXP-00060: an object type had multiple TYPE BODYs
Cause: More than one TYPE BODY was found for an object type.
EXP-00000 to EXP-00114 33-7
Action: Try dropping the TYPE BODY, if that is not successful, contact Oracle
Worldwide Support
EXP-00061: unable to find the outer table name of a nested table
Cause: While exporting a bitmap index or posttable action on an inner nested
table, the name of the outer table could not be located, using the NTAB$ table.
Action: Verify the table is properly defined.
EXP-00062: invalid source statements for an object type
Cause: TYPE was not found in the statements in SOURCE$ for an Object Type
Action: Contact Oracle Worldwide Support.
EXP-00063: error in changing language handle
Cause: Unable to change language handle.
Action: Contact Oracle Worldwide Support.
EXP-00064: string is an inner nested table and cannot be exported.
Cause: An attempt was made to export an inner nested table without its parent
table.
Action: Export the parent of the inner nested table.
EXP-00065: Error writing lob to the dump file.
Cause: The current LOB could not be written to the dump file.
Action: Identify the cause of the write failure and fix it.
EXP-00066: Object table string is missing its object identifier index
Cause: All object tables must have an object identifier index, but the specified
table was missing an index on its object identifier column.
Action: Recreate the type table and retry the operation.
EXP-00068: tablespace string is offline
Cause: Export failed to export tablespace (tablespace being offline).
Action: Make tablespace online and re export.
EXP-00070: attempt to free unallocated memory
Cause: An attempt was made to free memory that was not allocated.
Action: Contact Oracle Worldwide Support
EXP-00071: QUERY parameter not compatible with Direct Path export
Cause: You specified a value for the QUERY parameter for a direct path export.
The QUERY parameter cannot be used with a direct path export.
Action: Re-issue the export command with DIRECT=N or omit the DIRECT
parameter from the command line.
EXP-00072: error closing export file string
Cause: An error occurred while trying to close the export file.
Action: Contact Oracle Worldwide Support.
EXP-00073: dump file size too small
Cause: You specified either the FILESIZE parameter or the VOLSIZE parameter (if
your platform supports it), and the value of the parameter is too small to hold the
header information for the export file, plus any data.
33-8 Oracle Database Error Messages
Action: Increase the value of the FILESIZE or VOLSIZE parameter.
EXP-00074: rounding VOLSIZE down, new value is string
Cause: The VOLSIZE parameter must be a multiple of the RECORDLENGTH, but
the value you specified for VOLSIZE does not meet this requirement. The value of
VOLSIZE has been rounded down to be a multiple of the RECORDLENGTH used
for the dump file.
Action: No action is required. You can adjust the VOLSIZE or RECORDLENGTH
parameter to avoid this message. When importing this file, you must specify the
VOLSIZE value reported by this message.
EXP-00075: rounding FILESIZE down, new value is string
Cause: The FILESIZE parameter must be a multiple of the RECORDLENGTH, but
the value you specified for FILESIZE does not meet this requirement. The value of
FILESIZE has been rounded down to be a multiple of the RECORDLENGTH used
for the dump file.
Action: No action is required. You can adjust the FILESIZE or RECORDLENGTH
parameter to avoid this message. When importing this file, you must specify the
FILESIZE value reported by this message.
EXP-00076: multiple devices specified for tape output
Cause: You specified multiple file names when doing an export to a tape device.
EXPORT uses the same device for writing all files, of the number of tape volumes
required. For this reason, export will accept only one value for the FILE parameter
when writing to tape.
Action: Reenter the EXPORT command, but specify only one tape device in the
FILE parameter.
EXP-00077: multiple output files specified for unbounded export file
Cause: You specified multiple file names when doing an export and you also
specified a value of 0 for the FILESIZE parameter. Note that 0 is the value used if
FILESIZE is not specified on the command line. Since a value of 0 for FILESIZE
means that only one file will be written and there is no size limit for that file, the
other files you specified in the FILE parameter can never be used.
Action: If you intended to write multiple files, respecify the command but use the
FILESIZE to specify the maximum number of bytes that EXPORT should write to
each file. If you intended to write only one file with no limits on it's size, reissue
the EXPORT command but specify only one file name for the FILE parameter.
EXP-00078: Error exporting metadata for index string. Index creation will be
skipped
Cause: Domain indexes export private metadata via anonymous PL/SQL blocks
prior to the CREATE INDEX statement. Export does this by calling the
ODCIIndexGetMetadata method on the implementation type associated with the
index. A problem occurred inside this routine. Because the metadata is considered
an integral part of the index, the CREATE INDEX statement was not written to the
dump file.
Action: Contact the developer of the index's implementation type. If this is an
Oracle-supplied index (perhaps via a data cartridge), contact Oracle Worldwide
Support.
EXP-00079: Data in table "string" is protected. Conventional path may only be
exporting partial table.
EXP-00000 to EXP-00114 33-9
Cause: User without the execute privilege on DBMS_RLS, the access control
package, tries to export a table that has access control. Since table owner is also
subjected to access control, the owner may not be able to export all rows in the
table, but only the ones he can see. Also, to preserve integrity of the table, user
exporting the table should have enough privilege to recreate the table with the
security policies at import time. Therefore, it is strongly recommended the
database administrator should be handling exporting of this table. Granting the
table owner execute privilege would also satisfy this security check, though it
might have other security implications. If the table does not have objects, can use
direct mode.
Action: Ask the database administrator to export/import this table/view.
EXP-00080: Data in table "string" is protected. Using conventional mode.
Cause: User without the execute privilege on DBMS_RLS, the access control
package, tries to direct export a table that has access control enabled. Using
conventional export mode instead. Note that because of access control, only a
partial table may be exported.
Action: Ask the database administrator to export/import this table/view.
EXP-00081: Exporting access control for table/view "string" as non-DBA.
Cause: A non-DBA user tries to export table/view and the associated fine grain
access control policies. The user may not have enough privilege to recreate the
access control policies when importing the table/view. And such an event may
cause inconsistency in the security model of the table/view.
Action: Ask the database administrator to export/import this table/view.
EXP-00082: Invalid function name passed to procedural object support: string
Cause: Internal inconsistency error: The listed function is not a method on
export's procedural object interface specification.
Action: Contact Oracle Worldwide Support
EXP-00083: The previous problem occurred when calling string.string.string
Cause: The listed package provides export/import support for procedural
Action: Contact Oracle Worldwide Support. Most packages are supplied by
Oracle internal cartridge or server development groups. The package name will
help Support determine the correct owner of the problem.
EXP-00084: Unexpected DbmsJava error number at step number
Cause: The error was returned from a call to a DbmsJava procedure.
Action: Record the accompanying messages and report this as an Export internal
error to customer support.
EXP-00085: The previous problem occurred when calling string.string.string for
object number
Cause: The listed package provides export/import support for procedural objects,
i.e, those whose DDL is supplied by stored procedures. The previously listed error
occurred while calling the specified function.
Action: Contact Oracle Worldwide Support. Most packages are supplied by
Oracle internal cartridge or server development groups. The package name will
help Support determine the correct owner of the problem.
EXP-00086: Primary key REFs in table "string"may not be valid on import
33-10 Oracle Database Error Messages
Cause: The specified table contains primary key REFs which may not be valid in
the import database.
Action: Do not use Export/Import to move Primary key REFs between databases
having differing character sets.
EXP-00087: Problem with internal hash table of schema/table names
Cause: Most likely a problem with allocating memory for the hash table entries.
Action: Contact Oracle Worldwide Support
EXP-00089: invalid FILE_FORMAT specification
Cause: The FILE_FORMAT specification did not contain an instance of "%s". This
wildcard string must be present.
Action: Correct the error and reenter the EXPORT command.
EXP-00090: cannot pin type "string"."string"
Cause: Export was unable to pin the specified type in the object cache. This is
typically caused because a type could not be made valid (for example because of
authorization violations in accessing subtypes).
Action: Fix the problem with the offending type until the type can be successfully
compiled.
EXP-00091: Exporting questionable statistics.
Cause: Export was able export statistics, but the statistics may not be usuable. The
statistics are questionable because one or more of the following happened during
export: a row error occurred, client character set or NCHARSET does not match
with the server, a query clause was specified on export, only certain partitions or
subpartitions were exported, or a fatal error occurred while processing a table.
Action: To export non-questionable statistics, change the client character set or
NCHARSET to match the server, export with no query clause, export complete
tables. If desired, import parameters can be supplied so that only non-questionable
statistics will be imported, and all questionable statistics will be recalculated.
EXP-00092: Unable to set NLS_NUMERIC_CHARACTERS to required defaults.
Cause: Export was unable to set NLS_NUMERIC_CHARACTERS to '.,'
Action: Record the accompanying messages and report this as an Export internal
error to customer support.
EXP-00093: Could not convert to server character set's handle
Cause: Internal error.
Action: Contact Worldwide support.
EXP-00094: Could not convert to server national character set's handle
Cause: Internal error.
Action: Contact Worldwide support.
EXP-00095: Flashback_time and Flashback_scn are not compatible
Cause: Both flashback_time and flashback_scn paramerers were specified.
Action: Reissue command with only one flashback parameter.
EXP-00097: Object type "string"."string" is not in a valid state, type will not be
exported
EXP-00000 to EXP-00114 33-11
Cause: The object type's status is invalid which may be caused by a dependant
type's modification (or removal) without cascading the change.
Action: The type must be recompiled using ALTER TYPE COMPILE.
EXP-00098: Data in table has not been upgraded, table will not be exported
Cause: Export is attempting to process a table containing references to a type
which has evolved. In order for Export to process the table successfully, all data
within each table must be upgraded to the latest revision of each referenced type.
Action: The table must be updated using ALTER TABLE UPGRADE DATA.
EXP-00099: Table "string"."string" is not in a valid state, table will not be exported
Cause: A table or one of its dependant types has modified without cascading the
change. This left the table in an INVALID state.
Action: The table must be updated using ALTER TABLE UPDATE.
EXP-00100: error converting an object type's hashcode to characters
Cause: An invalid length of an object type identifier prevented its conversion.
Action: Contact Oracle Worldwide Support
EXP-00101: Version 1 extensible index "string"."string" can not be included in
Transportable Tablespace Export
Cause: Transporable Tablespace extensible indexes must be at least version 2.
Action: Upgrade extensibile index implementation to version 2 specifications.
EXP-00102: Resumable parameters ignored -- current session not resumable
Cause: Current session is not resumable.
Action: Must specify RESUMABLE=Y to enable resumable session in order for the
RESUMABLE_NAME and RESUMABLE_TIMEOUT parameters to take effect.
EXP-00103: The FLASHBACK_TIME parameter was invalid
Cause: FLASHBACK_TIME did not contain a valid timestamp or an expression
that yields a valid timestamp.
Action: Specify a timestamp value in the format of YYYY-MM-DD HH24:MI:SS or
an expression that evaluates to a valid timestamp.
EXP-00104: datatype (string) of column string in table string.string is not supported,
table will not be exported
Cause: The column is of a datatype which does not contain the required support.
The table will not be exported.
Action: Use the Data Pump version of Export to export this table.
EXP-00105: parameter string is not supported for this user
Cause: The user attempted to specify either CONSISTENT or OBJECT_
CONSISTENT when connected as sysdba.
Action: If a consistent export is needed, then connect as another user.
EXP-00106: Invalid Database Link Passwords
Cause: Invalid Encoded Password for Database Link
Action: Please drop the Database Link and recreate it after import.
EXP-00107: Feature (string) of column string in table string.string is not supported.
The table will not be exported.
33-12 Oracle Database Error Messages
Cause: Export does not contain the required support for this feature. The table
will not be exported.
Action: Use the Data Pump version of Export to export this table.
EXP-00108: NULL lob fetched
Cause: Internal error
Action: Contact Oracle Worldwide Support.
EXP-00109: XSL delimiter not found
Cause: Internal error
Action: Contact Oracle Worldwide Support.
EXP-00110: Tablespace string is encrypted and will not be exported
Cause: Encrypted Tablespace feature is not supported by classic export
Action: Use DATAPUMP Utility to export this tablespace.
EXP-00111: Table string resides in an Encrypted Tablespace string and will not be
exported
Cause: Encrypted Tablespace feature is not supported by classic export
Action: Use DATAPUMP Utility to export this table.
EXP-00112: Index string is of XMLType and could not be exported
Cause: Export does not contain the required support for this feature. The index
could not be exported.
Action: Use Oracle Data Pump Utility to export this index.
EXP-00113: Feature string is unsupported. string string.string could not be exported
Cause: Export does not contain the required support for this feature.
Action: Use Oracle Data Pump Utility
EXP-00114: Length of string string is exceeding the maximum limit
Cause: Provided length was more than the maximum limit allowed.
Action: Check the input value and provide the correct value.
34
IMP-00000 to IMP-00402 4 3
IMP-00000: Import terminated unsuccessfully
Cause: Import encountered an Oracle error.
Action: Look up the accompanying Oracle message in the ORA message chapters
of this manual, and take appropriate action.
IMP-00001: respond with either string, string, RETURN or '.' to quit
Cause: An invalid response was entered.
Action: Enter any of the responses shown in the message.
IMP-00002: failed to open string for read
Cause: Import failed to open the export file for reading. This message is usually
followed by a device message from the operating system.
Action: Take appropriate action to restore the device.
IMP-00003: ORACLE error number encountered
Cause: Import encountered the referenced Oracle error.
Action: Look up the Oracle message in the ORA message chapters of this manual,
and take appropriate action.
IMP-00004: invalid username or password
Cause: An invalid username or password was specified.
Action: Retry with a valid username and password.
IMP-00005: all allowable logon attempts failed
Cause: An attempt was repeatedly made to log on with an invalid username or
password.
Action: Retry with valid username and password.
IMP-00006: failed to allocate memory of size number
Cause: Import failed to allocate the necessary memory.
Action: Decrease the import buffer size so that less memory is required, or
increase the runtime memory size for Import.
IMP-00007: must be a DBA to import objects to another user's account
Cause: The privileges needed to import into another user's account do not exist.
Only a database administrator can import into another user's account.
Action: Ask the database administrator to do the import.
IMP-00008: unrecognized statement in the export file: string
34-2 Oracle Database Error Messages
Cause: Import did not recognize a statement in the export file. Either the export
file was corrupted, or an Import internal error has occurred.
Action: If the export file was corrupted, retry with a new export file. Otherwise,
report this as an Import internal error and submit the export file to customer
support.
IMP-00009: abnormal end of export file
Cause: The export file is probably from an aborted Export session.
Action: If so, retry the export and import. Otherwise, report this as an Import bug
and submit the export file that caused this error to customer support.
IMP-00010: not a valid export file, header failed verification
Cause: Either the file was not generated by Export or it was corrupted.
Action: If the file was indeed generated by Export, report this an Import bug and
submit the export file to customer support.
IMP-00011: formatted table data not currently supported
Cause: You tried to import an export file that contains formatted table data.
Import only supports export files containing binary table data. wher
Action: Retry using an export file that contains only binary table data.
IMP-00012: invalid export mode (character) in header
Cause: The Export mode specified in the export file header is invalid.
Action: Check the export file to see if it was corrupted. If it was not, report this as
an Import bug and submit the export file to customer support.
IMP-00013: only a DBA can import a file exported by another DBA
Cause: The privileges needed to Import an export file generated by a database
administrator do not exist. Only a database administrator can import such files.
Action: Ask the database administrator to do the import.
IMP-00014: option "string" is needed, but not present in database
Cause: The command entered requires the specified option. Either that option is
not installed, or the row describing the option is missing from table V$OPTION
Action: Reinstall Oracle with the option specified by the message.
IMP-00015: following statement failed because the object already exists:
Cause: Import failed to create an object because it already exists.
Action: Specify IGNORE=Y to ignore such errors and import rows even when
tables are not created because they already exist.
IMP-00016: required character set conversion (type number to number) not
supported
Cause: Import could not convert the character format of the export file into the
native character format.
Action: Change the user character set by setting the NLS_LANG environment
variable to match the character set of the export file.
IMP-00017: following statement failed with ORACLE error number:
Cause: Import failed to execute the statement from the export file because of an
Oracle error.
IMP-00000 to IMP-00402 34-3
Action: Look up the accompanying Oracle message in the ORA message chapters
of this manual and take appropriate action.
IMP-00018: partial import of previous table completed: number rows imported
Cause: A table was only partially imported because of an Oracle error.
Action: Look up the accompanying Oracle message in the ORA message chapters
of this manual and take appropriate action.
IMP-00019: row rejected due to ORACLE error number
Cause: Import encountered the referenced Oracle error while trying to import a
row.
Action: Look up the accompanying Oracle message in the ORA message chapters
of this manual and take appropriate action.
IMP-00020: long column too large for column buffer size (number)
Cause: The column buffer is too small. This usually occurs when importing
LONG data.
Action: Increase the insert buffer size 10,000 bytes at a time (for example). Use this
step-by-step approach because a buffer size that is too large may cause a similar
problem.
IMP-00021: INCTYPE parameter is obsolete
Cause: Import encountered the INCTYPE parameter when parsing Import
options. Incremental Imports are no longer supported.
Action: Consult the Oracle Backup and Recovery guide. Import will attempt to
continue.
IMP-00022: failed to process parameters, type 'IMP HELP=Y' for help
Cause: Invalid command-line parameters were specified.
Action: Check the online help screen for the set of valid parameters, then retry.
IMP-00023: Import views not installed, please notify your DBA
Cause: The necessary Import views were not installed.
Action: Ask your database administrator to install the required Import views.
IMP-00024: Only one mode (TABLES, FROMUSER, or FULL) can be specified
Cause: Parameters were specified that conflict with the import specification
FULL=Y.
Action: Retry, making sure not to specify FULL=Y.
IMP-00025: for DBA export files, FROMUSER must be specified with TOUSER
option
Cause: When importing a database administrator export file, you specified the
TOUSER parameter but not the FROMUSER parameter.
Action: Specify the FROMUSER parameter so that Import knows which user's
objects to import.
IMP-00027: failed to rollback partial import of previous table
Cause: Import encountered an Oracle error while trying to roll back a partial
import.
34-4 Oracle Database Error Messages
Action: Look up the accompanying Oracle message in the ORA message chapters
of this manual and take appropriate action. Then, log on to Oracle and check that
the partial import was not committed.
IMP-00028: partial import of previous table rolled back: number rows rolled back
Cause: Import encountered an Oracle error while trying to import a table.
Action: Look up the accompanying Oracle message in the ORA message chapters
of this manual and take appropriate action. Then, if necessary, re-import the table.
IMP-00029: cannot qualify table name by owner (string), use FROMUSER
parameter
Cause: A table name was qualified with the name of its owner, as shown in the
following example. This is not allowed. IMP SYSTEM/MANAGER
TABLES=(SCOTT.EMP)
Action: Use the FROMUSER parameter to specify the table's owner, as shown in
the following example: IMP SYSTEM/MANAGER FROMUSER=SCOTT
TABLES=(EMP, DEPT)
IMP-00030: failed to create file string for write
Cause: Import was unable to create the specified file with write enabled.
Action: Check the file name and file system for the source of the error.
IMP-00031: Must specify FULL=Y or provide FROMUSER/TOUSER or TABLES
arguments
Cause: The database administrator did not specify full or partial import.
Action: The database administrator must specify FROMUSER/TOUSER or table
arguments if not a full import.
IMP-00032: SQL statement exceeded buffer length
Cause: The buffer was too small for the SQL statement being read.
Action: Rerun with a larger buffer. This can also be an indication of a corruption
in the import datafile.
IMP-00033: Warning: Table "string" not found in export file
Cause: A table name was specified that does not exist in export file.
Action: Correct the table specification.
IMP-00034: Warning: FromUser "string" not found in export file
Cause: The user specified a FROMUSER name that does not exist in export file.
Action: Correct the FROMUSER specification.
IMP-00035: input file string must be on a disk
Cause: On some platforms, import can read files from tape. This message is
displayed if the first file in an export file set was on disk and you specified a tape
device for a second or subsequent file.
Action: Verify that you have specified the correct file name for the import file.
Remember that all input files can be either on disk or all files can be on tape, but
not mixed both tape and disk.
IMP-00036: Could not find environment character set
Cause: An environment character set was specified that was not recognized by
the Import utility.
IMP-00000 to IMP-00402 34-5
Action: Ensure that the spelling of the character set specified in the command line
parameter CHARSET (for Release 6 only) or the environment variable NLS_LANG
is correct.
IMP-00037: Character set marker unknown
Cause: The export file is corrupted.
Action: Try to obtain an uncorrupted version of the export file. If the export file is
not corrupted, report this as an Import internal error and submit the export file to
customer support.
IMP-00038: Could not convert to environment character set's handle
Cause: Internal error.
Action: Contact Worldwide Support.
IMP-00039: VOLSIZE does not match the value used for export: string
Cause: The value specified for VOLSIZE does not match the value specified
during the creation of the export file.
Action: If you believe that the specified VOLSIZE value is correct, verify that you
specified the correct file for import. If you specified the correct file but are unsure
about the correct value, re-execute the import command but specify VOLSIZE=0.
IMP-00040: FILESIZE does not match the value used for export: string
Cause: The value specified for FILESIZE does not match the value specified
during the creation of the export file.
Action: If you believe the specified FILESIZE value is correct, verify that you
specified the correct file for import. If you specified the correct file but are unsure
about the correct value, re-execute the import command but specify FILESIZE=0.
IMP-00041: Warning: object created with compilation warnings
Cause: The object in the SQL statement following this error was created with
compilation errors. If this error occurred for a view, it is possible that the base table
of the view was missing.
Action: This is a warning. The object may have to be recompiled before being
used.
IMP-00042: CHARSET used, but the export file has specific character set
Cause: The user requested that a specific character set be used to process an
export file that has a specific embedded character set ID. The ID in the export file
is accurate and should be used.
Action: Remove the CHARSET keyword from the command line.
IMP-00043: export file character set inconsistent
Cause: The character set of the export file and the environment character set (or
the character set specified with the CHARSET keyword) are inconsistent. One
character set is ASCII-based while the other is EBCDIC based.
Action: Specify the correct character set with the CHARSET keyword.
IMP-00044: unable to allocate enough memory for statement
Cause: Import was unable to allocate sufficient memory to read in the specified
statement and execute it.
Action: Increase the allocation for database buffers, restart the instance, and
reexecute the Import command.
34-6 Oracle Database Error Messages
IMP-00045: using VOLSIZE value from export file of string
Cause: Either you did not specify the VOLSIZE parameter in your IMPORT
command, or you specified VOLSIZE=0 and the export was created with a
non-zero value for VOLSIZE. Import will use the value specified in the export file.
Action: None required.
IMP-00046: using FILESIZE value from export file of string
Cause: Either you did not specify the FILESIZE parameter in your IMPORT
command, or you specified FILESIZE=0 and the export file was created with a
non-zero value for FILESIZE. Import will use the value specified in the export file.
Action: None required.
IMP-00047: unexpected file sequence number; expected number but found number
Cause: The header in the export file contains a sequence number that is used to
track the order in which multiple export files are written. The first export file is
assigned sequence number one, the second file is assigned sequence number two
and so on. This message is displayed when a number other than the expected
sequence number is found in the file header
Action: Execute the import command again, but specify the files in the order in
which Export wrote them.
IMP-00048: mismatched file header
Cause: During verification of the 2nd or subsequent file in a multi-file export,
Import found header fields in the file that did not match values in the first file.
Action: Check the names of the files created by Export and verify that you
specified them correctly for the import operation.
IMP-00049: Unknown language specified in CHARSET
Cause: An unknown language was listed in the CHARSET option.
Action: Use a known character set.
IMP-00050: Dump file and log file cannot be identical
Cause: Identical names were given to the dump file and log file.
Action: Specify different names for the dump file and log file and retry the
operation.
IMP-00051: Direct path exported dump file contains illegal column length
Cause: An invalid column length was encountered while processing column
pieces."
Action: Check to make sure the export file is not corrupted, or else report this to
Oracle Worldwide Support as an Import/Export internal bug and submit the
export file.
IMP-00052: Warning: Unable to set event for freelist communication with server
Cause: An event could not be set for current the session.
Action: If Import fails, give the Import user ALTER SESSION PRIV and retry the
operation.
IMP-00053: Import mode incompatible with Export dump file
Cause: The specified import option is incompatible with point-in-time- recovery
dump file.
Action: Generate a proper dump file or use point-in-time-recovery import mode.
IMP-00000 to IMP-00402 34-7
IMP-00054: must be connected 'AS SYSDBA' to do Point-in-time Recovery or
Transportable Tablespace import
Cause: The user must log in 'as SYSDBA' to perform transportable tablespace
imports or Point-In-Time Recovery imports.
Action: Ask your database adminstrator to perform the Transportable Tablespace
import or the Tablespace Point-in-time Recovery import.
IMP-00055: Warning: partition or subpartition "string":"string" not found in export
file
Cause: A partition or subpartition name was specified that does not exist in
export file.
Action: Check to make sure the partition or subpartition name belongs to the
table.
IMP-00056: multiple devices specified for tape input
Cause: You specified multiple file names when doing an import from a tape
device. Import uses the same device for reading all tapes, regardless of the number
of tape volumes required. For this reason, export will accept only one value for the
FILE parameter when writing to tape.
Action: Reenter the IMPORT command, but specify only one tape device in the
FILE parameter.
IMP-00057: Warning: Dump file may not contain data of all partitions of this table
Cause: The dump file used for this Table Import might not contain all of the data
belonging to the exported table.
Action: Check to see if the export was done as intended, or try performing a
Partition Import.
IMP-00059: Failure to initialize parameter manager
Cause: Parameter manager failed in initialization.
Action: Report this to Oracle Worldwide Support as an Import internal bug.
IMP-00060: Warning: Skipping table "string"."string" because object type
"string"."string" does not exist or has different identifier
Cause: An object type needed by the table, either does not exist on the
* target system or, if it does exist, it has a different object identifier.
Action: Create the object type on the target system with a valid
* identifier.
IMP-00061: Warning: Object type "string"."string" already exists with a different
identifier
Cause: An object type cannot be created because it already exists on the
* target system, but with a different identifier
Action: Drop the object type from the target system and retry the operation.
IMP-00062: Warning: The identifier on the dump file for object type
"string"."string" is invalid
Cause: The character string representing the object type's identifier
* could not be converted to an object identifier.
Action: Internal error.
34-8 Oracle Database Error Messages
IMP-00063: Warning: Skipping table "string"."string" because object type
"string"."string" cannot be created or has different identifier
Cause: An error occurred creating an object type that is used by the
* table.
Action: Examine the import log to determine why the object type could not
* be created. If the object type already existed, with a
* different object identifier, then drop the object type and
* retry the import.
IMP-00064: Definition of LOB was truncated by export
Cause: While producing the dump file, Export was unable to write the
*entire contents of a LOB. Import is therefore unable to
* reconstruct the contents of the LOB. The remainder of the
*import of the current table will be skipped.
Action: Delete the offending row in the exported database and retry the
*export.
IMP-00065: Import is unable to recreate lobs within objects.
Cause: An error occurred recreating a LOB within an imported object.
Action: Report this to Oracle Worldwide Support as an Import internal error.
IMP-00066: Missing NLS_CHARACTERSET in props$
Cause: No value for NLS_CHARACTERSET in props$.
Action: Contact Worldwide support.
IMP-00067: Could not convert to server character set's handle
Cause: Internal error.
Action: Contact Worldwide support.
IMP-00068: Could not find environment national character set
Cause: An environment national character set was specified that was not
recognized by the Import utility.
Action: Ensure that the spelling of the national character set specified in the
environment variable NLS_NCHAR is correct.
IMP-00069: Could not convert to environment national character set's handle
Cause: Internal error..
Action: Contact Worldwide support.
IMP-00070: Lob definitions in dump file are inconsistent with database.
Cause: The number of LOBS per row in the dump file is different than the
*number of LOBS per row in the table being populated.
Action: Modify the table being imported so that it matches the column
* attribute layout of the table that was exported.
IMP-00071: Object identifier of imported table mismatches object identifier of
existing table
IMP-00000 to IMP-00402 34-9
Cause: An attempt was made to import data into a table that was recreated under
a different object identifier than the object identifier used for the exported object
table. Under this situation, REF's to this table that are contained within the dump
file will also be invalid.
Action: Drop the offending object table prior to import.
IMP-00072: Warning: The object table's object identifier is invalid.
Cause: The character string representing the table's object identifier could not be
converted to an internal object identifier.
Action: Internal error.
IMP-00073: FILE locator "string" "string" is truncated to "string" "string" in server
character set
Cause: The conversion of the specified directory and name strings for a file
attribute or column from the export server's character set into the import server's
character set exceeded the maximum string lengths allowed within FILE
descriptors. The strings will be truncated to the maximum supported lengths.
Action: Rename the directory aliases and external filenames to match the
truncated names in the specified FILE column or attribute.
IMP-00074: The constraints flagged by ALL_CONSTRAINTS.BAD will break in
2000 A.D.
Cause: Constraints exist in the data base that specify date values without fully
specifying the year. These constraints could break in the year 2000 A.D.
Action: Query ALL_CONSTRAINTS and correct those constraints marked as bad.
IMP-00075: Warning: The nested table may contain partial rows or duplicate rows
Cause: An error occurred inserting data into an outer or inner nested table. If the
error occurred in the outer table, rows are still inserted into the inner tables. If the
error occurred in an inner table, data is still inserted into the outer table and other
inner tables. This can result in duplicate inner table rows or partial logical rows.
Action: Examine the data in the tables. Delete the incorrect rows or drop the entire
table and perform the import again.
IMP-00076: Missing NLS_NCHAR_CHARACTERSET in props$
Cause: No value for NLS_NCHAR_CHARACTERSET in props$.
Action: Contact Worldwide support.
IMP-00077: Could not convert to server national character set's handle
Cause: Internal error.
Action: Contact Worldwide support.
IMP-00078: Cannot translate FILE locator to "string" "string" in server character set
Cause: (1) The current export dump file was generated using Beta-2 of Oracle8.0
AND (2) there was a File that appeared as an an attribute of an ADT within a
table's column AND (3) the character set of the export server's database was
different than the character set of the import server's database AND (4) when the
filename or the aliasname of the File increased in size when it was translated to the
character set of the import server. When all of these conditions are true, translation
of the strings could yield corruption of the data in the column. Rather than
proceeding with the translation, import will leave the character strings in the File
in the old character set.
34-10 Oracle Database Error Messages
Action: After import completes, rename the directory aliases and external
filenames to match the real names used for the target database.
IMP-00079: Warning: National character set data in this table may be incorrect
Cause: Due to a problem in 8.0.2 Export, national character data in NCHAR and
NVARCHAR2 columns was incorrectly assumed to be in the export server's data
base character set and was converted to the export client's data base character set.
This conversion would only be correct if the export server's data base character set
was the same as the export server's national character set and the export client's
data base character set was the same as the export client's national character set.
All other combinations would likely be incorrect. This export dump file was
generated by 8.0.2 Export and the export client and server characater sets did not
fit that criteria.
Action: Examine the national character data. If incorrect, update the data with
correct data.
IMP-00080: Error during character conversion of long column or long command
Cause: During piecewise character conversion of the data in a long column or of a
long command, a fatal conversion error occurred. Either character truncation
occurred or an invalid character set handle was used.
Action: Retry the import with a different character set.
IMP-00081: attempt to free unallocated memory
Cause: An attempt was made to free memory that was not allocated.
Action: Contact Oracle Worldwide Support
IMP-00082: Error during conversion ROWID from string format to internal
Cause: An error occured while attempting to to convert a ROWID from an export
dump file into an internal format.
Action: Report this to Oracle Worldwide Support as an Import internal error.
IMP-00083: dump file does not contain an incremental export
Cause: An incremental import was requested and the dump file specified for the
import command is either a user or table export.
Action: Reissue the command import command but specify the name of a dump
file containing an incremental export.
IMP-00084: attempt to mix incremental import with user or table import
Cause: An incremental import was requested along with the FROMUSER,
TOUSER, or TABLE qualifier. An incremental import cannot be done if any of
these other qualifiers are also specified.
Action: Determine whether you want to do an incremental import, full import,
user import or table import and reissue the import command with the appropriate
qualifiers.
IMP-00085: multiple input files specified for unbounded export file
Cause: You specified multiple file names for the FILE parameter when doing an
import, but the header in the export file indicates that that the export operation
could create only one file. Specifying multiple file names is valid for an import
operation only if the export files were created by an export operation in which the
user specified a non-zero value for the FILESIZE parameter.
IMP-00000 to IMP-00402 34-11
Action: If you believe the export contains multiple files, verify that you have
specified the correct files. If you believe the export should be in only one file then
try the import operation again, but specify only one value for the FILE parameter.
IMP-00086: TOID "string" not found in export file
Cause: Import did not find the type identification specified in the TOID_
NOVALIDATE parameter. The specified type identification does not exist in
export file.
Action: Correct or omit the TOID_NOVALIDATE parameter.
IMP-00087: Problem with internal hash table of schema/table names
Cause: Most likely a problem with allocating memory for the hash table entries.
Action: Contact Oracle Worldwide Support
IMP-00088: Problem importing metadata for index string. Index creation will be
skipped
Cause: Domain indexes import private metadata via anonymous PL/SQL blocks
prior to the CREATE INDEX statement. The execution of one of these PL/SQL
blocks failed. Because the metadata is considered an integral part of the index, the
subsequent CREATE INDEX statement was skipped.
Action: Contact the developer of the index's implementation type. If this is an
Oracle-supplied index (perhaps via a data cartridge), contact Oracle Worldwide
Support.
IMP-00089: Fine grain policy "string" not recreated on table/view "string"
Cause: Import user fails to recreate fine grained policies of the table/view being
imported. To recreate the policy, the user doing the import needs execute privilege
on the package DBMS_RLS for access policies or DBMS_FGA for audit policies.
Action: Ask the database administrator to perform the export/import of this
table/view.
IMP-00090: Unexpected DbmsJava error number at step number while creating string
Cause: The error was returned from a call to a DbmsJava procedure.
Action: Record the accompanying messages and report this as an Import internal
error to customer support.
IMP-00091: Above error occurred on the following function and object: string.
Remaining PL/SQL blocks for this object will be skipped.
Cause: An error occurred while executing a PL/SQL block that implements the
DDL for the named function and procedural object. A procedural object is one
whose DDL is implemented as stored procedures rather than as standard SQL
statements.
Action: Contact Oracle Worldwide Support so they may determine the
development group responsible for the package that failed.
IMP-00092: Java object "string"."string" already exists, cannot be created
Cause: Import failed to create the Java source, class or resource object because it
already exists.
Action: Drop the object type from the target system and retry the operation.
IMP-00093: Inconsistency between dumpfile constraint definition for table string
with columns (string)
34-12 Oracle Database Error Messages
Cause: Import failed to locate a base table for a constraint that was defined in the
dump file and statistics were not imported.
Action: Check to see if the table and constraint exist. If the table and constraint
exist, then report this to Oracle Support Services as an Import internal error.
IMP-00094: Warning: The identifier on the dump file for object type
"string"."string" is invalid
Cause: The character string representing the object type's identifier
* could not be converted.
Action: Contact Oracle Worldwide Support.
IMP-00095: Resumable parameters ignored -- current session not resumable
Cause: Current session is not resumable.
Action: Must specify RESUMABLE=Y to enable resumable session in order for the
RESUMABLE_NAME and RESUMABLE_TIMEOUT parameters to take effect.
IMP-00096: Warning: Skipping table "string"."string" because type synonym
"string"."string" cannot be created
Cause: An error occurred creating a synonym for a type that is used by the
* table.
Action: Examine the import log to determine why the type synonym could
* not be created. If the synonym already existed, but is not
* needed, then drop the synonym and retry the import. If the
* synonym is PUBLIC but the importer does not have the
* CREATE PUBLIC SYNONYM system privilege, then the import must
* be done by someone possessing that privilege, or the importer
* must be granted the privilege.
IMP-00097: STREAMS_CONFIGURATION=Y ignored, only valid with FULL=Y
Cause: STREAMS_CONFIGURATION=Y can only be used
* when FULL=Y is present on the command line
Action: Remove conflicting command arguments
IMP-00098: INTERNAL ERROR: string
Cause: An INTERNAL error occurred.
Action: Contact Oracle Worldwide Support.
IMP-00099: Warning: The typeid in the dump file for object type "string"."string" is
invalid
Cause: The character string representing the object type's identifier
* could not be converted.
Action: Contact Oracle Worldwide Support.
IMP-00400: Warning: Object type "string"."string" already exists with a different
typeid
Cause: An object type could not be created because it already existed on the
* target system, but with a different typeid
IMP-00000 to IMP-00402 34-13
Action: Drop the object type from the target system and retry the operation.
IMP-00401: dump file "string" may be an Data Pump export dump file
Cause: A dump file was specified for an import operation which appears to have
been created using the Data Pump export utility. These dump files cannot be
processed by the original import utility.
Action: Try using the Data Pump import utility to process this dump file.
IMP-00402: Invalid parameter "string" with data_only mode
Cause: Parameter provided along data_only is invalid.
Action: Remove the invalid parameter from command line.


SQL*Loader-00100 to SQL*Loader-03120 5 3
SQL*Loader-00100: Syntax error on command-line
Cause: Possible causes for this error include: placing a positional argument after
keyword arguments, misspelling a keyword, not balancing parentheses or quotes,
or leaving space between the operator, '=', and an argument.
Action: Check the command syntax and the spelling, then retry.
SQL*Loader-00101: Invalid argument for username/password
Cause: The username/password argument specified on the command line was
not recognized. Another argument (not identified by a keyword) could be in the
position where username/password is expected.
Action: Check the format of the username/password argument, which is the first
argument on the command line, if arguments are given without keywords.
SQL*Loader-00102: Invalid control file name on command line
Cause: d an overflow of the output buffer.
Action: Check the spelling and position of the arguments on the command line.
SQL*Loader-00103: Invalid log file name on command line
Cause: The log file name specified on the command line was not recognized. It
could be misspelled, or another argument (not identified by a keyword) could be
in its place. Another possible cause is that the specified file name caused an
overflow of the output buffer.
Action: Check the spelling and position of the arguments on the command line.
SQL*Loader-00104: Invalid bad file name on command line
Cause: The bad file name specified on the command line was not recognized. It
could be misspelled, or another argument (not identified by a keyword) could be
in its place. Another possible cause is that the specified file name caused an
overflow of the output buffer.
Action: Correct it.
SQL*Loader-00105: Invalid data file name on command line
Cause: The datafile name specified on the command line was not recognized. It
could be misspelled, or another argument (not identified by a keyword) could be
in its place. Another possible cause is that the specified file name caused an
overflow of the output buffer.
Action: Check the spelling and position of the arguments on the command line.
SQL*Loader-00106: Invalid discard file name on command line
35-2 Oracle Database Error Messages
Cause: is that the specified file name caused an overflow of the output buffer.
Action: Check the spelling and position of the arguments on the command line.
SQL*Loader-00107: Invalid maximum number of discards
Cause: The argument's value is inappropriate, or another argument (not identified
by a keyword) is in its place.
Action: Check the command line and retry.
SQL*Loader-00108: Invalid number of logical records to load
Cause: The argument's value is inappropriate, or another argument (not identified
by a keyword) is in its place.
Action: Check the command line and retry.
SQL*Loader-00109: Invalid number of logical records to skip
Cause: The argument's value is inappropriate, or another argument (not identified
by a keyword) is in its place.
Action: Check the command line and retry.
SQL*Loader-00110: Invalid maximum number of errors
Cause: The argument's value is inappropriate, or another argument (not identified
by a keyword) is in its place.
Action: Check the command line and retry.
SQL*Loader-00111: Invalid number of rows for bind array or data saves
Cause: The argument's value is inappropriate, or another argument (not identified
by a keyword) is in its place.
Action: Check the command line and retry.
SQL*Loader-00112: Invalid maximum bind array size
Cause: The argument's value is inappropriate, or another argument (not identified
by a keyword) is in its place.
Action: Check the command line and retry.
SQL*Loader-00113: Invalid silent mode option
Cause: The only valid options for the SILENT command-line argument are ALL,
ERROR, FEEDBACK, or HEADER. The argument could be misspelled, or another
argument (not identified by a keyword) could be in its place.
Action: Check the command line and retry.
SQL*Loader-00114: Error in OPTIONS statement
Cause: Command line options specified in the SQL*Loader control file with the
OPTIONS clause were found to be incorrect.
Action: Check the format of the OPTIONS clause in the SQL*Loader control file.
SQL*Loader-00115: Invalid direct path option
Cause: The only valid options for the DIRECT command-line argument are TRUE
or FALSE. The argument could be misspelled, or another argument (not identified
by a keyword) could be in its place.
Action: Check the command line and retry.
SQL*Loader-00116: Error prompting for password
Cause: An internal error has occurred.
SQL*Loader-00100 to SQL*Loader-03120 35-3
Action: Contact customer support.
SQL*Loader-00118: Invalid parallel load option
Cause: The command-line argument used for the parallel load is incorrect.
Action: Use only TRUE or FALSE as the value for the parallel load option.
SQL*Loader-00119: Invalid parallel file (data file) name on command line
Cause: d an overflow of the output buffer.
Action: Check the command line argument and retry the operation.
SQL*Loader-00120: Invalid _synchro option string
Cause: The command-line argument _synchro is incorrect.
Action: Use only one of the allowed modes: see ulminv[].
SQL*Loader-00121: Invalid skip_unusable_indexes option
Cause: The command line argument for skip_unusable_indexes is incorrect.
Action: Use only TRUE or FALSE as the value for the skip_unusable_indexes
option.
SQL*Loader-00122: Invalid skip_index_maintenance option
Cause: The command line argument for skip_index_maintenance is incorrect.
Action: Use only true or falseas the value for the skip_index_maintenance option.
(Note: only on direct loads!)
SQL*Loader-00123: specified value for bindsize(number) less than readsize(number)
Cause: The command line argument specified for bindsize was less than the value
of readsize.
Action: No action is required. SQL*Loader automatically adjusts the value of
bindsize to equal the value of readsize.
SQL*Loader-00124: specified value for readsize(number) less than bindsize(number)
Cause: The command line argument specified for readsize was less than the value
of bindsize.
Action: No action is required. SQL*Loader automatically adjusts the value of
readsize to equal the value of bindsize.
SQL*Loader-00125: specified value for readsize(number) less than max_record_
size(number)
Cause: The command line argument specified for readsize was less than the value
of max_record_size.
Action: No action is required. SQL*Loader automatically adjusts the value of
readsize to equal the value of max_record_size.
SQL*Loader-00126: Invalid read size
Cause: The argument's value is inappropriate, or another argument (not identified
by a keyword) is in its place.
Action: Check the command line and retry.
SQL*Loader-00127: Invalid maximum record size
Cause: The argument's value is inappropriate, or another argument (not identified
by a keyword) is in its place.
Action: Check the command line and retry.
35-4 Oracle Database Error Messages
SQL*Loader-00128: unable to begin a session
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.
SQL*Loader-00129: Invalid number of rows for direct path column array
Cause: The argument's value is inappropriate
Action: Check the command line and retry.
SQL*Loader-00130: Invalid direct path stream size
Cause: The argument's value is inappropriate
Action: Check the command line and retry.
SQL*Loader-00131: Invalid multithreading option
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.
Action: Check the command line and retry.
SQL*Loader-00132: invalid argument for external table option
Cause: The command line argument specified for external_tables was not TRUE
or FALSE
Action: Check the command line and retry.
SQL*Loader-00133: Can't specify both direct path and external tables
Cause: Both options for direct path and exrernal 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.
SQL*Loader-00134: invalid option specified for EXTERNAL_TABLE parameter
Cause: An invalid value was specified for the EXTERNAL_TABLE parameter.
Action: Specify one of the following values. NOT_USED disables use of external
tables. GENERATE_ONLY generates the SQL statements that will use external
tables to load the data. EXECUTE both generates the SQL statements and then
executes them.
SQL*Loader-00135: Invalid argument for RESUMABLE
Cause: The command line argument specified for RESUMABLE was not TRUE or
FALSE.
Action: Check the command line and retry.
SQL*Loader-00136: Invalid argument for RESUMABLE_NAME
Cause: The command line argument specified for RESUMABLE_NAME was not a
valid string.
Action: Check the command line and retry.
SQL*Loader-00137: Invalid value for RESUMABLE_TIMEOUT
Cause: The command line argument specified for RESUMABLE_TIMEOUT was
not a valid positive integer.
Action: Check the command line and retry.
SQL*Loader-00138: Invalid value for DATE_CACHE
SQL*Loader-00100 to SQL*Loader-03120 35-5
Cause: The command line argument specified for DATE_CACHE was not a valid
positive integer.
Action: Check the command line and retry.
SQL*Loader-00144: Conflicting load methods: string/string specified.
Cause: External table mode and direct path mode were both specified.
Action: Specify only one load method.
SQL*Loader-00145: Invalid value for NO_INDEX_ERRORS
Cause: The command line argument specified was not a valid boolean.
Action: Check the command line and retry.
SQL*Loader-00146: Invalid value for PARTITION_MEMORY
Cause: The command line argument specified was not -1, 0, or positive.
Action: Check the command line and retry.
SQL*Loader-00147: Warning: The NO_INDEX_ERRORS parameter is ignored for
direct path parallel loads.
Cause: The NO_INDEX_ERRORS parameter was specified for a parallel load.
Action: Do not use the NO_INDEX_ERRORS parameter for parallel loads.
SQL*Loader-00148: Invalid value for the TABLE parameter.
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.
Action: Check the command line and retry.
SQL*Loader-00149: Control file cannot be specified with the TABLE parameter.
Cause: A control file was specified along with the TABLE parameter.
Action: Check the command line and retry. If you are doing an express mode
load, omit the control file. If you are not doing an express mode load, omit the
TABLE parameter.
SQL*Loader-00174: conflicting values for PARALLEL and DEGREE_OF_
PARALLELISM parameters
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.
Action: Verify the values for PARALLEL and DEGREE_OF_PARALLELISM.
SQL*Loader-00175: invalid number of Direct NFS (dNFS) read buffers
Cause: The argument's value was inappropriate.
Action: Check the command line and retry.
SQL*Loader-00176: Invalid value for the DATE_FORMAT parameter.
Cause: The command line argument specified for the DATE_FORMAT parameter
was not a valid string.
Action: Check the command line and retry.
35-6 Oracle Database Error Messages
SQL*Loader-00177: The DATE_FORMAT parameter can only be specified with the
TABLE parameter.
Cause: A control file was specified along with the DATE_FORMAT parameter.
Action: Check the command line and retry. If you are doing an express mode
load, omit the control file. If you are not doing an express mode load, omit the
DATE_FORMAT parameter.
SQL*Loader-00178: Invalid value for the TERMINATED_BY parameter.
Cause: The command line argument specified for the TERMINATED_BY
parameter was not a valid string.
Action: Check the command line and retry.
SQL*Loader-00179: Invalid hexadecimal value for the TERMINATED_BY
parameter.
Cause: The command line argument specified for the TERMINATED_BY
parameter was not a valid hexadecimal string.
Action: Check the command line and retry.
SQL*Loader-00180: Invalid hexadecimal value for the table-level NULLIF
parameter.
Cause: The command line argument specified for the table-level NULLIF
parameter was not a valid hexadecimal string.
Action: Check the command line and retry.
SQL*Loader-00181: The TERMINATED_BY parameter cannot be specified without
the TABLE parameter.
Cause: The TERMINATED_BY parameter was specified without the TABLE
parameter.
Action: Check the command line and retry. If you are doing an express mode
load, include the TABLE parameter and omit the control file. If you are not doing
an express mode load, omit the TERMINATED_BY parameter.
SQL*Loader-00182: Invalid value for the ENCLOSED_BY parameter.
Cause: The command line argument specified for the ENCLOSED_BY parameter
was not a valid string.
Action: Check the command line and retry.
SQL*Loader-00183: invalid hexadecimal value for the ENCLOSED_BY parameter:
string
Cause: The command line argument specified for the ENCLOSED_BY parameter
was not a valid hexadecimal string.
Action: Check the command line and retry.
SQL*Loader-00184: The ENCLOSED_BY parameter cannot be specified with the
OPTIONALLY_ENCLOSED_BY parameter.
Cause: Both the ENCLOSED_BY parameter and the OPTIONALLY_ENCLOSED_
BY parameter were specified.
Action: Check the command line and retry. Specify only the ENCLOSED_BY
parameter or the OPTIONALLY_ENCLOSED_BY parameter.
SQL*Loader-00185: The ENCLOSED_BY parameter cannot be specified without the
TABLE parameter.
SQL*Loader-00100 to SQL*Loader-03120 35-7
Cause: The ENCLOSED_BY parameter was specified without the TABLE
parameter.
Action: Check the command line and retry. If you are doing an express mode
load, include the TABLE parameter and omit the control file. If you are not doing
an express mode load, omit the ENCLOSED_BY parameter.
SQL*Loader-00186: Invalid value for the OPTIONALLY_ENCLOSED_BY
parameter.
Cause: The command line argument specified for the OPTIONALLY_
ENCLOSED_BY parameter was not a valid string.
Action: Check the command line and retry.
SQL*Loader-00187: invalid hexadecimal value for the OPTIONALLY_ENCLOSED_
BY parameter: string
Cause: The command line argument specified for the OPTIONALLY_
ENCLOSED_BY parameter was not a valid hexadecimal string.
Action: Check the command line and retry.
SQL*Loader-00188: The OPTIONALLY_ENCLOSED_BY parameter cannot be
specified with the ENCLOSED_BY parameter.
Cause: Both the OPTIONALLY_ENCLOSED_BY parameter and the ENCLOSED_
BY parameter were specified.
Action: Check the command line and retry. Specify only the OPTIONALLY_
ENCLOSED_BY parameter or the ENCLOSED_BY parameter.
SQL*Loader-00189: The OPTIONALLY_ENCLOSED_BY parameter cannot be
specified without the TABLE parameter.
Cause: The OPTIONALLY_ENCLOSED_BY parameter was specified without the
TABLE parameter.
Action: Check the command line and retry. If you are doing an express mode
load, include the TABLE parameter and omit the control file. If you are not doing
an express mode load, omit the OPTIONALLY_ENCLOSED_BY parameter.
SQL*Loader-00190: Invalid value for the CHARACTERSET parameter.
Cause: The command line argument specified for the CHARACTERSET
parameter was not a valid string.
Action: Check the command line and retry.
SQL*Loader-00191: The CHARACTERSET parameter can only be specified with
the TABLE parameter.
Cause: A control file was specified along with the CHARACTERSET parameter.
Action: Check the command line and retry. If you are doing an express mode
load, omit the control file. If you are not doing an express mode load, omit the
CHARACTERSET parameter.
SQL*Loader-00192: The CHARACTERSET parameter cannot be specified without
the TABLE parameter.
Cause: The CHARACTERSET parameter was specified without the TABLE
parameter.
Action: Check the command line and retry. If you are doing an express mode
load, include the TABLE parameter and omit the control file. If you are not doing
an express mode load, omit the CHARACTERSET parameter.
35-8 Oracle Database Error Messages
SQL*Loader-00193: Invalid value for the DEGREE_OF_PARALLELISM parameter.
Cause: The command line argument specified for the DEGREE_OF_
PARALLELISM parameter was not a valid string.
Action: Check the command line and retry.
SQL*Loader-00194: Option string specified and ignored for string path load.
Cause: An option was specified that is not supported for conventional path or
direct path.
Action: Do not specify the unsupported option or do not use conventional path or
direct path load.
SQL*Loader-00195: Invalid value for the TRIM parameter.
Cause: The command line argument specified for the TRIM parameter was not a
valid string.
Action: Check the command line and retry.
SQL*Loader-00196: Invalid value for the CSV parameter.
Cause: The command line argument specified for the CSV parameter was not a
valid string.
Action: Check the command line and retry.
SQL*Loader-00197: Invalid value for the TIMESTAMP_FORMAT parameter.
Cause: The command line argument specified for the TIMESTAMP_FORMAT
parameter was not a valid string.
Action: Check the command line and retry.
SQL*Loader-00198: The TIMESTAMP_FORMAT parameter can only be specified
with the TABLE parameter.
Cause: A control file was specified along with the TIMESTAMP_FORMAT
parameter.
Action: Check the command line and retry. If you are doing an express mode
load, omit the control file. If you are not doing an express mode load, omit the
TIMESTAMP_FORMAT parameter.
SQL*Loader-00199: Invalid value for the NULLIF parameter.
Cause: The command line argument specified for the NULLIF parameter was not
a valid string.
Action: Check the command line and retry.
SQL*Loader-00200: FORMAT clause should not be present - flat data files only
Cause: SQL/DS FORMAT clause is not supported.
Action: Remove the FORMAT command from the SQL*Loader control file or
SQL*Loader-00201: There is an invalid value for the CSV clause.
Cause: The control file clause specified for CSV was neither CSV WITH
EMBEDDED or CSV WITHOUT EMBEDDED.
Action: Check the control file CSV clause syntax and retry.
SQL*Loader-00202: shift-based character sets not supported with CSV format files
with embedded record terminators
Cause: A CSV format file with embedded record terminators was specified with a
shift-based character set.
SQL*Loader-00100 to SQL*Loader-03120 35-9
Action: Either use a nonshift-based character set or do not use CSV format files
with embedded record terminators.
SQL*Loader-00203: The NULLIF parameter can only be specified with the TABLE
parameter.
Cause: A control file was specified along with the NULLIF parameter.
Action: Check the command line and retry. If you are doing an express mode
load, omit the control file. If you are not doing an express mode load, omit the
NULLIF parameter.
SQL*Loader-00204: Invalid value for the FIELD_NAMES 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.
Action: Check the command line and retry.
SQL*Loader-00205: The FIELD_NAMES parameter can only be specified with the
TABLE parameter.
Cause: A control file was specified along with the FIELD_NAMES parameter.
Action: Check the command line and retry. If you are doing an express mode
load, omit the control file. If you are not doing an express mode load, omit the
FIELD_NAMES parameter.
SQL*Loader-00206: Empty field name for field number in the FIELD NAMES record
in data file
Cause: A field name in the FIELD NAMES record was empty.
Action: Specify a valid field name and retry the operation.
SQL*Loader-00207: Missing one or more field names in the FIELD NAMES record
in the data file. Found number fields, there should be number fields.
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.
Action: Include all field names in the data file and retry the operation.
SQL*Loader-00208: Error on the FIELD NAMES record for table string, field
stringstringstring was not found in the control file.
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.
Action: Check the listed field and fix it. Then retry the operation.
SQL*Loader-00209: error processing the FIELD NAMES record in data file string.
Cause: An error occurred while processing the FIELD NAMES record for the data
file.
Action: See messages that preceed this one for more details. Fix the error and
retry the operation.
SQL*Loader-00210: first data file is empty, cannot process the FIELD NAMES
record
Cause: The data file listed in the next message was empty. Therefore, the FIELD
NAMES FIRST FILE directive could not be processed.
Action: Check the listed data file and fix it. Then retry the operation.
35-10 Oracle Database Error Messages
SQL*Loader-00211: Field name stringstringstring in the FIELD NAMES record in
the data file is too long.
Cause: The field name exceeded the maximum of 30 characters.
Action: Specify at most 30 characters.
SQL*Loader-00212: The field level ENCLOSED BY clause is not allowed with the
CSV WITH EMBEDDED clause.
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.
Action: Either remove the field level ENCLOSED BY clause, or, if the data file
does not contain embedded record terminators, change CSV WITH EMBEDDED
to CSV WITHOUT EMBEDDED.
SQL*Loader-00213: Invalid value for the table parameter
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.
Action: Check the spelling and position of the arguments on the command line.
SQL*Loader-00214: Invalid value for the table name in the INTO TABLE clause
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.
Action: Check the name and try again with a valid table name.
SQL*Loader-00215: Invalid data file name in INFILE statement
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.
Action: Check the spelling and length of the data file specification.
SQL*Loader-00216: Invalid bad file name in BADFILE statement
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.
Action: Check the spelling and length of the bad file specification.
SQL*Loader-00217: Invalid discard file name in DISCARDFILE statement
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.
Action: Check the spelling and length of the discard file specification.
SQL*Loader-00218: Specified command-line parameter string ignored since not an
express mode load.
Cause: A command-line parameter was specified that is supported only for
express mode and not for loads which use a control file.
SQL*Loader-00100 to SQL*Loader-03120 35-11
Action: Omit the option which is not supported if the option is not needed or use
the control file syntax for the option. For example, use the CSV WITH
EMBEDDED or CSV WITHOUT EMBEDDED control file syntax.
SQL*Loader-00248: multiple string format masks specified at table level for table
string
Cause: Multiple format masks were specified for the listed datetime data type at
the table level for the listed table.
Action: Remove one of the mask specifications and try the operation again.
SQL*Loader-00249: Unexpected error occurred while processing datetime format
mask (string).
Cause: An unexpected error occurred while processing the datetime format mask.
Action: Check the mask and try the operation again with a correct mask. If the
problem still occurs, contact Oracle Support Services.
SQL*Loader-00250: Work data sets are not used by SQL*Loader
Cause: The SQL*Loader control file contains a WRKDDN statement. SQL*Loader
ignores this clause.
Action: No action required. This is an informational message.
SQL*Loader-00251: Sort devices are not used by SQL*Loader
Cause: The SQL*Loader control file contains a SORTDEVT statement.
SQL*Loader ignores this clause.
Action: No action required. This is an informational message.
SQL*Loader-00252: Sort data sets are not used by SQL*Loader
Cause: The SQL*Loader control file contains a SORTNUM statement. SQL*Loader
ignores this clause.
Action: No action required. This is an informational message.
SQL*Loader-00253: DB2 partition number has no significance -- ignored
Cause: The SQL*Loader control file contains a PART statement. SQL*Loader
ignores this clause.
Action: No action required. This is an informational message.
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.
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-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.
35-12 Oracle Database Error Messages
Action: Specify a direct path load with DIRECT=TRUE on the command line,
remove the statement from the SQL*Loader control file, or
SQL*Loader-00257: TERMINATED BY EOF option not valid with ENCLOSED BY
option
Cause: A field description in the SQL*Loader control file contains both the
TERMINATED BY EOF and the ENCLOSED BY options. These options are
mutually exclusive.
Action: Remove either or both of the clauses.
SQL*Loader-00258: Maximum number of SORTED INDEXES (number) exceeded on
table string
Cause: There are too many indexes in the SORTED INDEX clause. The message
displays the maximum number that are permitted.
Action: Reduce the number of indexes specified in the SORTED INDEX clause or
use the conventional path load instead of the direct path load.
SQL*Loader-00259: Could not escalate DDL share lock to exclusive on table string
Cause: This error occurs when another user has a parse lock on the table, for
example, when another user is doing a select on the table. The parse lock should
clear momentarily.
Action: Give the parse lock a chance to clear and then retry or else use the
conventional path load.
SQL*Loader-00260: TERMINATED BY EOF option available only with LOBFILE
option
Cause: The TERMINATED BY EOF option can be used only when describing data
to be loaded from a LOBFILE. It cannot be specified at the table level and it cannot
be for data in "regular" 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-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 control file.
SQL*Loader-00262: PIECED keyword (on column string) allowed only when path is
direct
Cause: The PIECED keyword cannot be used in a conventional path load.
Action: Remove the PIECED keyword or use the direct path load.
SQL*Loader-00263: PIECED column string must be last specified column in table
string
Cause: A column that is not the last column was specified as PIECED.
Action: Remove the PIECED keyword or place the column last.
SQL*Loader-00264: File mode token string parsed but ignored
Cause: An obsolete file mode token was used in the SQL*Loader control file. As of
Release 1.1 of SQL*Loader, the file-processing options string is used to control file
SQL*Loader-00100 to SQL*Loader-03120 35-13
processing, rather than keywords like STREAM, RECORD, FIXED, and
VARIABLE.
Action: No action required. This message is informational. Removing the obsolete
keywords will eliminate the message without changing the way in which the
datafile is processed.
SQL*Loader-00265: Unable to get default character set name.
Cause: SQL*Loader was unable to locate the default character set name for the
environment.
Action: Supply a character set name with the CHARACTERSET keyword.
SQL*Loader-00266: Unable to locate character set handle for string.
Cause: SQL*Loader could not find the character set handle for the named
character set.
Action: Correct the character set name.
SQL*Loader-00267: Control file must be first data file.
Cause: The SQL*Loader control file is specified as containing data using the
INFILE "*" clause, but other datafiles were named first.
Action: Move the INFILE "*" clause so that it is the first datafile declared in the
SQL*Loader control file.
SQL*Loader-00268: UNRECOVERABLE keyword may be used only in direct path.
Cause: The UNRECOVERABLE keyword can only be specified in the direct path
load.
Action: Use the direct path load or remove the keyword. (Conventional path
loads are always recoverable).
SQL*Loader-00269: Null string not allowed as clause comparison text.
Cause: A clause is being compared to a null string.
Action: Modify the clause to compare to at least one character.
SQL*Loader-00270: TERMINATED BY EOF valid only for CHAR or RAW datatypes
Cause: A field description in the SQL*Loader control file used the TERMINATED
BY EOF option when the field was not a RAW or CHAR datatype.
Action: Modify the SQL*Loader control file to either remove the TERMINATED
BY EOF clause or change the datatype for the field to be CHAR or RAW.
SQL*Loader-00271: Not a Parallel load. Table level OPTIONS statement ignored.
Cause: A table-level OPTIONS statement was specified for a non-parallel load.
Action: Remove the OPTIONS statement from the SQL*Loader control file.
SQL*Loader-00272: Table level OPTIONS statement ignored.
Cause: In the parallel load option, the file specified on the command line
overrides the file specified in the SQL*Loader control file.
Action: Remove the OPTIONS statement from the SQL*Loader control file.
SQL*Loader-00273: READBUFFERS may be used only in direct path.
Cause: The READBUFFERS specification was not entered as part of a direct path.
Action: Use the direct path or remove the READBUFFERS specification from the
SQL*Loader control file.
35-14 Oracle Database Error Messages
SQL*Loader-00274: At least 2 read buffers have to be specified.
Cause: Fewer than 2 read buffers have been specified.
Action: Specify at least 2 read buffers in the READBUFFERS statement, in the
SQL*Loader control file.
SQL*Loader-00275: Data is in control file but "INFILE *" has not been specified.
Cause: The INFILE specification was not entered in the SQL*Loader control file.
Action: If data in the SQL*Loader control file is to be read, specify INFILE * in the
SQL*Loader control file.
SQL*Loader-00276: Local storage option overrides global storage.
Cause: A storage clause has been specified in the table level options statement
and also in the global options statement.
Action: This is only a warning message. Table level options take precedence over
global options. Drop the table level options statement if this is not the intent.
SQL*Loader-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.
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-00279: Only APPEND mode allowed when parallel load specified.
Cause: INSERT, REPLACE, or TRUNCATE mode was used in a parallel load
specification.
Action: Change the SQL*Loader control file to use the APPEND keyword and
re-invoke the parallel loader.
SQL*Loader-00280: table string is a temporary table
Cause: The sqlldr utility does not load temporary tables. Note that if sqlldr did
allow loading of temporary tables, the data would disappear after the load
completed.
Action: Load the data into a non-temporary table.
SQL*Loader-00281: Warning: ROWS parameter ignored in parallel mode.
Cause: Specifying save points using the ROWS parameter is not supported for
parallel loads.
Action: Remove the ROWS parameter from the command-line arguments or
specify a non-parallel direct load to have save points performed.
SQL*Loader-00282: Unable to locate character set handle for character set ID
(number).
Cause: SQL*Loader could not find the character set handle for the given character
set ID.
Action: The character set ID was obtained from the database server, the
SQL*Loader client does not have knowledge of the given character set ID. Possible
mis-match of NLS data on the client and server side.
SQL*Loader-00100 to SQL*Loader-03120 35-15
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 control file has a different record format, then you need to copy the
data into a separate file and use that file's name in the INFILE clause.
SQL*Loader-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/BADDN/DISCARDFILE/DISCARDDN/DISCARDS.
SQL*Loader-00285: string 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-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-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-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-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.
35-16 Oracle Database Error Messages
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-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-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-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-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-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-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")".
SQL*Loader-00100 to SQL*Loader-03120 35-17
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-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-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-00299: Virtual column string in table string.string cannot be loaded.
Cause: Virtual columns were specified in the control file.
Action: Virtual columns cannot be specified in the control file. Remove the virtual
column from the SQL*Loader control file.
SQL*Loader-00300: error while attempting to enable tracing
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.
Action: No action required.
SQL*Loader-00301: string for TERMINATED BY or ENCLOSED BY clause is longer
than number bytes
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.
Action: Use shorter strings for the TERMINATED BY and ENCLOSED BY
clauses.
SQL*Loader-00303: Non-hex character encountered where hex char expected
Cause: A non-hex character was found in a hexadecimal string.
Action: Change it to the intended hexadecimal character.
SQL*Loader-00304: Illegal combination of non-alphanumeric characters
Cause: The SQL*Loader control file contains a combination of non-alphanumeric
characters that SQL*Loader does not recognize. For example, the combination != is
recognized as "not equal", but the combination =! is not valid.
Action: Remove the unrecognized characters from the control file.
SQL*Loader-00305: More than one end of file character encountered
Cause: The file contains multiple end-of-file marks.
Action: Remove the excess end-of-file characters.
SQL*Loader-00306: Token longer than max allowable length of number chars
35-18 Oracle Database Error Messages
Cause: The SQL*Loader control file contains a single word or combination of
characters (a token) that is longer than the maximum permissible value. The
maximum possible value is shown. This error could result from missing spaces, so
that multiple tokens are joined.
Action: Check that the proper SQL*Loader control file is being executed Separate
tokens, if joined, or shorten the token.
SQL*Loader-00307: Warning: conflicting lengths number and number specified for
column string table string
Cause: The SQL*Loader control file specifies two different lengths for the named
column. There are three ways to specify the length of a field: --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-00308: string 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-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-00310: Interval partition values of table string must be in double
quotes.
Cause: A string specified for interval partitioning was found that was not quoted
or in single quotes.
Action: Use double quotes for the interval partitioning values string, rather than
single quotes.
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-00100 to SQL*Loader-03120 35-19
SQL*Loader-00401: End field position number must be greater than or equal to start
number
Cause: The named field contains a (start:end) clause in which end is less than
start.
Action: Modify the clause so that end is greater than or equal to start.
SQL*Loader-00402: Unable to determine length of column string from specification
Cause: The specified datatype does not have an implied length (for example, a
numeric external or RAW datatype), it is not specified with delimiters, no length
was specified, and a length cannot be determined from a POSITION clause.
Action: If a POSITION clause is specified, adding an end location to it produces a
length specification. This clause then has the form POSITION(start:end) A length
can also specified after the datatype, as in INTEGER EXTERNAL (6) Finally, the
field could be specified with delimiters, or the datatype changed to one that has an
implied length.
SQL*Loader-00403: Referenced column string not present in table string.
Cause: The named column is not present in the given table.
Action: Correct the column name or table name.
SQL*Loader-00404: Column string present more than once in string's INTO TABLE
block.
Cause: The named column is specified more than once in a single INTO TABLE
statement.
Action: Remove the extraneous column specification.
SQL*Loader-00405: Need termination delim with optional enclosure delim: column
string table string
Cause: The named column was specified with an optional enclosure delimiter, but
no termination delimiter. Enclosure delimiters can only be optional when
termination delimiters are present.
Action: Specify a termination delimiter or make the enclosure delimiters
non-optional.
SQL*Loader-00406: If data is all generated, number to load cannot be ALL
Cause: When only generated data is loaded, a number to load must be given so
SQL*Loader knows when to stop.
Action: Specify a number to load.
SQL*Loader-00407: If data is all generated, number to skip is meaningless
Cause: When all data is generated, no file is read, and there are no records to skip.
Action: Remove the number to skip.
SQL*Loader-00408: Physical record stack overflow
Cause: An internal error has occurred.
Action: Contact customer support.
SQL*Loader-00409: Number to skip must be table-level, not load-level on
continued loads
Cause: The SKIP parameter was specified on the command line or in the
OPTIONS statement, but the load was specified as continued with CONTINUE_
LOAD. When a multiple-table direct load is interrupted, it is possible that a
35-20 Oracle Database Error Messages
different number of records were loaded into each table. As a result, the number of
records to skip must be specified for each table when continuing the load. In this
case, the load is specified as continued with the CONTINUE_LOAD statement,
and the number of records to skip is given in each INTO TABLE statement. See
also messages 410 and 411 for more information.
Action: Check the log file to determine the appropriate number of records to skip
for each table and specify this number in the INTO TABLE statement for each table
in a continued load or with the command-line SKIP parameter in a standard load.
SQL*Loader-00410: Number to skip must be load-level, not table-level
Cause: A SKIP clause was found in the INTO TABLE statement of a standard
(non-continued) load. In a standard load, specified with LOAD DATA, it is not
possible to skip a different number of records for each table. The number of
records to skip must be specified for the entire load by using the SKIP parameter
on the command line or in the OPTIONS clause. If table-level skip is required,
because a different number of records were loaded into each table (only possible
for a multiple- table direct load), then specify a continued load with the
CONTINUE_LOAD statement. See also messages 409 and 411 for more
information.
Action: If the load was not a multiple-table, direct path load, then move the SKIP
clause from the INTO TABLE statements to the command line or to the OPTIONS
clause. Otherwise, specify the load as continued with CONTINUE_LOAD.
SQL*Loader-00411: Only a direct path load may be continued
Cause: The load is specified with CONTINUE_LOAD, but DIRECT=FALSE.
CONTINUE_LOAD is only possible for a direct path load and is only necessary
for a multiple-table, direct path load when a different number of records have
been loaded into each table. See also messages 409 and 410 for more information.
Action: If CONTINUE_LOAD is necessary, specify a direct load and put the
number of records to skip in each INTO TABLE statement. Otherwise, use the
command line or OPTIONS clause to specify the number of records to skip and
use LOAD DATA instead of CONTINUE_LOAD.
SQL*Loader-00412: More columns specified for table string than the maximum
(number)
Cause: More columns were specified for the table than the maximum number
allowed by the database.
Action: Remove the extraneous columns.
SQL*Loader-00413: NULLIF or DEFAULTIF clause specified for filler field string in
table string.
Cause: A NULLIF or DEFAULTIF clause was specified in the SQL*Loader control
file for the named filler field. These options cannot be specified for filler fields.
Action: Remove the NULLIF or DEFAULTIF clause from the field definition.
SQL*Loader-00414: no columns to load for table string
Cause: There were no fields in the data file to be loaded for the table. Probably all
fields were identified as FILLER fields.
Action: Verify that the FILLER attribute was set correctly for the fields.
SQL*Loader-00415: column string in table string cannot use and be the object of an
SDF or LOBFILE
SQL*Loader-00100 to SQL*Loader-03120 35-21
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.
Action: Verify that the SDF and LOBFILE clauses in the SQL*Loader control file
name the correct fields. Also verify that the SDF and LOBFILE clauses are
specified for the correct field.
SQL*Loader-00416: SDF clause for field string in table string references a non
existent field.
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.
Action: Verify the definition of the secondary data file to make sure it identifies
the intended field.
SQL*Loader-00417: SQL string (on column string) not allowed in direct path.
Cause: Because the direct path bypasses SQL processing, the SQL string cannot be
used.
Action: Remove the SQL string or use the conventional path.
SQL*Loader-00418: Bad datafile datatype for column string
Cause: The datatype in the data file specified for the column cannot be used to
load the column. This message is often displayed for columns that need to be
loaded with special features. For example, BFILE columns can only be loaded via
the BFILE directive in the control file; same goes for REF fields. in the SQL*Loader
control file. Similarly, REF columns can only be loaded with theREF datatype in
the SQL*Loader control file.
Action: Determine the datatype of the column in the database check the
documentation for the correct mechanisms to use to load columns of that type.
SQL*Loader-00419: input datatype for column string is not supported when loading
varrays
Cause: The datatype in the SQL*Loader control file for the column is cannot be
used to load data in a varray.
Action: Use a different datatype.
SQL*Loader-00420: unsupported datatype conversion requested for column string
in table string
Cause: The colummn needs to have it's data converted to another datatype before
loading the data. The required conversion cannot be done by sqlldr.
Action: Verify that the correct datatype was specified for the column.
SQL*Loader-00421: error converting data
Cause: This message can be displayed as one of the reasons for rejecting a row.
The sqlldr utility was attempting to convert data for the column from its datatype
in the data file 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 data file so that it can be converted.
SQL*Loader-00422: constant element count of number for column string is greater
than maximum, number
Cause: The number of elements specified for a varray column in a table is greater
than the maximum number of elements allowed for the type of the varray column.
35-22 Oracle Database Error Messages
Action: Increase the number of elements allowed for the type or remove
unwanted elements from the data file.
SQL*Loader-00423: element count is greater than maximum allowed for the column
Cause: When building a varray from the data file, SQL*Loader encountered more
varray elements than are allowed for the column.
Action: The previous error messages contain the name of the column and the row
number containing the bad data.
SQL*Loader-00424: table string makes illegal reference to collection field string
Cause: A WHEN, OID or SID clause for the table refers to a field declared inside
of a collection.
Action: Move the data containing the value for a SID or OID clause outside of the
collection definition.
SQL*Loader-00425: column string makes illegal reference to collection field string
Cause: A clause, such as NULLIF or BFILE clause, for the column refers to a field
declared inside of a collection.
Action: Move the data containing the value for a SID or OID clause outside of the
collection definition.
SQL*Loader-00426: count of elements in VARRAY string comes after the data for
the varray
Cause: The COUNT clause for a VARRAY field indicates that the count of
elements in the varray is stored in another data field. However, that data field
comes after the varray data in the 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.
Action: Move the count field to be before the collection data in the data file.
SQL*Loader-00427: a field condition references a non-scalar field or a LOB field
string
Cause: The field condition is referencing a field which is either a nested table,
varray, column object, LOB or BILE field. These fields with these typescannot be
references by other field.
Action: Correct the NULLIF, DEFAULTIF, or WHEN clauses to reference only
non-LOB scalar data fields.
SQL*Loader-00428: count for field string not stored in character or integer field
Cause: The count clause for a field references another field, but the referenced
field is not a character or integer datatype.
Action: Modify the count field so that it reference a a data field that has the count
in an integere or character format.
SQL*Loader-00429: insufficient number of elements found for varray
Cause: The COUNT directive was specified for a varray, but the number of
elements found is less than the number specified by the COUNT directive.
Action: Correct the data so that the count and the number of elements agree.
SQL*Loader-00430: NULL nested table element is not allowed
Cause: A row in a nested table was set to NULL. Nested tables cannot contain
NULL fields.
Action: Correct the data so that there are no NULL rows in the nested table.
SQL*Loader-00100 to SQL*Loader-03120 35-23
SQL*Loader-00431: illegal NULLIF or DEFAULTIF clause specified for nested table
column string
Cause: Rows in a nested table cannot be set to NULL. SQLLDR displays this error
when a NULLIF clause was specified for the element that defines the row that
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.
Action: None
SQL*Loader-00432: converted data too large
Cause: This message is preceded by a message identifying a row and column. It is
displayed when there is insufficient room to convert the data from the datatype in
the input file to the datatype for the column in the database.
Action: Modify the data so that it fits in the database field.
SQL*Loader-00433: no attributes found for column object string in table string
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.
SQL*Loader-00434: Can not load LOB/XML in a nested table along with the parent
table.
Cause: Loading LOBs and XML data within a nested table at the same time as the
parent table is not supported.
Action: Load the nested table with the LOB or XML column separately from the
parent table.
SQL*Loader-00435: invalid constant value string for nested table column string
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.
Action: Make sure the constant string contains valid hexadecimal characters and
that there are 32 hexadecimal characters.
SQL*Loader-00436: error converting GUID
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.
Action: Fix the data and reload the row.
SQL*Loader-00437: enabled constraint not allowed on LOB column string
Cause: An enabled constraint was present on a LOB column.
Action: Disable the constraint and try again.
SQL*Loader-00440: Invalid table specified as scope of a REF
Cause: As part of the REF directive one specifies the table name or another fields
name which contains the table name of the table which the REF references.
35-24 Oracle Database Error Messages
Action: Make sure that the right referenced table name is specified.
SQL*Loader-00456: end of collection found after number elements when looking for
number elements
Cause: A count value was specified for a varray or nested table column and the
number of rows found is less than the number of rows specified
Action: Verify that the count field has the correct value and that there is no
missing data for the collection.
SQL*Loader-00457: Comparison text of CONTINUEIF LAST must have length 1 not
number
Cause: The comparison text is too long. It can only be one character.
Action: Reduce the comparison text to one character.
SQL*Loader-00458: Comparison text ('string') of CONTINUEIF LAST must be
non-whitespace
Cause: The comparison text is a whitespace character (blank or tab).
Action: Change the comparison text to a non-whitespace character.
SQL*Loader-00459: error fetching numeric value for sequence on column (string)
Cause: An attempt was made to retrieve a non-numeric value for a sequenced
column.
Action: Verify that the data for the sequenced column is numeric. Then retry the
operation.
SQL*Loader-00460: Column (string), form of use (number) does not match char set
id of (number)
Cause: The given column with the given form of use does not have the same
character set ID as a previous column with the same form of use.
Action: This should not happen. Contact ORACLE support and supply the
following information: DDL for the table being loaded, and the SQL*Loader
control file. ADDED in 8.1
SQL*Loader-00461: direct path loading of datatype for column string not supported
Cause: The datatype for the specified column is one that cannot be loaded with
direct path.
Action: If the datatype is supported with conventional path, load the table using
conventional path.
SQL*Loader-00462: error inserting LOB into column string, row number, table string
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 sqlldr took (if any), and where the errors may be in order to
reload.
SQL*Loader-00463: secondary data file for LOB is string
Cause: The secondary data file that was in use for populating the LOB when an
error occured.
Action: None
SQL*Loader-00464: file offset for beginning of lob is string
Cause: The offset into the secondary data file that contains the start of the LOB
that was being written when an error occured.
SQL*Loader-00100 to SQL*Loader-03120 35-25
Action: None
SQL*Loader-00465: string directive expects number arguments, number found.
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.
Action: Correct the SQL*Loader control file so that the directive contains the
correct number of arguments.
SQL*Loader-00466: Column string does not exist in table string.
Cause: The SQL*Loader control file specified a table column that does not exist.
Action: None
SQL*Loader-00467: attribute string does not exist in type string for table string.
Cause: The SQL*Loader control file specified an attribute that does not exist for
the specified type. The table that contains the type is also identified in the error
message.
Action: Verify that the correct table in the correct schema is named in the
SQL*Loader control file. Also verify that the column name is spelled correctly.
SQL*Loader-00468: OID directive expects 1 argument, number found.
Cause: More than one argument was specified for an OID clause.
Action: Specify the name of the field containing the value to use for the OID. If
the OID for the table is user-defined, then do not use the OID clause in the control
file.
SQL*Loader-00469: SID directive expects 1 argument, number found.
Cause: More than one argument was specified for a SID clause.
Action: Only specify the name of the field containing the value to use for the SID
in the SID clause.
SQL*Loader-00470: table string does not have system generated OID
Cause: You specified an OID clause for a table but the table is either not an object
table or the table is an object table but the OIDs for the rows are not system
generated.
Action: Verify that the you are loading the correct table. If you are, then you must
not specify the OID clause for this table. You should use the OID clause only when
the table is an object table, has system generated OIDs and when you want to
specify OIDs to be assigned to each row of the table.
SQL*Loader-00471: OID or SID clause has an argument that is CONSTANT
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.
Action: Store the OID for each row in a filler field and specify the name of the
filler field as an argument.
SQL*Loader-00472: collections can contain only one non FILLER field specification
Cause: More than one non filler field specification is found in a collection field's
member field list.
Action: See correct syntax in the Utilities Manual. If indeed there is more than one
attribute that makes up the particular collection, then it must be a collection of a
35-26 Oracle Database Error Messages
object type which needs to be specified using the COLUMN OBJECT field
specification syntax.
SQL*Loader-00473: nesting of collections is not allowed.
Cause: Nesting of one collection type field description within another is not
allowed.
Action: Verify that collection nesting is attempted in the SQL*Loader control file.
Correct the mistake.
SQL*Loader-00474: no value set for dynamic file for column string in table string
row number
Cause: The data for the named column is in a dynamic LOBFILE or secondary
data file. This message is returned when the field containing the name of the file
with the data for this field has not been set or is NULL. This could be because the
record in the data file does not match the format described by the SQL*Loader
control file.
Action: Correct any errors in the data file or the SQL*Loader control file.
SQL*Loader-00475: field for dynamic file name is string in table string
Cause: This message is always displayed after message 474.
Action: None
SQL*Loader-00476: count of elements for collection is not set or null, 0 will be used
Cause: This message is displayed following a message that identifies the column
and row that contained the problem. The message indicates that the collection
field named in the previous message has the count of elements in the collection
stored in another field. This message is displayed if the field containing the count
does not have a value or is set to NULL. When this happens, SQL*Loader uses 0 as
the number of elements.
Action: If 0 is not the count of elementsfor the collection, correct the data in the
data file.
SQL*Loader-00477: REF directive for field string requires at least two arguments
Cause: The SQL Loader control file contains a REF directive for the field, but only
one argument was supplied for the directive. The REF directive always requires at
least two arguments.
Action: Supply the missing argument to the REF directive. Remember that you
must always supply a table name to the REF directive even if the REF is scoped.
SQL*Loader-00478: unable to continue due to missing filename for LOBFILE or
SDF
Cause: The name for a LOBFILE or secondary data file is either missing or NULL
for the current row. SQL*Loader is unable to continue loading since it can't
determine how to get the LOB for the next row.
Action: Correct the data file so that there are valid values for all fields containing
the names of LOBFILEs and secondary data files.
SQL*Loader-00479: REF directive for column string expects number arguments;
found number.
Cause: The number of arguments in the REF directive for the column is incorrect.
Action: Specify the correct number of arguments for REF. Remember that the REF
directive always requires a table name. Also, primary key REFs require one
arguments for each field in the primary key.
SQL*Loader-00100 to SQL*Loader-03120 35-27
SQL*Loader-00480: EXPRESSION may not be used with elements of a collection.
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.
SQL*Loader-00481: HIDDEN may not be used with non-scalar fields.
Cause: The HIDDEN keyword is only allowed for scalar fields.
Action: Remove the HIDDEN keyword from the non-scalar field in the control
file.
SQL*Loader-00486: sql-strings may not be specified for collection field string
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.
Action: Remove the sql-string from the field description. Modify the data file so
that it contains the values to be loaded into the column in the collection.
SQL*Loader-00487: COUNT clause required for collection string
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.
Action: Add a COUNT clause to the VARRAY or NESTED TABLE definition.
SQL*Loader-00488: string not a named collection type for filler field string
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.
Action: Verify that the correct type name was specified. If the type is defined in a
different schema, also verify that the correct schema name is specified.
SQL*Loader-00489: cannot insert NULL object into object table string, row number
Cause: There was no data specified in the control file, a lob file, or a secondary
data file for this object column.
Action: Place valid data for this column in the appropriate file prior to invoking
SQL*Loader to load data into this table.
SQL*Loader-00490: absolute position is not allowed for inline collections
Cause: The absolute position specification was used for inline collections.
Specifying the absolute position for inline collections is not supported.
Action: Use relative positioning for inline collections.
SQL*Loader-00500: Unable to open file (string)
Cause: SQL*Loader could not open the named file.
Action: Check the operating system messages below this one in the log file.
SQL*Loader-00501: Unable to read file (string)
Cause: SQL*Loader could not read the named file.
35-28 Oracle Database Error Messages
Action: Check the operating system messages following this message in the log
file.
SQL*Loader-00502: unable to open data file 'string' for field string table string
Cause: An attempt to open a LOBFILE or secondary data file 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 data file.
SQL*Loader-00503: Error appending extension to file (string)
Cause: SQL*Loader could not append the default extension to create the filename.
The given name could be too long or contain illegal characters.
Action: Check the specified filename.
SQL*Loader-00504: Error skipping records in file (string)
Cause: SQL*Loader could not open the file or could not read from it.
Action: Check that the file is where it is expected and that read access has been
granted.
SQL*Loader-00505: error reading LOBFILE
Cause: An attempt to read a secondary data file failed.
Action: Check the operating system message that follows this message for more
information.
SQL*Loader-00506: formatting error reading SDF or LOBFILE string for column
string in table string
Cause: The the record format of the named LOBFILE or SDF file is incorrect.
Action: Fix the record formatting problems in the file.
SQL*Loader-00507: unexpected EOF reading SDF or LOBFILE string for column
string in table string
Cause: The end of file was reached for a secondary data file 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 data file, make sure the record format is specified
correctly in the SQL*Loader control file.
SQL*Loader-00508: record formating error in data file string
Cause: The data found in the data file does not correspond to the record format in
the SQL*Loader control file.
Action: Verify that all records in the data file match the format as described in the
SQL*Loader control file.
SQL*Loader-00509: System error: string
Cause: A platform-specific error was returned during an operation. This message
is used to display the text of the error.
Action: None
SQL*Loader-00510: Physical record in data file (string) is longer than the
maximum(number)
Cause: The datafile has a physical record that is too long.
Action: Use CONCATENATE or CONTINUEIF. Break up the physical records.
SQL*Loader-00100 to SQL*Loader-03120 35-29
SQL*Loader-00511: Unable to initialize read functions
Cause: SQL*Loader could not initialize the read functions.
Action: Check the errors below this message in the log file for more information.
SQL*Loader-00512: Unable to free read buffer
Cause: An internal error has occurred.
Action: Contact customer support.
SQL*Loader-00513: Unable to close file (string)
Cause: SQL*Loader could not close the named file.
Action: Check the errors below this message in the log file for more information.
SQL*Loader-00514: Error getting elapsed time
Cause: SQL*Loader could not get the elapsed time from the system.
Action: No action required.
SQL*Loader-00515: Error getting CPU time
Cause: SQL*Loader could not get the CPU time from the system.
Action: No action required.
SQL*Loader-00516: Control file (string) has no contents
Cause: The named file was found to be empty.
Action: Check that the intended file was referenced and that it is not empty.
SQL*Loader-00517: Error decomposing file name (string)
Cause: SQL*Loader could not break down the filename into its component parts.
Action: Check the filename for illegal characters.
SQL*Loader-00518: Error reassembling file name (string)
Cause: SQL*Loader could not put the filename back together again from its
components.
Action: Check the filename for illegal characters.
SQL*Loader-00520: lfimknam failed for file (string)
Cause: LFI failed to make a name object for the file.
Action: Contact Oracle Worldwide Support.
SQL*Loader-00521: lfilini failed for file (string)
Cause: LFI failed to create or initialize a file object for the file.
Action: Contact Oracle Worldwide Support.
SQL*Loader-00522: lfiopn failed for file (string)
Cause: LFI failed to open the file.
Action: Check for any possible operating system errors and/or potential memory
problems.
SQL*Loader-00523: error number writing to file (string)
Cause: Could not write to specified file.
Action: Check the following: the file actually resides in the specified location you
have write privileges on the file you have sufficient disk space you have not
35-30 Oracle Database Error Messages
exceeded your disk quota If all of these conditions are satisfied, then retry the
operation.
SQL*Loader-00524: partial record found at end of datafile (string)
Cause: An incomplete record was found at the end of the indicated datafile.
Action: Make sure the last record in the datafile is complete and has the correct
terminating character(s). Also, if fixed-length records are in use, verify that no
record exceeds the platform-specific length for a single record.
SQL*Loader-00525: OCI return status: success
Cause: The message describes the status code returned by an OCI call.
Action: See surrounding messages for more information.
SQL*Loader-00526: OCI return status: success with info
Cause: The message describes the status code returned by an OCI call.
Action: See surrounding messages for more information.
SQL*Loader-00527: OCI return status: no data
Cause: The message describes the status code returned by an OCI call.
Action: See surrounding messages for more information.
SQL*Loader-00528: OCI return status: error
Cause: The message describes the status code returned by an OCI call.
Action: See surrounding messages for more information.
SQL*Loader-00529: OCI return status: invalid handle
Cause: The message describes the status code returned by an OCI call.
Action: See surrounding messages for more information.
SQL*Loader-00530: OCI return status: need data
Cause: The message describes the status code returned by an OCI call.
Action: See surrounding messages for more information.
SQL*Loader-00531: OCI return status: still executing
Cause: The message describes the status code returned by an OCI call.
Action: See surrounding messages for more information.
SQL*Loader-00532: OCI return status: continue
Cause: The message describes the status code returned by an OCI call.
Action: See surrounding messages for more information.
SQL*Loader-00533: OCI return status: unknown, value is number
Cause: An unknown status was returned by an OCI call.
Action: See surrounding messages for more information.
SQL*Loader-00534: Warning: no files found for INFILE wildcard specification
(string).
Cause: SQL*Loader could not find a file which matched the INFILE wildcard
specification.
Action: Check to make sure that the files exist in order for them to be loaded.
SQL*Loader-00100 to SQL*Loader-03120 35-31
SQL*Loader-00535: Warning: no files found for INFILE subdirectory search
specification (string).
Cause: SQL*Loader could not find a file which matched the INFILE subdirectory
search specification.
Action: Check to make sure that the files exist in order for them to be loaded.
SQL*Loader-00536: No files found for any data parameter specification or INFILE
specification.
Cause: SQL*Loader could not find a file which matched any of the data parameter
specifications or INFILE specifications.
Action: Check to make sure that the files exist in order for them to be loaded.
SQL*Loader-00537: Warning: no files found for data parameter wildcard
specification (string).
Cause: SQL*Loader could not find a file which matched the data parameter
wildcard specification.
Action: Check to make sure that the files exist in order for them to be loaded.
SQL*Loader-00538: Warning: no files found for data parameter subdirectory search
specification (string).
Cause: SQL*Loader could not find a file which matched the data parameter
subdirectory search specification.
Action: Check to make sure that the files exist in order for them to be loaded.
SQL*Loader-00539: No files found for any data parameter specification in express
mode.
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.
Action: Check to make sure that the files exist in order for them to be loaded.
SQL*Loader-00551: internal error: error initializing slf
Cause: An internal error occured while trying to initialize the file I/O component.
Action: Call customer support.
SQL*Loader-00552: insufficient privilege to open file
Cause: SQL*Loader does not have the previleges required to open the file.
Action: Verify that the correct file was specified and that the file has the
appropriate permissions.
SQL*Loader-00553: file not found
Cause: The specified file cannot be found.
Action: verify that the correct name exists and whether the file is in the intended
location.
SQL*Loader-00554: error opening file
Cause: An error occurred while trying to open the file. No further information is
available.
Action: Verify that the file is accessible.
SQL*Loader-00555: unrecognized processing option
Cause: The processing option specified for the file cannot be processed.
35-32 Oracle Database Error Messages
Action: Verify that the processing options specified for the file contain legal
syntax for the platform where SQL*Loader is running.
SQL*Loader-00556: unable to allocate read buffer
Cause: Attempt to allocate the read buffer failed.
Action: If possible, try specifying a smaller size for the read buffer.
SQL*Loader-00557: unable to allocate memory
Cause: An attempt to allocate some memory to track I/O for the file failed.
Action: Contact customer support.
SQL*Loader-00558: attempt to use SKIP parameter with linked-in loader
Cause: SKIP parameter was specified with a linked-in file processor.
Action: Do not use the SKIP parameter in this case.
SQL*Loader-00559: error closing file
Cause: An error occured while closing the file.
Action: Contact customer support.
SQL*Loader-00560: error reading file
Cause: An error occurred while reading the file.
Action: Make sure the file is still accessible.
SQL*Loader-00561: end of file
Cause: End of file reached.
Action: None
SQL*Loader-00562: record too big
Cause: A record in the file is larder than the read buffer.
Action: Verify that the file is not corrupt. If not, try specifying a larger size for the
read buffer.
SQL*Loader-00563: bad length for VAR record
Cause: The length protion of a VAR record contains non-numeric data.
Action: Fix the data in the file.
SQL*Loader-00564: illegal hexadecimal literal specified for record delimiter
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.
SQL*Loader-00565: unexpected error during skip .
Cause: an unexpected error occured while attempting to skip records.
Action: This message should be followed by another message giving more
specific information about the error
SQL*Loader-00566: partial record found at end of datafile
Cause: An incomplete record was found at the end of file.
Action: Make sure the last record in the datafile is complete and has the correct
terminating character(s).
SQL*Loader-00100 to SQL*Loader-03120 35-33
SQL*Loader-00567: unable to derive file name
Cause: An error occured while attempting to build a name for a data file, bad file,
discard file or log file.
Action: Instead of relying on SQL Loader to build these file names, try specifying
full file specifications for these files in the control file or on the SQL Loader
command line.
SQL*Loader-00568: error writing to file
Cause: Unexpected error occured while writing to a file. This message is followed
by another message with more information about the error.
Action: None
SQL*Loader-00569: READSIZE parameter exceeds maximum value string for
platform
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
Action: Decrease the size of the READSIZE parameter to be less than the
maximum size allowed on the platform.
SQL*Loader-00570: Warning: single bad file specification with multiple data files
using string file may get overwritten.
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.
Action: No action is needed. This is a warning. However, for a parallel load with
external tables or express mode, the file may get overwritten or may get corrupted
due to contention on the file by multiple parallel query slaves. Try the operation
again with a directory only or omit the parameter and use the default bad file
name.
SQL*Loader-00571: Warning: single discard file specification with multiple data
files, using string, but file may get overwritten.
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.
Action: No action is needed. This is a warning. However, for a parallel load with
external tables or express mode, the file may get overwritten or may get corrupted
due to contention on the file by multiple parallel query slaves. Try the operation
again with a directory only or omit the parameter and use the default discard file
name.
SQL*Loader-00572: Warning: cannot add "_\%p" to string for file string. Using file
name as is.
35-34 Oracle Database Error Messages
Cause: SQL*Loader could not add "_%p" to the file name. The name specified or
the derived name may be too long.
Action: No action is needed. This is a warning. However, for a parallel load with
external tables or express mode, the file may be overwritten or may get corrupted
due to contention on the file by multiple parallel query slaves. Try the operation
again with a shorter file name.
SQL*Loader-00573: Error opening the directory (string), failed with return code
[number].
Cause: An error occurred while trying to open the directory (see accompanying
error code).
Action: Verify that the directory is accessible.
SQL*Loader-00574: Check the log file: string for more information about the load.
Cause: Informational only.
Action: No action is needed.
SQL*Loader-00575: Check the log files: string string for more information about the
load.
Cause: Informational only.
Action: No action is needed.
SQL*Loader-00576: Error getting count of entries for directory (string), failed with
return code [number].
Cause: An error occurred while trying to get the count of directory entries (see
accompanying error code).
Action: Verify that the directory is accessible.
SQL*Loader-00577: Error reading the directory (string), failed with return code
[number].
Cause: An error occurred while trying to read the directory (see accompanying
error code).
Action: Verify that the directory is accessible.
SQL*Loader-00578: Error finishing wild card search in directory (string), failed with
return code [number].
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).
Action: This is an informational message. No action is needed.
SQL*Loader-00579: switching to direct path for the load
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.
Action: No action is needed. This is an informational message.
SQL*Loader-00582: Warning: cannot remove "_\%p" from string for file string.
Using file name as is.
Cause: SQL*Loader could not remove "_%p" from the file name.
Action: No action is needed. This is a warning. The file name was used as is.
SQL*Loader-00583: ignoring trim setting with string, using value of LDRTRIM
SQL*Loader-00100 to SQL*Loader-03120 35-35
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.
Action: No action is needed. This is an informational message.
SQL*Loader-00584: ignoring DEGREE_OF_PARALLELISM setting with string,
using value of NONE
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.
Action: No action is needed. This is an informational message.
SQL*Loader-00585: defaulting DEGREE_OF_PARALLELISM to NONE since
load=number was specified
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.
Action: No action is needed. This is an informational message.
SQL*Loader-00600: Bind size of number bytes increased to number bytes to hold 1
row.
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.
SQL*Loader-00601: For INSERT option, table must be empty. Error on table string
Cause: A non-empty table is being loaded with the INSERT option.
Action: Use the REPLACE keyword to empty the old table and store the new data
in its place. Use the APPEND keyword to leave the table's contents intact and add
the new data to it.
SQL*Loader-00602: Maximum converted length number of column string is too big
for bind array
Cause: The named column cannot undergo the specified character set conversion
and still be placed in a contiguous piece of memory on the system.
Action: Specify a shorter data column or eliminate the conversion.
SQL*Loader-00603: Maximum length number of column string is too big for bind
array
Cause: The named column cannot be put in a contiguous piece of memory on the
system.
Action: Specify a shorter data column.
SQL*Loader-00604: Error occurred on an attempt to commit
Cause: An error occurred while trying to commit changes to the database.
Action: Look at the message listed below this one in the log file for more
information.
SQL*Loader-00605: Non-data dependent ORACLE error occurred -- load
discontinued.
35-36 Oracle Database Error Messages
Cause: An error occurred that is independent of the data. For example, an
out-of-space condition. Because all further rows will be rejected, the load is
discontinued. (If the error were data dependent, then other rows might succeed.)
Action: See the errors below this one in the log file for more information.
SQL*Loader-00606: Object string in INTO TABLE clause is not a local table
Cause: The synonym specified in the INTO TABLE clause in the SQL*Loader
control file specifies a remote object via a database link. Only a synonym for an
existing local table can be specified in the INTO TABLE clause.
Action: Ensure that a local table name or a synonym for a local table is fully
specified in the INTO TABLE clause. The table must already exist.
SQL*Loader-00607: partition not empty for INSERT option; table string, partition
string
Cause: An attempt was made to use the INSERT option on a non-empty partition.
Action: Empty the partition, or use the REPLACE or TRUNCATE option.
SQL*Loader-00608: subpartition not empty for INSERT option; table string,
subpartition string
Cause: An attempt was made to use the INSERT option on a non-empty
subpartition.
Action: Empty the subpartition, or use the REPLACE or TRUNCATE option.
SQL*Loader-00609: value used for ROWS parameter changed from number to
number
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.
Action: If the limit of 65534 rows for conventional path load is not being reached,
then try increasing the value of BINDSIZE.
SQL*Loader-00610: cannot load system partitioned table string; partition name(s)
required
Cause: An attempt was made to load a system partitioned table with no
partitioning clause specified in the SQL*Loader control file.
Action: Specify the partition name(s) in the SQL*Loader control file.
SQL*Loader-00620: Initial enclosure character not found
Cause: A mandatory initial enclosure delimiter was not present. Either it is
missing on the current field or the previous field is missing an identical closing
delimiter.
Action: Supply the missing delimiters.
SQL*Loader-00621: Field in data file exceeds maximum length
Cause: A field exceeded its maximum allowable length. The maximum length is
either the length specified in the SQL*Loader control file, or, for delimitable fields
without a length specified, the default maximum length (255 bytes).
Action: Check for missing delimiters and/or shorten the field.
SQL*Loader-00100 to SQL*Loader-03120 35-37
SQL*Loader-00622: Column not found before end of logical record (use TRAILING
NULLCOLS)
Cause: The logical record ended before all specified fields were found.
Action: If the missing fields should be loaded as null, use the TRAILING
NULLCOLS clause. Otherwise, correct the data.
SQL*Loader-00623: second enclosure string not present
Cause: The logical end of record or the end of a LOBFILE was reached before a
second enclosure delimiter was found.
Action: Correct the data file to include the missing delimiter.
SQL*Loader-00624: no terminator found after TERMINATED and ENCLOSED
field
Cause: No termination delimiter was found after the enclosed field ended.
Action: Supply the missing termination delimiter.
SQL*Loader-00625: Multibyte character error in control file.
Cause: Incomplete multi-byte character strings were found in the SQL*Loader
control file.
Action: Edit the SQL*Loader control file to check that all multi-byte character data
is valid.
SQL*Loader-00626: Character set conversion buffer overflow.
Cause: A conversion from the datafile character set to the client character set
required more space than that allocated for the conversion buffer. The size of the
conversion buffer is limited by the maximum size of a varchar2 column.
Action: The input record is rejected. The data will not fit into the column.
SQL*Loader-00627: Character set conversion graph not available.
Cause: A conversion from the datafile character set to the client character failed
due to the conversion graph not being available.
Action: Contact Oracle support. Check NLSRTL installation.
SQL*Loader-00628: Character set conversion error.
Cause: A character set conversion error occurred.
Action: Contact Oracle support. Check NLSRTL installation. Provide a
reproduceable test case.
SQL*Loader-00640: Variable length field was truncated.
Cause: The end of the logical record was encountered before the end of a variable
length field. The length of each variable-length field is embedded in the field, so
SQL*Loader knows that more data should have been present.
Action: Check the data for inadvertent truncation and verify the SQL*Loader
control file specifications against the log file; the field may be starting in the wrong
place.
SQL*Loader-00641: Invalid packed decimal nibble.
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.
35-38 Oracle Database Error Messages
SQL*Loader-00642: Relative start position > absolute field end position.
Cause: A field specified as POSITION(*+n:y) had its relative start occur after the
absolute position y.
Action: Check that a delimiter is not missing and that the values of n and y are
correct.
SQL*Loader-00643: error executing INSERT statement for table string
Cause: A fatal error occured 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. Specifcally,
check for balanced parenthesis and correct use of quotation marks. Another format
error
SQL*Loader-00644: end of logical record found when reading length of varying
length field
Cause: While attempting to read the length portion of a varying length field, then
end of the logical record was reached.
Action: Verify that the SQL*Loader control file describes the data correctly and
that the data in the data file matches the description in the SQL*Loader control file
SQL*Loader-00645: error converting character length field to a number
Cause: An error occurred while attempting to convert the characters containing
the count portion of a VARCHARC or VARRAWC field.
Action: Verify that the count portion for the column has the correct value.
SQL*Loader-00646: lob set to EMPTY in column string, row number, table string
Cause: Encountered errors (e.g. 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.
SQL*Loader-00647: Integer to number conversion error
Cause: An error occurred while attempting to convert an integer to an 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 length specified is valid.
SQL*Loader-00649: Quoted string missing closing quote
Cause: A quoted string in the control file is missing a closing quote.
Action: Insert the closing quote as appropriate.
SQL*Loader-00650: incomplete lob data written for column string, row number,
table string
Cause: Encountered errors (e.g. 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.
SQL*Loader-00651: error skipping lob for column string, row number, table string
Cause: Encountered errors (e.g. parsing errors in LOBFILE) while skipping LOBs.
Action: Correct the data file (see accompanying messages) and reload.
SQL*Loader-00100 to SQL*Loader-03120 35-39
SQL*Loader-00652: Invalid zoned decimal byte.
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.
SQL*Loader-00653: XML data set to NULL in column string, row number, table
string
Cause: Encountered errors (e.g. 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.
SQL*Loader-00654: Variable length field exceeds maximum length.
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).
Action: Shorten the field and its length.
SQL*Loader-00655: cannot load object-relational XML attribute using direct path
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.
Action: Perform the load with conventional path mode.
SQL*Loader-00656: position specification for column string is not allowed in
external table loads
Cause: Use of a position specification was present in an external table load.
Action: Either remove the position specification, change the position specification
to a field name reference, use direct path, or use conventional path.
SQL*Loader-00657: table string loaded using number passes, partition memory limit
was numberkb
Cause: Due to memory use, multiple passes were used to load some partitions.
Action: To decrease the number of passes, consider increasing the partition
memory limit using the PARTITION_MEMORY command line option, or by
increasing PGA_AGGREGATE_TARGET. Note that increasing the limit too much
can cause the load to run out of memory.
SQL*Loader-00700: Out of memory while performing essential allocations [number]
Cause: SQL*Loader could not allocate the memory it needs.
Action: Check the operating system and process memory. Increase memory
available to SQL*Loader, if possible. If using direct path, try lowering the
columnarrayrows option (see log file for current default value).
SQL*Loader-00702: Internal error - string
Cause: An internal error has occurred.
Action: Make a note of the message and contact customer support.
35-40 Oracle Database Error Messages
SQL*Loader-00703: Internal error: argument number
Cause: An internal error has occurred.
Action: Make a note of the message and the number, then contact customer
support.
SQL*Loader-00704: Internal error: string [number]
Cause: An internal error has occurred.
Action: Make a note of the message and the number, then contact customer
support.
SQL*Loader-00705: Internal error
Cause: An internal error has occurred.
Action: Contact customer support.
SQL*Loader-00706: Bad argument to ulerr [number].
Cause: An internal error has occurred.
Action: Contact customer support.
SQL*Loader-00708: Internal error: unknown status number returned from sllf layer
Cause: An unknown status was returned by a call to the sllf layer.
Action: Contact customer support.
SQL*Loader-00709: Internal error calling SLTS layer: string failed
Cause: A nonsuccess status was returned by a call to the SLTS layer.
Action: Contact customer support.
SQL*Loader-00710: Internal error: direct path stream buffer not loaded
Cause: A direct path stream buffer was built but not loaded.
Action: Contact customer support.
SQL*Loader-00711: Internal error: bad address for little endian UTF16 conversion
Cause: Address for little endian UTF16 data not in a valid buffer.
Action: Contact customer support.
SQL*Loader-00712: Internal error: bad address for big endian UTF16 conversion
Cause: Address for big endian UTF16 data not in a valid buffer.
Action: Contact customer support.
SQL*Loader-00713: Internal error calling SLTS layer: string failed with return code
[number].
Cause: A nonsuccess status was returned by a call to the SLTS layer.
Action: Contact customer support.
SQL*Loader-00800: string specified and ignored
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.
SQL*Loader-00801: all INTO TABLE clauses must have the same options (string)
Cause: At least two INTO TABLE clauses have different options set.
Action: Set the options to be the same or do the loads separately.
SQL*Loader-00100 to SQL*Loader-03120 35-41
SQL*Loader-00802: numeric EXTERNAL with DEFAULTIF clause not supported by
External Table
Cause: A numeric EXTERNAL type was specified with a DEFAULTIF clause
which is not supported by external table load.
Action: Remove the clause if possible or do not use external table load.
SQL*Loader-00803: Field type string not supported by External Table
Cause: The specified field type is not supported by external table.
Action: Remove the specified field type or do not use external table load.
SQL*Loader-00804: SEQUENCES with intervals are not supported by External
Table Load.
Cause: A sequence with an interval was specified which is not supported by
external table load.
Action: Remove the interval from the sequence, or remove the sequence itself, or
do not use external table load.
SQL*Loader-00805: Option string not supported by string
Cause: The specified option is not supported by external table or express mode
load.
Action: Remove the specified option or do not use external table load or express
mode load.
SQL*Loader-00806: unknown record format specified for data file
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.
SQL*Loader-00807: error loading table
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.
Action: See subsequent messages for more information about the error.
SQL*Loader-00808: error creating sequence: string
Cause: An attempt to create a sequence needed for the load failed.
Action: See messages that follow this one for information about the failure.
SQL*Loader-00809: error dropping sequence: string
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.
SQL*Loader-00810: error creating external table: string
Cause: An attempt to create the external table sued for the load failed.
Action: See messages that follow for more information about the failure.
SQL*Loader-00811: error dropping external table: string
Cause: An error occurred when trying to drop an external table. Note that the
table may have been left from a previous load.
35-42 Oracle Database Error Messages
Action: None
SQL*Loader-00812: error creating internal table: string
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.
Action: None
SQL*Loader-00813: error dropping internal table: string
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.
Action: None
SQL*Loader-00816: error creating temporary directory object string for file string
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.
SQL*Loader-00817: error dropping directory object string
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.
SQL*Loader-00820: cannot create WHERE clause with POSITION syntax for table
string
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.
Action: Modify the control file to only use field name 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 tables separately. In
that case, SQL*Loader can use the access parameter list LOAD WHEN syntax to
specify the range of bytes using POSITION syntax for a single table.
SQL*Loader-00821: switching to GENERATE_ONLY
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.
Action: None
SQL*Loader-00822: operation not supported on external organized table
Cause: User attempted on operation on an external table which is not supported.
Action: Don't do that!
SQL*Loader-00100 to SQL*Loader-03120 35-43
SQL*Loader-00823: TREAT AS clause for object tables not supported for external
tables
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.
Action: Use SQL*Loader direct path or SQL*Loader conventional path to load the
table.
SQL*Loader-00824: column type string not supported by string
Cause: The column type was not supported by external table or express mode
using the external table load method.
Action: Do not use external table or express mode using the external table load
method. Try the load using conventional path or direct path as the load method.
SQL*Loader-00901: Error logging on to ORACLE:
Cause: An attempt was made to log on to Oracle in direct path load mode.
Action: Ensure that the instance is up and running. Check the Oracle messages
below this one in the log file for more information.
SQL*Loader-00902: Error opening cursor: [number]
Cause: An internal error has occurred.
Action: Check the Oracle messages below this one in the log file and contact
customer support.
SQL*Loader-00903: Database must be at least version
number.number.number.number.number for direct path
Cause: The direct path load mode is being used with an incompatible database.
Action: Upgrade the database to the specified version or else use the conventional
path load.
SQL*Loader-00904: You cannot used the direct path when linked with v5 of the
database
Cause: The direct path mode is being used after SQL*Loader has been linked with
a Version 5 database.
Action: Use the conventional path.
SQL*Loader-00905: Error parsing SQL statement for upi: [number]
Cause: Header message.
Action: Check the message below this one in the log file for more information.
SQL*Loader-00906: Error executing SQL statement for upi: [number]
Cause: An internal error has occurred.
Action: Check the message below this one in the log file for more information.
SQL*Loader-00909: Loader views must be loaded (as SYS) for direct path to be used
Cause: Database views required for the direct path mode are not present.
Action: The Oracle7 Server Administrator's Guide details how to run the required
scripts as user SYS for loading the required views.
SQL*Loader-00910: Error binding input variables for upi: [number]
35-44 Oracle Database Error Messages
Cause: Header message.
Action: Check the message below this one in the log file for more information.
SQL*Loader-00911: Error defining output variable(s) for upi: [number]
Cause: Header message.
Action: Check the message below this one in the log file for more information.
SQL*Loader-00913: Error fetching results of select statement (upi): [number]
Cause: Header message.
Action: Check the message below this one in the log file for more information.
SQL*Loader-00914: Error locking table string in exclusive mode.
Cause: The direct path mode could not lock the named table.
Action: Check the message below this one in the log file for more information.
Check that the necessary privileges have been granted.
SQL*Loader-00915: Error closing cursor: [number]
Cause: Header message.
Action: CCheck the message below this one in the log file for more information.
SQL*Loader-00916: Error checking path homogeneity
Cause: To do a direct path load load when the front end and back end of the
database are on separate hardware systems, the systems must be identical, using
the same machine, operating system, and character set. This error occurs when
SQL*Loader detects a difference between the systems that will prevent a direct
load from operating properly.
Action: Use a conventional path load for this configuration.
SQL*Loader-00918: The catalog must be loaded (as SYS) for SQL*Loader to be used
Cause: The catalog is not loaded.
Action: Logon as user SYS and load the Oracle7 catalog and the views in the
script ULVIEW.SQL.
SQL*Loader-00919: Error during upi fetch: [number]
Cause: An internal error has occurred.
Action: Check the message below this one in the log file for more information.
SQL*Loader-00925: Error while string
Cause: An internal error has occurred.
Action: Check the message below this one in the log file for more information.
The table or column referenced may not be accessible.
SQL*Loader-00926: OCI error while string for table string
Cause: An OCI error has occurred.
Action: Check the message below this one in the log file for more information.
The table or column referenced may not be accessible.
SQL*Loader-00929: Error parsing insert statement for table string.
Cause: The table's insert statement caused a parse error.
Action: Check all SQL strings that were used.
SQL*Loader-00930: Error parsing insert statement for table string column string.
SQL*Loader-00100 to SQL*Loader-03120 35-45
Cause: The named column's INSERT statement caused a parse error.
Action: Check the message below this one in the log file for more information.
Check the SQL string used for this column.
SQL*Loader-00931: OCI error while binding variable for column string in table
string
Cause: An OCI error has occurred.
Action: Check the errors below it for more information. The SQL string for this
column may be in error.
SQL*Loader-00932: Could not truncate table string.
Cause: Truncation of the table was attempted and failed.
Action: Check the following errors for more information. Truncation due to
referential constraints should not occur.
SQL*Loader-00933: Specified file string not part of database
Cause: The specified filename to load the table is not a database file.
Action: Specify a valid datafile.
SQL*Loader-00934: Incorrect data file string specified for table string
Cause: A datafile name was given to load the table that is not a part of the
tablespace in which the table resides.
Action: Specify a valid datafile.
SQL*Loader-00935: Error verifying required option for parallel load.
Cause: An error was encountered because a required option was not found or was
invalid.
Action: Correct the problem as described in the accompanying Oracle message.
SQL*Loader-00937: parallel load requested and string has enabled triggers or
constraints
Cause: A request was made for a parallel direct load, but the object to be loaded
has an enabled constraint (check, referential) and/or enabled triggers.
Action: Disable the offending enabled constraints and/or triggers and retry the
parallel direct load.
SQL*Loader-00938: partition load requested and string has enabled triggers or
constraints
Cause: A request was made for a direct load of a single partition, but the object to
be loaded has an enabled constraint (check, referential) and/or enabled triggers.
Action: Disable the offending enabled constraints and/or triggers and retry the
parallel direct load.
SQL*Loader-00939: OCI error while string for table string partition string
Cause: Header message.
Action: Check the following errors for more information. The table or partition
referenced may not be accessible.
SQL*Loader-00940: UPI error while setting NCHAR bind attributes for column
string table string
Cause: An error occured while setting the charsetform attribute of an NCHAR
column.
35-46 Oracle Database Error Messages
Action: This is an internal error. Report to ORACLE support.
SQL*Loader-00941: Error during describe of table string
Cause: Error while executing a describe of a select list on the given table. Check
the error immediately preceding this error.
Action: None
SQL*Loader-00942: partition string not part of table string
Cause: the specified partition is not part of the specified table
Action: None
SQL*Loader-00943: incorrect datafile string specified for table string partition string
Cause: The specified datafile is not in the tablespace of the specified partition.
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.
Action: None
SQL*Loader-00944: error preparing insert statement for table string.
Cause: A call to OCIStmtPrepare for the table's insert statement returned an error.
Action: Refer to the message that follows for information about the error returned
by OCIStmtPrepare. Make sure the syntax is correct for all SQL strings specified in
the SQL*Loader control file.
SQL*Loader-00945: record size number too large for direct path
Cause: The maximum size of records in the data file is larger than the maximum
size supported by direct path, which is 65535
Action: Load the data file using conventional path.
SQL*Loader-00946: OCI error while string for table string subpartition string
Cause: Header message.
Action: Check the following errors for more information. The table or
subpartition referenced may not be accessible.
SQL*Loader-00947: subpartition load requested and string has enabled triggers or
constraints
Cause: A request was made for a direct load of a single subpartition, but the
object to be loaded has an enabled constraint (check, referential) and/or enabled
triggers.
Action: Disable the offending enabled constraints and/or triggers and retry the
parallel direct load.
SQL*Loader-00948: subpartition string not part of table string
Cause: the specified subpartition is not part of the specified table
Action: None
SQL*Loader-00949: incorrect datafile string specified for table string subpartition
string
Cause: The specified datafile is not in the tablespace of the specified subpartition.
Due to use of FILE= keyword on a subpartitioned table. When loading all
subpartitions of a subpartitioned table, the subpartitions must be in the same
tablespace. When loading a single subpartition, the tablespace of the subpartition
SQL*Loader-00100 to SQL*Loader-03120 35-47
being loaded must be the same as the tablespace in which the specified datafile file
resides.
Action: None
SQL*Loader-00950: Error shipping data structures across 2-task
Cause: Header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00951: Error calling once/load initialization
Cause: Header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00952: Error calling once/data file initialization
Cause: Header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00953: Error shipping read buffer across 2-task
Cause: Header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00954: Error shipping index to read buffer across 2-task
Cause: Header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00955: Error calling col array build, block formatter
Cause: Header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00956: Error calling once/data file finishing
Cause: Header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00957: Error shipping text string across 2-task
Cause: Header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00958: Error popping data relocation address stack
Cause: Header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00959: Error shipping buffer across 2-task
Cause: Header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00961: Error calling once/load finishing for table string
Cause: Header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00962: Error setting user-side Ctrl-C handler
Cause: Header message.
Action: Check the error(s) below it for more information.
35-48 Oracle Database Error Messages
SQL*Loader-00963: Error clearing user-side Ctrl-C handler
Cause: Header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00965: Error number disabling constraint string on table string
Cause: Header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00966: Error number disabling all triggers on table string
Cause: Header message.
Action: Check the error(s) below it for more information.
SQL*Loader-00969: Error performing file name translation on kernel side
Cause: File specified for parallel load is probably not a valid database file.
Action: Specify a valid database file.
SQL*Loader-00970: enabled constraint on an XML column not allowed in direct
path
Cause: An enabled check constraint existed on an XML column.
Action: Disable the check constraint before attempting to load the table data using
the direct path mode, or leave the constraint enabled but use the conventional path
mode instead.
SQL*Loader-00971: parallel load option not allowed when loading lob columns
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)
Action: Do not use the parallel option when loading lob columns.
SQL*Loader-00972: Warning: ROWS parameter ignored when NO_INDEX_
ERRORS is used.
Cause: Specifying save points using the ROWS parameter was not supported
with NO_INDEX_ERRORS=TRUE.
Action: Remove the ROWS parameter from the command-line arguments or do
not specify NO_INDEX_ERRORS=TRUE.
SQL*Loader-00973: Warning: ROWS parameter ignored when PARTITION_
MEMORY is used.
Cause: Specifying save points using the ROWS parameter was not supported
with PARTITION_MEMORY=n.
Action: Remove the ROWS parameter from the command-line arguments or do
not specify PARTITION_MEMORY=n.
SQL*Loader-00974: database is not available for update
Cause: The database was not opened for read/write access. SQL*Loader requires
that the database be opened for read/write access.
Action: Verify that the database is opened for read/write access. Then retry the
operation.
SQL*Loader-02026: the load was aborted because SQL Loader cannot continue.
Cause: The load cannot continue. See the error message before this
* message for the cause of the error.
SQL*Loader-00100 to SQL*Loader-03120 35-49
Action: See the action for the error message that precedes this one.
SQL*Loader-02050: Multibyte character error.
Cause: Text specified by POSITION or terminated by newlines is invalid.
Action: Edit the SQL*Loader control file or the data file to fix alignment of
column.
SQL*Loader-02300: For CSV format files, all fields must be delimited fields. Field
string is not delimited.
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.
Action: Make all of the fields delimited or remove the CSV specification and retry.
SQL*Loader-02301: For FIELD NAMES, all fields must be delimited fields. Field
string is not delimited.
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.
Action: Make all of the fields delimited and retry.
SQL*Loader-02302: Data in the control file not supported with CSV format files.
Cause: CSV format file was specified with INFILE * indicating that there was data
in the control file.
Action: Move the data to a separate data file and retry.
SQL*Loader-03120: Resumable parameters ignored -- current session not resumable
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.
  • 1
    点赞
  • 5
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
ORA-01017错误是Oracle数据库中一个常见的错误,它表示用户在进行认证时没有提供正确的用户名或密码,导致登录失败。这个错误可能会在用户在进行各种数据库操作时出现,例如启动或连接数据库、执行SQL查询、创建或删除表等。 如果您遇到ORA-01017错误,首先应该确认您输入的用户名和密码是否正确。您可以尝试使用其他有效的用户名和密码重新登录数据库。如果您使用的是Oracle数据库的默认账户,例如SYS或SYSTEM账户,那么可以使用以下命令来重置密码: ALTER USER username IDENTIFIED BY new_password; 其中username为您要重置密码的账户名,new_password为新密码。 除了输入错误的用户名或密码外,还有一些其他常见的原因可能会导致ORA-01017错误。例如,您的数据库可能已被锁定,可能是由于某些数据库对象被其他用户或进程所占用,或者因为数据库正在进行备份或恢复操作。在这种情况下,您需要等待一段时间,直到数据库解锁。您还可以尝试重启数据库实例来解决此问题。 另外,ORA-01017错误也可能是由于网络故障或连接问题引起的。如果您正在通过网络连接数据库,请检查您的网络连接是否正常、数据库服务器是否可用,并确保您使用的是正确的连接字符串和端口号。 总之,ORA-01017错误可能是由多种原因引起的,但它通常表示用户输入了错误的用户名或密码。如果您遇到此问题,您需要核实提供的认证信息是否正确,并尝试使用其他有效的用户名和密码重新登录数据库。如果错误仍然存在,您可以考虑其他可能的原因,并采取相应的措施来解决问题。

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值