Oracle 12c R2 Error Codes and Solution Suggestions from ORA-12800 to ORA-13000
- ORA-12800: system appears too busy for parallel query execution
Cause: load on system is too high to perform parallel queries.
Action: re-execute serially or wait until system load is reduced.
Cause: A parallel query server reached an exception condition.
Action: Check the following error message for the cause, and consult your error manual for the appropriate action.
Cause: A parallel query server lost contact with the foreground (coordinator) process/thread.
Action: Check your system for anomalies and reissue the statement. If this error persists, contact Oracle Support Services.
Cause: A parallel query server lost contact with another server.
Action: Check your system for anomalies and reissue the statement. If this error persists, contact Oracle Support Services.
Cause: Cannot find process information for a parallel query server thread.
Action: Check your system for anomalies and reissue the statement. If this error persists, contact Oracle Support Services.
Cause: A parallel query server died unexpectedly, PMON cleaning up the process.
Action: Check your system for anomalies and reissue the statement. If this error persists, contact Oracle Support Services. See trace file for more details.
Cause: Internal error.
Action: This error should not normally occur. If it persists, contact Oracle Support Services.
Cause: Internal error.
Action: This error should not normally occur. If it persists, contact Oracle Support Services.
Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM command to a value larger than the number of available instances.
Action: See the accompanying message for the current allowable maximum value, or set SCAN_INSTANCES / CACHE_INSTANCES to ALL.
Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM command while the database was mounted in exclusive mode.
Action: SCAN_INSTANCES / CACHE_INSTANCES may not be set unless running Oracle Real Application Clusters mounted in CLUSTER_DATABASE mode.
Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to a value higher than the maximum allowed by the system.
Action: Set PARALLEL_MAX_SERVERS to a value less than or equal to the maximum specified in the accompanying message and retry.
Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter to a value higher than PARALLEL_MAX_SERVERS.
Action: Set PARALLEL_MIN_SERVERS to a value less than or equal to PARALLEL_MAX_SERVERS (indicated in the accompanying message) and retry.
Cause: PARALLEL was specified more than once, NOPARALLEL was specified more than once, or both PARALLEL and NOPARALLEL were specified in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement, or in a RECOVER command.
Action: Remove all but one of the PARALLEL or NOPARALLEL clauses and reissue the statement.
Cause: PARALLEL 0 or DEGREE 0 was specified in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement.
Action: Specify a degree of parallelism greater than 0 or specify default parallelism using PARALLEL with no degree or using DEGREE DEFAULT within a PARALLEL clause.
Cause: CACHE was specified more than once, NOCACHE was specified more than once, or both CACHE and NOCACHE were specified in a CREATE TABLE or CLUSTER, or in an ALTER TABLE or CLUSTER statement.
Action: Remove all but one of the CACHE or NOCACHE clauses and reissue the statement.
Cause: PARALLEL parameter specifying number of instances must be a positive integer or DEFAULT
Action: specify a positive integer or DEFAULT for INSTANCES if parallelism across instances is desired.
- ORA-12816: parallel create index fastpath operation
- ORA-12817: parallel query option must be enabled
Cause: A parallel query option feature has been invoked but this option has not been enabled.
Action: Enable the parallel query option.
Cause: an unrecognized option was used within a PARALLEL clause.
Action: specify any combination of DEGREE { n | DEFAULT } and INSTANCES { n | DEFAULT } within the PARALLEL clause.
Cause: PARALLEL clause cannot be empty.
Action: specify any combination of DEGREE { n | DEFAULT } and INSTANCES { n | DEFAULT } within the PARALLEL clause.
Cause: invalid value for DEGREE was specified within a PARALLEL clause.
Action: specify a positive integer or DEFAULT for the DEGREE option within a PARALLEL clause.
Cause: invalid value for INSTANCES was specified within a PARALLEL clause.
Action: specify a positive integer or DEFAULT for the INSTANCES option within a PARALLEL clause.
Cause: DEGREE or INSTANCES was specified more than once within a PARALLEL clause.
Action: specify each desired PARALLEL clause option only once.
Cause: the PARALLEL keyword was used alone or DEGREE DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER command.
Action: respecify with an explicit degree of parallelism.
Cause: INSTANCES DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER command
Action: respecify with an explicit value for INSTANCES or omit the INSTANCES option if single instance recovery is desired.
Cause: the DEGREE option was omitted from an ALTER DATABASE RECOVER command.
Action: respecify with an explicit degree of parallelism.
Cause: parallel query server was hung and subsequently killed.
Action: re-execute query and report suspicious events in trace file to Oracle Support Services if error persists.
- ORA-12827: insufficient parallel query slaves (requested string, available string, parallel_min_percent string)
Cause: PARALLEL_MIN_PERCENT parameter was specified and fewer than the minimum number of slaves were acquired
Action: Either reexecute the query with a lower PARALLEL_MIN_PERCENT or wait until some running queries are completed, thus freeing up slaves
Cause: PDML transaction cannot be started because we are not in the coordinator site of the distributed transaction.
Action: Do not use PDML at remote sites.
Cause: parallel statement failed because all itls in the current block are occupied by siblings of the same transaction.
Action: increase MAXTRANS of the block or reduce the degree of parallelism for the statement. Reexecute the statement. Report suspicious events in trace file to Oracle Support Services if error persists.
Cause: After executing a parallel INSERT/UPDATE/DELETE statement, a command other than COMMIT or ROLLBACK was issued.
Action: Execute COMMIT or ROLLBACK before issuing another SQL command.
Cause: After executing an INSERT statement with an APPEND hint, a command other than COMMIT or ROLLBACK was issued.
Action: Execute COMMIT or ROLLBACK before issuing another SQL command.
Cause: After executing a query on a global v$ fixed view, one or more instances failed to allocate a slave to process query
Action: To allow results to be returned by sucessfully allocated slaves, execute ALTER SESSION SET ALLOW_PARTIAL_SN_RESULTS=TRUE statement, or check parameters of instances
Cause: The coordinator’s instance must be a member of the parallel_instance_group in which this operation will be run.
Action: Either add the coordinator’s instance to the current parallel_instance_group or change parallel_instance_group.
Cause: The instance group name is too long.
Action: Either shorten the name or get rid of the instance group.
Cause: There must be at least one instance in the GLOBAL_VIEW_ADMIN_GROUP in order to execute a query on global views
Action: Change the value of GLOBAL_VIEW_ADMIN_GROUP
Cause: Within the same transaction, an attempt was made to add read or modification statements on a table after it had been modified in parallel or with direct load. This is not permitted.
Action: Rewrite the transaction, or break it up into two transactions: one containing the initial modification and the second containing the parallel modification operation.
Cause: Within the same transaction, an attempt was made to perform parallel modification operations on a table after it had been modified. This is not permitted.
Action: Rewrite the transaction or break it up into two transactions: one containing the parallel modification and the second containing the initial modification operation.
Cause: Within a transaction, an attempt was made to perform distributed access after a PDML or insert direct statement had been issued.
Action: Commit/rollback the PDML transaction first, and then perform the distributed access, or perform the distributed access before the first PDML statement in the transaction.
Cause: Transaction in progress
Action: Commit or rollback transaction and then re-execute
Cause: The cursor was invalidated during the parse phase of deferred parallel processing, e.g. when set operands are parallelized.
Action: Depends on why the cursor was invalidated. Possible causes include DDL on a schema object and shared pool being flushed.
Cause: The coodinator crashed or released the lock on the partition which the slave is trying to aquire currently.
Action: Check if the coordinator or some of the other slaves died. Also check that the lock has not been corrupted. Issue the pdml again.
Cause: OS or interconnect problem receiving interinstance message
Action: Check OS specific diagnostics
Cause: When executing a query on a gv$ fixed view, one or more instances failed to allocate a slave to process query.
Action: Check trace output for instances on which slaves failed to start. GV$ query can only proceed if slaves can be allocated on all instances.
Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to a value less than PARALLEL_MIN_SERVERS.
Action: Set PARALLEL_MAX_SERVERS to a value greater than or equal to PARALLEL_MIN_SERVERS value specified in the accompanying message and retry.
- ORA-12852: PARALLEL_MIN_SERVERS must be less than PROCESSES minus the number of reserved processes, string
Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter to a value higher than PROCESSES minus the number of reserved processes.
Action: Set PARALLEL_MIN_SERVERS to a value less than PROCESSES minus the number of reserved processes specified in the accompanying message and retry.
Cause: Insufficient SGA memory for PX buffers
Action: Reconfigure sga to include at least (max – current) bytes of additional memory
Cause: The parallel query statement produced a temporary LOB.
Action: Turn off parallelism for the query or underlying table
Cause: A loopback was created in the transaction before this operation.
Action: Do not use loopback when using pdml or insert direct load.
Cause: A table or index in a parallel query is referenced via a loopback connection.
Action: Do not use loopback connection when running a query in parallel.
Cause: First hard parse on slave given QC-supplied environment and parameters gave different plan from QC. Try again with outline.
Action: No external action. Internally used for outline-based reparse.
Cause: The parallel execution monitor process died.
Action: Wait for the process to restart.
Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to 0 in the multitenant container database (CDB) system.
Action: Set the PARALLEL_MAX_SERVERS parameter to non-zero value to ensure CDB system performance.
Cause: The ‘setsparseparent’ command specified a source file that was not sparse.
Action: Use a sparse file as the source file.
Cause: The ‘setsparseparent’ command specified a destination that was not backed by a sparse disk group.
Action: Use a destination backed by a sparse disk group.
Cause: The ‘setsparseparent’ command specified a child file that was not sparse.
Action: Use a sparse file as the child file.
Cause: The ‘setsparseparent’ command was not successful.
Action: Examine the accompanying error messages for details.
Cause: The parent information was not copied to the destination file.
Action: The ‘setsparseparent’ command can be used to set the parent.
Cause: An attempt was made to insert or update a column with a value which is too wide for the width of the destination column. The name of the column is given, along with the actual width of the value, and the maximum allowed width of the column. Note that widths are reported in characters if character length semantics are in effect for the column, otherwise widths are reported in bytes.
Action: Examine the SQL statement for correctness. Check source and destination column data types. Either make the destination column wider, or use a subset of the source column (i.e. use substring).
Cause: a locally managed database must have a temporary tablespace other than SYSTEM tablespace
Action: specify the default temporary tablespace when creating a locally managed database
Cause: in a locally managed database, default temporary tablespace must be TEMPORARY type
Action: n/a
Cause: in a dictionary managed database, default temporary tablespace must be SYSTEM or TEMPORARY type
Action: n/a
- ORA-12903: default temporary tablespace must be an ONLINE tablespace
- ORA-12904: default temporary tablespace cannot be altered to PERMANENT type
- ORA-12905: default temporary tablespace cannot be brought OFFLINE
- ORA-12906: cannot drop default temporary tablespace
- ORA-12907: tablespace string is already the default temporary tablespace
- ORA-12908: cannot specify SYSTEM as default temporary tablespace when creating database
- ORA-12909: TEMPORARY keyword expected
- ORA-12910: cannot specify temporary tablespace as default tablespace
Cause: attempt to assign a temporary tablespace to be a user’s default tablespace
Action: assign a permanent tablespace to be the default tablespace
Cause: attempt to assign a permanent tablespace to be a user’s temporary tablespace
Action: assign a temporary tablespace to be user’s temporary tablespace
Cause: attempt to assign a dictionary managed tablespace to be a user’s temporary tablespace
Action: Assign a locally managed temporary tablespace to be user’s temporary tablespace
Cause: Attemp to create dictionary managed tablespace in database which has system tablespace as locally managed
Action: Create a locally managed tablespace.
Cause: Attemp to migrate locally managed tablespace to dictionary managed type when the database has locally managed system tablespace.
Action: Command cannot be issued.
Cause: Attemp to alter dictionary managed tablespace to read write in database which has system tablespace as locally managed. This tablespace can only be dropped.
Action: Command cannot be issued.
Cause: An attempt was made to shrink a permanent tablespace or a dictionary managed tablespace.
Action: Check the tablespace type and issue the statement only on locally managed temporary tablespaces.
- ORA-12917: Invalid option specified for default permanent tablespace
- ORA-12918: Invalid tablespace type for default permanent tablespace
Cause: The tablespace is either dropped, temporary or undo
Action: Check the tablespace type and reissue the statement
Cause: An attemp was made to drop the default permanent tablespace
Action: Make a different tablespace as the default permanent tablespace and reissue the drop
Cause: ALTER DATABASE FORCE LOGGING command failed because the database is already in force logging mode.
Action: n/a
Cause: ALTER DATABASE NO FORCE LOGGING command failed because the database is not in force logging mode.
Action: n/a
Cause: There is a concurrent ALTER DATABASE FORCE LOGGING or ALTER DATABASE NO FORCE LOGGING command running in the system.
Action: Contact the database administrator who is responsible for the concurrent command.
Cause: An attempt to alter the specified tablespace temporary failed because the tablespace is in force logging mode.
Action: Put the tablespace out of force logging mode by ALTER TABLESPACE NO FORCE LOGGING command.
Cause: An attempt to alter the specified tablespace into force logging mode failed because it is already in force logging mode.
Action: n/a
Cause: An attempt to alter the specified tablespace out of force logging mode failed because it is not in force logging mode.
Action: n/a
Cause: In CREATE TABLESPACE, the FORCE LOGGING option was specified more than once.
Action: Remove all but one of the FORCE LOGGING options.
Cause: In CREATE TABLESPACE, the RETENTION option was specified more than once.
Action: Remove all but one of the RETENTION options.
Cause: In CREATE TABLESPACE, the ENCRYPTION option was specified more than once.
Action: Remove all but one of the ENCRYPTION options.
Cause: FORCE LOGGING or SET STANDBY NOLOGGING options were specified more than once.
Action: Remove all but one of the FORCE LOGGING or SET STANDBY NOLOGGING options.
Cause: A request from a remote database in the same Oracle Data Guard configuration to send data blocks to avoid or replace soft corrupt blocks due to nonlogged operations failed. This error is accompanied by additional errors that indicate the reason for the failure.
Action: Use any additional errors reported to identify and rectify the the underlying issue.
Cause: A request from a remote database in the same Oracle Data Guard configuration to send data blocks to avoid or replace soft corrupt blocks due to nonlogged operations could not connect to the requesting database. This error is accompanied by additional errors that indicate the reason for the failure.
Action: Use any additional errors reported to identify and rectify the the underlying issue.
Cause: The process performing replacement of nonlogged blocks failed to replace one or more blocks of the file indicated due to unexpected reasons such as a write failure reported by the operating system.
Action: Inspect any additional error messages and check the alert log for any messages related to Nonlogged Block Replacement (NBR).
Cause: The process performing replacement of nonlogged blocks received an error when attempting to connect (CONNECT) or make a fetch request (REQUEST) against the database identified by the given service. The database was expected to act as a source of replacement blocks.
Action: Use the reported error to identify the issue or inspect any additional error messages and check the alert log for any messages related to Nonlogged Block Replacement (NBR).
Cause: The process performing replacement of nonlogged blocks waited too long for a request sent to the remote database for a range of blocks to be completed.
Action: Check connectivity to the remote database or check the alert log at the remote database for problems reported by a transport task process (TTnn).
Cause: A database received data blocks requested by a recovery session that has now terminated. This error signals to the sending database that no more transfer requests should be made for the same RCVID.
Action: None required.
Cause: A request to use space in the data transfer cache was rejected because there was no free space left in the cache and space could not be freed up.
Action: Ensure that automatic SGA tuning is enabled using either MEMORY_TARGET or SGA_TARGET system parameters or specify a larger size for the system parameter DATA_TRANSFER_CACHE_SIZE.
Cause: A request to perform Nonlogged Block Replacement (NBR) recovery could not identify any other database in the Data Guard environment from which to request replacement blocks.
Action: Ensure there is a LOG_ARCHIVE_DEST_n parameter configured that identifies the primary or standby database from which requests for replacement blocks can be made.
Cause: DBVerify ran out of text buffer. The error was trapped internally by the system. DBVerify would return the result in text buffer and then resume checking.
Action: None
Cause: DBVerify encountered run-time error. The error signal was trapped internally by the system.
Action: None
Cause: A request to send data blocks to a recovery process failed because the source of the blocks is not on the same database incarnation as the site where the recovery is being performed.
Action: Use standard Oracle Data Guard procedures to synchronize the primary and standby databases. Standby media recovery automatically tries to resolve many of the remaining nonlogged blocks on the standby database. To resolve any remaining nonlogged blocks, use the RMAN RECOVER … NONLOGGED BLOCK command.
Cause: SYSTEM tablespace was specified as the default permanent during database creation.
Action: If default permanent tablespace is not specified,then SYSTEM will implicitly become the default permanent tablespace. Specify an alternate tablespace or omit the default tablespace clause and reissue the CREATE DATABASE statement
Cause: It is incorrect to alter the default permanent tablespace of a database to temporary type
Action: n/a
- ORA-12952: Control space growth in ASSM segment under concurrency
- ORA-12953: enable space scan optimization for clusters
- ORA-12961: cannot open database in read write mode on a read-only instance
Cause: An attempt was made to open the database on a read-only instance under the following 2 cases: 1) User explicitly specified read write option in the SQL command. 2) User forgot to explicitly specify read-only in which case, read write mode was assumed by default.
Action: User should specify the open mode as read-only.
Cause: An attempt was made to create a database on a read-only instance.
Action: Create database should only be attempted from a read write instance.
Cause: A read-only instance was the first instance to try to open a database.
Action: A database must have been opened by at least one read write instance for a read-only instance to be able to open it.
Cause: The last read write instance holding the database open closed it.
Action: There has to be at least one read write instance holding the database open for a read-only instance to hold it open.
Cause: An attempt was made to mount an enabled redo thread obtained as a user specified parameter.
Action: The parameter value should be changed to the thread number of a disabled thread.
Cause: There were no available disabled redo threads which could be used to mount on the current read-only instance.
Action: None
Cause: An attempt was made to mount a standby database on a read-only instance.
Action: This action is not allowed.
Cause: The system parameter for ping with no log force feature was set to true.
Action: The parameter should be set to false on a read-only instance.
Cause: An attempt was made to execute a disallowed ALTER DATABASE statement on a read-only instance.
Action: Only OPEN, CLOSE and CREATE TEMPFILE options are allowed for ALTER DATABASE statement on a read-only instance.
Cause: An attempt was made to close a pluggable database (PDB) on the last read/write instance while a read-only instance was holding it open.
Action: A PDB should be closed on all of the read-only instances before it can be closed on the last read/write instance.
Cause: An attempt was made to specify checkpoint option with SET UNUSED.
Action: Remove checkpoint option.
Cause: An attempt was made to drop a column from an object type table.
Action: This action is not allowed.
Cause: An attempt was made to drop a column from a nested table.
Action: This action is not allowed.
Cause: An attempt was made to drop all columns in a table.
Action: Ensure that at least one column remains in the table after the drop column operation.
Cause: An attempt was made to drop a column used as the partitioning key.
Action: This action is not allowed.
Cause: An attempt was made to drop column from a partition/subpartition on a read only tablespace.
Action: Set the tablespace to read write and resubmit statement.
Cause: An attempt was made to access a table with columns in partially dropped state (i.e., drop column operation was interrupted).
Action: Submit ALTER TABLE DROP COLUMNS CONTINUE to complete the drop column operation before accessing the table.
Cause: An attempt was made to combine drop column with other ALTER TABLE operations.
Action: Ensure that drop column is the sole operation specified in ALTER TABLE.
Cause: An attempt was made to drop a column from a system table.
Action: This action is not allowed
Cause: An invalid checkpoint interval specified in statement. Checkpoint interval must be between 0 and (2^31-1).
Action: Correct checkpoint interval and resubmit statement
Cause: Duplicate option specified in statement.
Action: Remove the duplicate option and resubmit statement.
Cause: An attempt was made to drop a column referenced by some constraints.
Action: Drop all constraints referencing the dropped column or specify CASCADE CONSTRAINTS in statement.
Cause: An attempt was made to drop a parent key column.
Action: Drop all constraints referencing the parent key column, or specify CASCADE CONSTRAINTS in statement.
Cause: An attempt was made to drop a column from a partition/subpartition on an offline tablespace.
Action: Bring the tablespace online and resubmit statement.
Cause: An attempt was made to repeat the drop column option in a single statement.
Action: Separate drop column options into different statements and resubmit statements.
Cause: An attempt was made to submit DROP COLUMNS CONTINUE statement while there are no partially dropped columns.
Action: Cannot submit this statement.
Cause: An attempt was made to drop a virtual column generated by the system.
Action: n/a
Cause: An attempt was made to drop a primary key column from an index- organized table.
Action: This action is not allowed.
- ORA-12998: Ignore errors during drop column from atb.c
- ORA-12999: cannot DROP or SET UNUSED a column that has been set unused
Cause: An attempt was made to DROP or SET UNUSED a column that has already been ‘set unused’.
Action: Use the DROP UNUSED COLUMNS option to remove the column.
Cause: The specified dimension was either smaller than 1 or greater than the number of dimensions encoded in the HHCODE.
Action: Ensure that the dimension number is between 1 and the maximum number of dimensions encoded in the HHCODE.