Oracle 12c R2 Error Codes and Solution Suggestions from ORA-07400 to ORA-07500
- ORA-07400: slemtr: translated name for the message file is too long.
Cause: The name for the message file overflows internal buffer.
Action: Try making the complete path-name of the message file shorter by reorganizing the directory hierarchy.
Cause: The system failed to restore user exception handlers.
Action: Check errno and sercose[0] for the signal number that failed.
Cause: The system failed to restore user signal handlers.
Action: Check errno and sercose[0] for the signal number that failed.
Cause: The db_writers parameter in INIT.ORA exceeds the system-dependent maximum or is less than 0.
Action: Change the db_writers parameter in INIT.ORA.
Cause: The master database writer timed out waiting for a write or close to complete. One of the database writers may have stopped running.
Action: Check all database writer trace files. Shut down the database and try to warm start.
Cause: The system failed to setup an alternate signal stack.
Action: Check errno and sercose[0] for the location where it failed.
Cause: An impossible request for binary to decimal conversion was made.
Action: This conversion cannot be performed.
Cause: An impossible request for binary to decimal conversion was made
Action: This conversion cannot be performed.
Cause: An impossible request for binary to decimal conversion was made.
Action: This conversion cannot be performed.
Cause: An impossible request for decimal to binary conversion was made.
Action: This conversion cannot be performed.
Cause: An impossible request for decimal to binary conversion was made.
Action: This conversion cannot be performed.
Cause: The supplied buffer is not big enough to hold the full path name.
Action: The construction of the full path name cannot be performed.
Cause: One of the database writer processes could not locate its entry in the SGA.
Action: Contact customer support.
Cause: Malloc() failed to allocate buffer for storing ORACLE_PATH.
Action: System has run out of heap space. Additional information indicates errno.
Cause: The slpath routine is given a maximum length buffer to expand the name into. An overflow of this buffer occurred.
Action: Possible internal error. Check output buffer length stored in sercose[0] and constructed pathname length in sercose[1].
Cause: One or more of the database writer processes is no longer running.
Action: Check the trace files for the database writers. Shut down the database and try to warm start.
Cause: An error occurred when the database writer called the system timing function.
Action: Check the database writer trace file. Shut down database and try to warm start.
Cause: An error occurred when the database writer called the system timing function.
Action: Check the database writer trace file. Shut down database and try to warm start.
Cause: An oracle error occurred when translating the location of the dump file.
Action: Check the oracle error code.
Cause: An oracle error occurred when translating the location of the dbs directory.
Action: Check additional information for the error returned from sltln.
Cause: Chdir system call returned an error. Possible permission problems.
Action: Check additional information for the OS error code.
Cause: The server process was unable to fork a child process.
Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient.
Cause: An attempt was made to make a process sleep when it was already sleeping. This platform does not support this capability.
Action: Try the SLEEP command when the process is not sleeping.
Cause: The wakeup monitor process died.
Action: Warm start instance.
Cause: An improperly aligned function address was specified.
Action: Use a properly aligned function address.
Cause: An invalid function address was specified.
Action: Use a valid function address.
Cause: A nonexistent or an invalid function name was specified.
Action: Use a valid function name.
Cause: An invalid function name/address was specified.
Action: Use a valid function name/address.
Cause: An operating system exception occurred which should result in the creation of a core file. This is an internal error.
Action: Visit My Oracle Support to access the ORA-07445 Lookup tool (reference Note 7445.1) for more information regarding the specific ORA-07445 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 directory specified as the value for the stated parameter could not be used.
Action: Make sure the directory you have specified is a valid directory/file specification.
Cause: Oracle failed to create a shared arena file.
Action: Use sercerrno field to determine cause of failure.
Cause: Oracle attempted to create more shared arena files than permitted.
Action: Raise the value for max_arena in INIT.ORA.
Cause: Oracle failed to acquire a shared arena lock.
Action: Check result code in sercerrno to determine the cause of failure.
Cause: kstat library returned an error. Possible OS failure
Action: Check result code in sercose[0] for more information.
Cause: User tried to load a resource manager plan that does not exist.
Action: Use a resource manager plan that exists in the data dictionary.
Cause: User tried to load a resource manager plan schema that does not contain the OTHER_GROUPS group.
Action: Use a resource manager plan schema that contains the OTHER_GROUPS group.
Cause: User session queued for longer than maximum specified queue queue duration time for consumer group.
Action: Re-submit job at a later time or increase queue timeout.
Cause: User attempted to execute an operation whose estimated execution time exceeds the limit specified for the consumer group.
Action: Execute job on behalf of another group, or increase limit.
Cause: An attempt was made to turn on the Resource Manager when the database was closed.
Action: Open the database and try again.
Cause: An attempt was made to set the _INTERNAL_RESOURCE_MANAGER_PLAN parameter, however this failed because the current RESOURCE_MANAGER_PLAN has the FORCE prefix.
Action: Remove the FORCE prefix from the RESOURCE_MANAGER_PLAN parameter.
Cause: An attempt was made to set the RESOURCE_MANAGER_PLAN parameter, however, this failed because the database was quiesced.
Action: Unquiesce the database.
Cause: An attempt was made to internally restore the RESOURCE_MANAGER_PLAN parameter to the value before it was internally set. This failed because the current plan was set by the user and therefore did not need to be restored.
Action: No action needed.
Cause: An attempt was made to internally set the RESOURCE_MANAGER_PLAN parameter, however, this failed because the current RESOURCE_MANAGER_PLAN has the FORCE prefix.
Action: Remove the FORCE prefix from the RESOURCE_MANAGER_PLAN parameter.
Cause: The mset routine returned an error. Semaphore may not exist.
Action: Check result code in sercerrno. Semaphore number returned in sercose[0].
Cause: The mclear routine returned an error. Semaphore may not exist.
Action: Check result code in sercerrno. Semaphore number returned in sercose[0].
Cause: The cluster_status system call failed to get status information for the current cluster.
Action: Check result code in sercose[0]. Possible operating system failure.
Cause: Unable to expand out ?/dbs/sgadef@.dbf file name.
Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are properly set. Check error number returned from sltln in sercose[0].
Cause: open failed when opening the file ?/dbs/sgadef@.dbf
Action: Check errno. Possible permission problem. Verify that the file ?/dbs/sgadef@.dbf exists.
Cause: Read had an error when reading sgadef.dbf file.
Action: Check errno. Verify file exists, and is correct size.
Cause: An error occurred in close, while closing the file “?/dbs/sgadef@.dbf”
Action: Check errno. Possible operating system error.
Cause: The vm_statistics system call failed to get virtual memory statistics.
Action: Check result code in sercerrno. Possible operating system failure.
Cause: The vm_mapmem system call failed to get mapped memory statistics.
Action: Check result code in sercerrno. Possible operating system failure.
Cause: Lock manager must be initialized before converting locks.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_stat_lock failed.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_open or lm_open_convert failed.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: When creating an instance, snlmini could not change the permissions on ?/dbs/sgalm.dbf
Action: Contact your customer support representative.
Cause: lm_attach failed to attach to lock manager instance.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_create failed to create lock manager instance.
Action: Check permissions on ?/dbs, and remove ?/dbs/sgalm.dbf if it exists, then retry.
Cause: lm_convert failed to convert(get) lock.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_convert failed to put lock value.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_open failed.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_convert failed to get lock value.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_create failed.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: Lock manager must be initialized before releasing locks.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_stat_lock failed during lock release/cancel.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_convert failed during lock release/cancel.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_cancel failed during lock release/cancel.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_close failed during lock release/cancel.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: An error was encountered releasing the lock.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: Unknown or unexpected error code.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_wait failed.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: lm_post failed.
Action: Check result code in sercerrno. Possible lock manager failure.
Cause: 1. The trace file could not be created for writing. 2. The trace file is a symbolic link.
Action: 1. Check if the dump directory exists and whether it is writable. 2. Remove the symbolic link.
Cause: The rescheduling driver /dev/resched is not found or is not working properly.
Action: Check installation of the ORACLE rescheduling driver in the AIX kernel.
Cause: The rescheduling driver /dev/resched is not open. This is an internal error and should not occur.
Action: Contact your customer support representative.