12C ORA 错误汇总18 ORA 57000 to ORA 65535 EXP 00000 to EXP 00114

分享一下我老师大神的人工智能教程！零基础，通俗易懂！http://blog.csdn.net/jiangjunshow

也欢迎大家转载本篇文章。分享知识，造福人民，实现我们中华民族伟大复兴！

                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