Oracle 12c R2 Error Codes and Solution Suggestions from ORA-00400 to ORA-00500
- ORA-00400: invalid release value string for parameter string
Cause: The release level given for the specified init parameter is invalid.
Action: Correct the parameter value in the parameter file and retry.
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.
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 init file.
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.
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 filename is accessable.
Cause: Reporting a type associated with another error.
Action: See accompanying error
Cause: 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: Shutdown and startup with a higher compatibility setting.
Cause: Another instance executing software at a different point release already has the database mounted.
Action: Shutdown all instances then startup with the new software.
Cause: Reporting the parameter that resulted in the compatibility error.
Action: Shutdown and startup with a higher compatibility setting.
Cause: This is due to migrating from an older release of Oracle with tablespaces created using AUTO SEGMENT SPACE MANAGEMENT. To open the database, the COMPATIBLE parameter needs to be set to the specified value.
Action: Shutdown and startup with the specified compatibility setting.
Cause: The required number of sessions for the PROCESSES parameter was greater than the maximum supported value.
Action: Decrease the required number of processes and start the instance.
- ORA-00436: ORACLE is not licensed. Contact Oracle Corp. for assistance
- ORA-00437: ORACLE feature is not licensed. Contact Oracle Corp. for assistance
Cause: ORACLE feature is not licensed.
Action: Contact ORACLE for assistance.
Cause: The specified option is not installed.
Action: Purchase and install the option.
Cause: The specified feature is not enabled.
Action: Do not attempt to use this feature.
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.
Cause: Usually due to a bad (or non-existent) background process image.
Action: Get a good background process image.
Cause: The specified process did not start after the specified time.
Action: Ensure that the background did not die and leave a trace file.
Cause: The background process specified started up AFTER the RDBMS was already running.
Action: If nobody at your site started the process, then this is an internal error.
Cause: One of the background processes died unexpectedly.
Action: Warm start the system.
Cause: One of the background processes completed normally (i.e. exited). The background process thinks that somebody asked it to exit.
Action: Warm start the system.
Cause: A foreground process needing service from a background process has discovered the process died.
Action: Consult the error code, and the trace file for the process.
Cause: The specified process did not start.
Action: Consult the error code, and the trace file for the process.
Cause: The foreground process for the new connection did not start.
Action: Reconnect to Oracle.
Cause: The foreground process for the new connection did not start.
Action: Reconnect to Oracle.
Cause: The background process that was being messaged was dead or its incarnation was invalid.
Action: Restart the background process.
Cause: An attempt to spawn a background process that was already running failed.
Action: None
Cause: The state of the background process was not cleaned up.
Action: None
Cause: Prespawn was not enabled.
Action: None
Cause: The process pool was not found.
Action: Verify the process pool name.
Cause: The process pool was already started.
Action: None
Cause: The process pool was not started.
Action: None
Cause: Invalid configuration values were specified for the process pool.
Action: Verify the configuration values.
Cause: Managed Global Area(MGA) namespace was already opened.
Action: None
Cause: Managed Global Area(MGA) namespace shared handle was not valid.
Action: None
Cause: Managed Global Area(MGA) namespace private handle was not valid.
Action: None
Cause: Processes were still attached to Managed Global Area(MGA) namespace.
Action: None
Cause: Segments were still attached to Managed Global Area(MGA) namespace.
Action: None
Cause: Managed Global Area(MGA) segment information was not valid.
Action: None
Cause: There was already an attachement to the Managed Global Area(MGA) handle.
Action: None
Cause: There was no attachement to the Managed Global Area(MGA) handle.
Action: None
Cause: The checkpoint process died
Action: Warm start instance
Cause: The log writer process died
Action: Warm start instance
Cause: The database writer process died
Action: Warm start instance
Cause: The process cleanup process died
Action: Warm start instance
Cause: The archive process died
Action: Warm start instance
Cause: The system cleanup process died
Action: Warm start instance
Cause: The system tracing process died
Action: Warm start instance
Cause: The distributed transaction (two-phase commit) recovery process died.
Action: Warm start instance
Cause: A materialized view refresh process died
Action: PMON will restart SNP process shortly. If SNP process does not get started, contact Oracle support.
Cause: SMON was unable to service the requests due to error in cleanup of resources
Action: Warm start instance
Cause: The RVWR process died
Action: Warm start instance
Cause: A system lock process died
Action: Warm start instance
Cause: The global enqueue service monitor process died
Action: Warm start instance
Cause: A global enqueue service daemon process died
Action: Warm start instance
Cause: One of the background processes did not exit normally at or near the time of shutdown.
Action: Use shutdown abort.
Cause: A global cache service process died
Action: Warm start instance
Cause: A global diagnostic process died
Action: Wait for process to restart
Cause: An ASM background process died.
Action: Warm start instance. Also check that ASM Instance is running.
Cause: The change tracking process died
Action: Warm start instance
Cause: The ASM rebalance coordinator process died.
Action: Warm start instance.
Cause: An ASM rebalance worker process died.
Action: Wait for process to restart.
Cause: The process spawner died
Action: Warm start instance
Cause: The RAC Management Process died
Action: n/a
Cause: A global transaction background process died.
Action: Warm start instance
Cause: The ASM disk group monitor process died
Action: Warm start instance
- ORA-00494: enqueue string held for too long (more than string seconds) by ‘inst string, osid string‘
Cause: The specified process did not release the enqueue within the maximum allowed time.
Action: Reissue any commands that failed and contact Oracle Support Services with the incident information.
Cause: The generic background processing process died.
Action: Warm start the instance.
Cause: The LM heartbeat monitor process died.
Action: Warm start the instance.
Cause: The Cell automation manager process terminated with error.
Action: PMON will restart XDMG process shortly. If XDMG process does not restart, contact Oracle Support Services.
Cause: The Cell automation worker actions process terminated with error.
Action: PMON will restart XDWK process shortly. If XDWK process does not restart, contact Oracle Support Services.
Cause: The Cell automation manager process repeatedly failed to initialize.
Action: Examine the alert log for the reason prior attempts to start XDMG failed. If it is due to user error or bad configuration, fix it and restart the instance. Otherwise, contact Oracle Support Services.
Cause: The listener registration process died.
Action: Warm start the instance.