32 ORA-60001 to ORA-64307

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.

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.; 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-62001: value for parameter cannot contain a comma: Cause: Parameter value contained a comma.; Action: Remove the comma from the parameter value.

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

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

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

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-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-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: hybrid columnar compression is only supported in tablespaces residing on Exadata storage: Cause: An attempt was made to use hybrid columnar compression on unsupported storage.; Action: Create this table in a tablespace residing on Exadata storage or use a different compression type.