Oracle 12c R2 Error Codes and Solution Suggestions from ORA-00500 to ORA-00900
- ORA-00500: Listener registration process terminated with an error.
Cause: The listener registration process died.
Action: Warm start the instance.
Cause: The cleanup process died.
Action: Warm start the instance.
Cause: The manager process died.
Action: Warm start the instance.
Cause: A cleanup slave died.
Action: Warm start the instance.
Cause: The service monitor background process died.
Action: PMON will restart the background process shortly.
Cause: The generic background processing process 1 died.
Action: Warm start the instance.
Cause: The given Managed Global Area (MGA) index was not of the heap type.
Action: None
Cause: The cluster flash cache process died.
Action: Warm start the instance.
Cause: Cannot start process in a requested processor group when the NUMA feature is disabled.
Action: Start the process without requesting a NUMA processor group.
Cause: The process could not be started in the requested processor group.
Action: Start the process in another processor group.
Cause: User specified too many ^c handlers
Action: Remove some old handlers.
Cause: A prior error occurred on one of the instances in the cluster. Typically errors are caused by shared pool resource contention.
Action: Check for and resolve prior errors on all instances in the cluster. If there is shared pool resource contention, increase the SHARED_POOL_SIZE, DML_LOCKS, PROCESSES, TRANSACTIONS, CLUSTER_DATABASE_INSTANCES and PARALLEL_MAX_SERVERS initialization parameters.
- ORA-00574: osndnt: $CANCEL failure (break)
- ORA-00575: osndnt: $QIO failure (send out-of-band break)
- ORA-00576: in-band break protocol error
- ORA-00577: out-of-band break protocol error
- ORA-00578: reset protocol error
- ORA-00579: osndnt: server received malformed connection request
- ORA-00580: protocol versions do not match
- ORA-00581: osndnt: cannot allocate context area
- ORA-00582: osndnt: cannot deallocate context area
- ORA-00583: osndnt: $TRNLOG failure
- ORA-00584: cannot close connection
- ORA-00585: host name has incorrect form
- ORA-00586: osndnt: LIB$ASN_WTH_MBX failure
- ORA-00587: cannot connect to remote host
- ORA-00588: message from host was too short
- ORA-00589: message from host had incorrect data length
- ORA-00590: message from host had incorrect message type
- ORA-00591: incorrect number of bytes written
- ORA-00592: osndnt: $QIO failure (mailbox queue)
- ORA-00593: osndnt: $DASSGN failure (network device)
- ORA-00594: osndnt: $DASSGN failure (mailbox)
- ORA-00595: osndnt: $QIO failure (receive)
- ORA-00596: osndnt: $QIO failure (send)
- ORA-00597: osndnt: $QIO failure (mailbox requeue)
- ORA-00598: osndnt: $QIO failure (mailbox read)
- ORA-00600: internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string], [string], [string], [string], [string]
Cause: This is the generic internal error number for Oracle program exceptions. It indicates that a process has encountered a low-level, unexpected condition. The first argument is the internal message number. This argument and the database version number are critical in identifying the root cause and the potential impact to your system.
Action: Visit My Oracle Support to access the ORA-00600 Lookup tool (reference Note 600.1) for more information regarding the specific ORA-00600 error encountered. An Incident has been created for this error in the Automatic Diagnostic Repository (ADR). When logging a service request, use the Incident Packaging Service (IPS) from the Support Workbench or the ADR Command Interpreter (ADRCI) to automatically package the relevant trace information (reference My Oracle Support Note 411.1). The following information should also be gathered to help determine the root cause: – changes leading up to the error – events or unusual circumstances leading up to the error – operations attempted prior to the error – conditions of the operating system and databases at the time of the error Note: The cause of this message may manifest itself as different errors at different times. Be aware of the history of errors that occurred before this internal error.
Cause: The process monitor (PMON) database process ran into a lock conflict while trying to recover the processes.
Action: This is an internal issue. No action required.
Cause: An address violation was encountered.
Action: Report the issue as a bug.
Cause: An Oracle server session was in an unrecoverable state.
Action: Log in to Oracle again so a new server session will be created automatically. Examine the session trace file for more information.
Cause: An error occurred while processing a recursive SQL statement (a statement applying to internal dictionary tables).
Action: If the situation described in the next error on the stack can be corrected, do so; otherwise contact Oracle Support.
Cause: A call to deferred upi functions was made in non deferred mode
Action: Report as a bug.
Cause: An internal error or memory exception occurred while Oracle was applying redo to a data block.
Action: call Oracle Support
Cause: Internal error reserved for testing.
Action: call Oracle Support
Cause: Oracle process could not answer incoming connection
Action: If the situation described in the next error on the stack can be corrected, do so; otherwise contact Oracle Support.
Cause: A quarantine limit was reached and the instance was aborted.
Action: Restart the instance.
- ORA-00700: soft internal error, arguments: [string], [string], [string], [string], [string], [string], [string], [string], [string], [string], [string], [string]
Cause: Internal inconsistency that will not crash a process
Action: Report as a bug – the first argument is the internal error.
Cause: Attempt to alter or drop a database object (table, cluster, or index) which are needed for warmstarting the database.
Action: None
Cause: The reading version of the boostrap is incompatible with the current bootstrap version.
Action: Restore a version of the software that is compatible with this bootstrap version.
Cause: There are not enough row cache enqueues.
Action: Increase the row cache enqueue parameter and warm start the system.
Cause: Failure in processing bootstrap data – see accompanying error.
Action: Contact your customer support representative.
Cause: A previous attempt to start an instance was terminated.
Action: Shut down the instance completely, then restart it.
Cause: An attempt to change the block0 format of the specified file failed because the file is read-only or offline.
Action: Make the file read-write or bring the file online and set the BLK0_FMTCHG event.
Cause: An attempt to rename a tablespace failed because the new name is the same as the old name.
Action: No action required.
Cause: An attempt to rename a tablespace failed because the new name is invalid.
Action: Choose a valid new name and retry the command.
Cause: An attempt to rename the system tablespace failed.
Action: No action required.
Cause: ALTER DATABASE RESET COMPATIBILITY command has been de-supported since Oracle 10i.
Action: No action required.
Cause: An attempt to import a tablespace failed because the tablespace contains changes that require a newer software release or that violate the compatibility parameters.
Action: Use a version of the software that can understand the changes or relax the compatibility requirements in the initialization parameter file.
Cause: Reporting name of the feature for details of another error.
Action: See associated error message.
Cause: Oracle detected that the initialization parameter COMPATIBLE was not explicitly specified, and the compatibility of the database is lower than the default value of the COMPATIBLE parameter. In order to use the new compatible setting, the intialization parameter must be explicitly set by the user.
Action: Explicitly set the value of COMPATIBLE parameter either in PFILE or SPFILE, whichever is used.
Cause: ALTER DATABASE CONVERT command has been de-supported since Oracle 10i.
Action: No action required.
Cause: A deprecated ALTER DATABASE SET STANDBY was specified.
Action: No action required.
Cause: The user specified datafile size exceeded maximum file size.
Action: Please check REFERENCE for maximum size. Reduce the size and retry.
Cause: The user specified logfile size exceeded maximum logfile size.
Action: Please check REFERENCE for maximum size. Reduce the size and retry.
Cause: Either a write issued by Oracle was lost by the underlying operating system or storage system or an Oracle internal error occurred.
Action: The trace file shows the lost write location. Dump the problematic log file to see whether it is a real lost write. Contact Oracle Support Services.
Cause: The instance has already mounted and dismounted the database, which is only allowed once in its lifetime.
Action: Shut down the database.
Cause: An error occurred while obtaining the mirror resilvering status of a file.
Action: Refer to other error messages shown for additional details of the problem.
Cause: A data block write to storage was lost during normal database operation on the primary database.
Action: Shutdown the primary database and activate the physical standby database to failover. Call Oracle Support Services. See the Data Guard documentation for details.
Cause: A data block write to storage was lost during normal redo database operation on the standby database or during recovery on a primary database.
Action: Close the database and try the RECOVER MANAGED STANDBY DATABASE (on the standby database) or RECOVER DATABASE … FORCE START AT (on the primary database) statement starting at the SCN of the bad block that was printed already. See the Administrator’s Guide for details.
Cause: An error caused a data block mismatch with a log record.
Action: If running on a primary database in recovery mode, you may perform a point-in-time recovery to an earlier time. Otherwise, call Oracle Support Services. See the Administrator’s Guide for details.
Cause: A data block write to storage was lost during normal redo database operation on the standby database or during recovery on a primary database.
Action: Close the database and try the RECOVER MANAGED STANDBY DATABASE (on the standby database) or RECOVER DATABASE … FORCE START AT (on the primary database) statement starting at the SCN of the bad block that was printed already. See the Administrator’s Guide for details.
Cause: An internal error occurred.
Action: If running on a primary database in recovery mode, you may perform a point-in-time recovery to an earlier time. Otherwise, call Oracle Support Services. See the Administrator’s Guide for details.
Cause: The standby database was going through a role transition and the new primary database was not reopened in the configured timeout duration after switchover.
Action: Open the new primary database and try to connect again.
Cause: An error occurred while trying to remove lost write tracking.
Action: Check the system log for ERROR: or WARNING: for further information.
Cause: An error occurred while trying to suspend lost write tracking.
Action: Check the system log for ERROR: or WARNING: for further information.
Cause: Memory allocation failed.
Action: Ensure that enough memory including stack memory is available
Cause: An error occurred while trying to add lost write tracking; could not lookup target data file.
Action: This may be an internal error if the target data file exists.
- ORA-00764: The current transaction started on standby database and attempted to make an update after role transition.
Cause: The session, which started a transaction on the standby database and stayed alive after a role transition, attempted to do an update.
Action: The client should catch the exception and retry the transaction.
- ORA-00816: error message translation failed
- ORA-00820: Specified value of sga_max_size is too small, needs to be at least stringM
Cause: The specified value of sga_max_size is too small for the SGA to accommodate all of the necessary SGA components such as the log buffer, buffer pools, shared pool, etc.
Action: Set sga_max_size to the recommended value or reduce the values of any SGA component size parameters you have specified.
Cause: The specified value of sga_target is too small for the SGA to accommodate all of the necessary SGA components such as the log buffer, buffer pools, shared pool, etc.
Action: Set sga_target to the recommended value or reduce the values of any SGA component size parameters you have specified.
Cause: The Memory Management process died.
Action: Warm start instance
Cause: The specified value of sga_target is greater than sga_max_size.
Action: Increase sga_max_size to match up with sga_target or decrease sga_target to match up with sga_maxsize.
Cause: Could not set SGA_TARGET or MEMORY_TARGET due to current parameter settings.
Action: Check the other error messages for additional information.
Cause: SGA_TARGET or MEMORY_TARGET set with DB_BLOCK_BUFFERS set.
Action: Do not set SGA_TARGET, MEMORY_TARGET or use new cache parameters, and do not use DB_BLOCK_BUFFERS which is an old cache parameter.
Cause: SGA_TARGET or MEMORY_TARGET set for an ASM instance.
Action: Do not set SGA_TARGET or MEMORY_TARGET.
Cause: Attempted to shrink the SGA to the specified value but did not succeed because the SGA components could not be shrunk as they were already at their minimum sizes.
Action: Do not set sga_target to a value below the current value without first shrinking the individual SGA components.
Cause: Unable to set shared_pool_reserved_size to specified value if SGA_TARGET set, either because the specified value is too small, or because it is too large for the current internal size of shared pool. More details can be found in the alert log.
Action: If possible, do not set shared_pool_reserved_size without setting shared_pool_size if SGA_TARGET set. Examine the alert log for information about current internal size of shared pool, and valid range of values for shared_pool_reserved_size.
Cause: The user attempted to set statistics_level to BASIC with auto-tune SGA enabled which cannot be done because auto-tune SGA cannot work with statistics_level set to BASIC.
Action: Disable auto-tune SGA and try setting the statistics_level to BASIC again.
Cause: A database feature which needs STREAMS SGA was being used, however, the streams_pool_size parameter was not defined and the value of db_cache_size was too small to permit an automatic transfer of SGA to the streams pool from the buffer cache.
Action: Please set the parameter streams_pool_size or set SGA_TARGET.
Cause: The specified value of MEMORY_TARGET was greater than MEMORY_MAX_TARGET.
Action: Set MEMORY_TARGET less than or equal to MEMORY_MAX_TARGET.
Cause: The specified value of MEMORY_TARGET was less than the sum of the specified values for SGA_TARGET and PGA_AGGREGATE_TARGET.
Action: Set MEMORY_TARGET to at least the recommended value.
Cause: The specified value of SGA_TARGET was not compatible with current settings of PGA_AGGREGATE_TARGET and MEMORY_TARGET/MEMORY_MAX_TARGET.
Action: Set SGA_TARGET to be no more than the difference of MEMORY_TARGET/MEMORY_MAX_TARGET and PGA_AGGREGATE_TARGET. Also ensure that the current PGA memory used for non-auto workareas is low.
Cause: The specified value of PGA_AGGREGATE_TARGET was not compatible with current settings of SGA_TARGET and MEMORY_TARGET/MEMORY_MAX_TARGET.
Action: Set PGA_AGGREGATE_TARGET to be no more than the difference of MEMORY_TARGET/MEMORY_MAX_TARGET and SGA_TARGET.
Cause: MEMORY_TARGET parameter was not supported on this system as shmfs was disabled.
Action: Refer to documentation for a list of supported systems.
Cause: DB_BLOCK_BUFFERS was incompatible with SGA_TARGET and MEMORY_TARGET.
Action: Remove the incompatible parameter setting.
Cause: The parameter was larger than MEMORY_MAX_TARGET.
Action: Check the other error messages for additional information about the parameter. Set the parameter to a lower value than MEMORY_MAX_TARGET.
Cause: The parameter was larger than MEMORY_TARGET.
Action: Check the other error messages for additional information about the parameter. Set the parameter to a lower value than MEMORY_TARGET.
Cause: The MEMORY_TARGET parameter was not supported on this operating system or /dev/shm was not sized correctly on Linux.
Action: Refer to documentation for a list of supported operating systems. Or, size /dev/shm to be at least the SGA_MAX_SIZE on each Oracle instance running on the system.
Cause: Attempted to shrink MEMORY_TARGET to the specified value but did not succeed because the PGA and SGA components could not be shrunk.
Action: Do not set MEMORY_TARGET to a value below the current value without first shrinking the individual memory components.
Cause: MEMORY_TARGET/MEMORY_MAX_TARGET was set to a non-zero value and LOCK_SGA was also set
Action: Do not set MEMORY_TARGET or MEMORY_MAX_TARGET if LOCK_SGA is set to TRUE.
Cause: STATISTICS_LEVEL of BASIC was incompatible with SGA_TARGET and MEMORY_TARGET.
Action: Fix the incompatible parameter setting. Set STATISTICS_LEVEL to TYPICAL or ALL to use SGA_TARGET or MEMORY_TARGET.
Cause: SGA_TARGET value was more than MEMORY_MAX_TARGET value.
Action: Set SGA_TARGET to be less than MEMORY_MAX_TARGET.
Cause: PGA_AGGREGATE_TARGET value was more than MEMORY_MAX_TARGET value.
Action: Set PGA_AGGREGATE_TARGET to be less than MEMORY_MAX_TARGET.
Cause: SGA_MAX_SIZE value was more than MEMORY_TARGET value.
Action: Set SGA_MAX_SIZE to be less than MEMORY_TARGET.
Cause: The ASM rolling migration monitor process died.
Action: Warm start the instance.
Cause: SGA_MAX_SIZE value was more than MEMORY_MAX_TARGET value.
Action: Set SGA_MAX_SIZE to be less than MEMORY_MAX_TARGET.
Cause: The ASM IOServer Fence monitor process died.
Action: Warm start the instance.
Cause: PGA_AGGREGATE_TARGET value was too high for the current system global area (SGA) size and amount of physical memory available.
Action: Reduce the SGA size or increase the physical memory size.
Cause: PGA_AGGREGATE_TARGET value was greater than 50 percent the current value of PGA_AGGREGATE_LIMIT.
Action: Increase PGA_AGGREGATE_LIMIT or use a lower PGA_AGGREGATE_TARGET.
Cause: The current operation could not be performed on the same session.
Action: None
Cause: The SQL ID specified was invalid or did not exist.
Action: Retry with a valid SQL ID.
Cause: The instance ID specified was invalid.
Action: Retry with a valid instance ID.
Cause: The dedicated connection broker could not be enabled or disabled.
Action: Check the process trace file for the reason for failure.
Cause: The syntax for the nth CONNECTION_BROKERS specification was invalid.
Action: See the additional errors that were reported. Refer to the Oracle Database Reference manual for the correct syntax.
Cause: Multiple CONNECTION_BROKER specifications contained the same TYPE.
Action: Specify only one specification for each TYPE.