Below are the list of Oracle ORA message from ORA-00401 to ORA-00816. You can find the cause and actions from each of the message accordingly.
| ORA MESSAGE | CAUSE / ACTION |
|---|---|
| ORA-00401 the value for parameter string is not supported by this release | Cause: The value specified cannot be supported by this release of the software. Action: Choose an appropriate value or remove the parameter value to use the default value. |
| ORA-00402 database changes by release string cannot be used by release string | Cause: Changes have been made to the database 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 file. |
| ORA-00403 string (string) is not the same as other instances (string) | Cause: Another instance has set the COMPATIBLE or COMPATIBLE NO RECOVERY parameters differently than this instance. Action: Change the parameters of the current instance to match other instances already running. |
| ORA-00404 Convert file not found: 'string' | Cause: The file used for converting the database from V7 to V8 could not be found. Action: Verify that the migration process has been started on this database and that the convert file name is accessible. |
| ORA-00405 compatibility type "string" | Cause: Reporting a type associated with another error. Action: See the accompanying error. |
| ORA-00406 COMPATIBLE parameter needs to be string or greater | Cause: The value of the COMPATIBLE initialization parameter is not high enough to allow the operation. Allowing the command would make the database incompatible with the release specified by the current COMPATIBLE parameter. Action: Shut down and restart with a higher compatibility setting. |
| ORA-00407 rolling upgrade from release string.string to string.string is not allowed | Cause: Another instance executing software at a different point release already has the database mounted. Action: Shut down all instances then restart with the new software. |
| ORA-00408 parameter string is set to TRUE | Cause: Reporting the parameter that resulted in the compatibility error. Action: Shut down and restart with a higher compatibility setting. |
| ORA-00409 COMPATIBLE needs to be string or higher to use AUTO SEGMENT SPACE MANAGEMENT | Cause: This is due to upgrading from an older release of Oracle with tablespaces created using automatic segment-space management. To open the database the COMPATIBLE parameter needs to be set to the specified value or higher. Action: Shut down and start up with the specified compatibility setting. |
| ORA-00436 ORACLE is not licensed. Contact Oracle Corp. for assistance | Cause: This installed Oracle software is not licensed to run on this CPU. This can also occur if Oracle software has been installed incorrectly for example with the wrong licensing codes. Action: Check that Oracle is installed correctly. Then contact Oracle Support Services. |
| ORA-00437 ORACLE feature is not licensed. Contact Oracle Corp. for assistance | Cause: This installed Oracle feature is not licensed to run on this CPU. This can also occur if Oracle software has been installed incorrectly for example with the wrong licensing codes. Action: Check that Oracle is installed correctly. Then contact Oracle Support Services. |
| ORA-00438 string Option not installed | Cause: The specified option is not installed. Action: Either avoid calling the option or purchase and install the option. |
| ORA-00439 feature not enabled: string | Cause: The specified feature is not enabled. Action: Do not attempt to use this feature. |
| ORA-00443 background process "string" did not start | Cause: The specified process did not start. Action: Ensure that the executable image is in the correct place with the correct protections and that there is enough memory. |
| ORA-00444 background process "string" failed while starting | Cause: Usually due to a bad (or non-existent) background process image. Action: Get a good background process image. |
| ORA-00445 background process "string" did not start after string seconds | Cause: The specified process did not start after the specified time. Action: Ensure that the background did not die and leave a trace file. |
| ORA-00446 background process started when not expected | Cause: The background process specified started after Oracle was already running. Action: Check the accompanying messages if any and the background process trace file. Correct the problem mentioned in the other messages. If no user on site started the process report the message to Oracle Support Services. |
| ORA-00447 fatal error in background process | Cause: One of the background processes died unexpectedly. Action: Restart the system. Check and if necessary correct the problem indicated by the background trace file in BACKGROUND_DUMP_DEST. |
| ORA-00448 normal completion of background process | Cause: One of the background processes completed normally as requested by the user. Action: If you are solving a problem check for other messages and the background process trace file. Correct the problem mentioned in the other messages. Then shut down and restart Oracle. |
| ORA-00449 background process 'string' unexpectedly terminated with error string | Cause: A foreground process needing service from a background process has discovered the process died. Action: Refer to the message code given in the message and the trace file for the foreground and the background processes. |
| ORA-00470 LGWR process terminated with error | Cause: The Log Writer process terminated abnormally. Action: Check the accompanying messages and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages check the trace file for the mentioned process until the root message is found. |
| ORA-00471 DBWR process terminated with error | Cause: The Database Writer process terminated abnormally. Action: Check the accompanying messages and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages check the trace file for the mentioned process until the root message is found. |
| ORA-00472 PMON process terminated with error | Cause: The Process Monitor process terminated abnormally. Action: Check the accompanying messages and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages check the trace file for the mentioned process until the root message is found. |
| ORA-00473 ARCH process terminated with error | Cause: The Archiver process terminated abnormally. Action: Check the accompanying messages if any and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages check the trace file for the mentioned process until the root message is found. |
| ORA-00474 SMON process terminated with error | Cause: The System Monitor process terminated abnormally. Action: Check the accompanying messages if any and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages check the trace file for the mentioned process until the root message is found. |
| ORA-00475 TRWR process terminated with error | Cause: The system tracing process terminated abnormally. Action: Restart the instance. |
| ORA-00476 RECO process terminated with error | Cause: The distributed transaction (two-phase commit) recovery process terminated abnormally. Action: Restart the instance. |
| ORA-00477 SNP* process terminated with error | Cause: A materialized view refresh process terminated abnormally. Action: PMON will restart SNP process shortly. If SNP process does not get started contact Oracle Support Services. |
| ORA-00478 SMON process terminated due to error string | Cause: SMON was unable to service the requests due to an error in cleanup of resources. Action: Warm start the instance. |
| ORA-00480 LCK* process terminated with error | Cause: One Lock process terminated abnormally. Action: Check the accompanying messages if any and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages check the trace file for the mentioned process until the root message is found. |
| ORA-00481 LMON process terminated with error | Cause: The global enqueue service monitor process terminated abnormally. Action: Restart the instance. |
| ORA-00482 LMD* process terminated with error | Cause: A global enqueue service daemon process terminated abnormally. Action: Restart the instance. |
| ORA-00483 During shutdown a process abnormally terminated | Cause: One of the background processes did not exit normally at or near the time of shutdown. Action: Use the SHUTDOWN ABORT command. Check the accompanying messages if any and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages check the trace file for the mentioned process until the root message is found. |
| ORA-00484 LMS* process terminated with error | Cause: A global cache service process terminated abnormally. Action: Warm start the instance. |
| ORA-00485 DIAG process terminated with error string | Cause: A global diagnostic process died. Action: Wait for the process to restart. |
| ORA-00568 Maximum number of interrupt handlers exceeded | Cause: The number of registered interrupt handling routines for when the break key is entered exceeds the maximum allowed. Action: Reduce the number of registered interrupt handlers. |
| ORA-00600 internal error code arguments: [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. Causes of this message include: -timeouts -file corruption -failed data checks in memory -hardware / memory or I/O errors -incorrectly restored files The first argument is the internal message number. Other arguments are various numbers / name and character strings. The numbers may change meanings between different versions of Oracle. Action: Report this error to Oracle Support Services after gathering the following information: -events that led up to the error -the operations that were attempted that led to the error -the conditions of the operating system and databases at the time of the error -any unusual circumstances that occurred before receiving the ORA-00600 message -contents of any trace files generated by the error -the relevant portions of the Alter files 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. |
| ORA-00601 cleanup lock conflict | Cause: The Process Monitor encountered a lock conflict while trying to recover processes. This is an internal error message not usually issued. Action: Contact Oracle Support Services. |
| ORA-00602 internal programming exception | Cause: Internal programming exception occurred. Action: Report this error as a program bug to Oracle Support Services. |
| ORA-00603 ORACLE server session terminated by fatal error | Cause: An Oracle Server session is 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. |
| ORA-00604 error occurred at recursive SQL level string | 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 Services. |
| ORA-00606 Internal error code | Cause: A call to deferred UPI functions was made in non-deferred mode. Action: Contact Oracle Support Services. |
| ORA-00607 Internal error occurred while making a change to a data block | Cause: An internal error or memory exception occurred while Oracle was applying redo to a data block. Action: Contact Oracle Support Services. |
| ORA-00701 object necessary for warmstarting database cannot be altered | Cause: An attempt was made to alter or drop a database object (table / cluster or index) defined in the control file's bootstrap segment and needed to warm start the database. Action: Correct the spelling of the object name or remove it from the ALTER or DROP statement. |
| ORA-00702 bootstrap verison 'string' inconsistent with version 'string' | Cause: The version of the bootstrap data is incompatible with the current version of the software. Action: Restore a version of the software that is compatible with the datafiles. |
| ORA-00703 maximum number of row cache instance locks exceeded | Cause: There are not enough row cache enqueues. Action: Increase the value of the ROW CACHE ENQUEUE parameter and restart the system. |
| ORA-00704 bootstrap process failure | Cause: Failure in processing bootstrap data. Refer to the accompanying messages for more information about the cause of the problem. Action: Correct the problems mentioned in the other messages. If the problem persists contact Oracle Support Services. |
| ORA-00705 inconsistent state during start up; shut down the instance then restart it | Cause: A previous attempt to start an instance was terminated. Action: Shut down the instance completely and then restart it. |
| ORA-00706 error changing format of file 'string' | 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. |
| ORA-00816 error message translation failed | Cause: There is an internal error where a routine was unable to translate a message code. Action: Contact Oracle Support Services. |
