Oracle 12c R2 Error Codes and Solution Suggestions from ORA-09700 to ORA-09800
- ORA-09700: sclin: maximum number of latches exceeded
Cause: ORACLE wants to use more latches then available.
Action: increase INIT.ORA parameter latch_pages or decrease the amount of shared memory you are using.
Cause: PROCESSES INIT.ORA parameter exceeded.
Action: Decrease the PROCESSES parameter and restart.
Cause: The semaphore used for accessing latches could not be seized
Action: Send trace file to your customer support representative, along with information on reproducing the error.
Cause: The semaphore used for accessing latches could not be released
Action: Send trace file to your customer support representative, along with information on reproducing the error.
Cause: the ftok() library call failed in sstastcre().
Action: Verify that tasdef@.dbf file exists. If it does then this is a possible system failure. Perhaps System V compatibility is not enabled.
Cause: The semaphore used for accessing latches could not be initialized
Action: Send trace file to your customer support representative, along with information on reproducing the error.
Cause: get_process_stats system call returned an error. Possible OS error.
Action: Check additional information returned. Look for information in OS reference. Contact customer support.
Cause: The bind system call failed on the socket.
Action: Check additional information for OS error. Try connecting again.
Cause: The accept system call failed on the socket.
Action: Check additional information for OS error. Try connecting again.
Cause: The internal buffer is not big enough to hold the message read.
Action: Internal error. Contact customer support representative.
Cause: An existing connection has already been made from archmon to orasrv.
Action: Stop trying to connect.
Cause: An existing connection has already been made from log archiver to orasrv.
Action: Stop trying to connect.
Cause: The TXIPC driver cannot obtain the name of the PU. (Possible OS error)
Action: Check if the PUs are named (consistend).
Cause: Orasrv cannot obtain the name of the PU. (Possible OS error)
Action: Check if the PUs are named (consistend).
Cause: One Oracle process died while still holding a lamport latch.
Action: Exit (kill) all Oracle user processes. Shutdown (abort) and restart Oracle RDBMS kernel.
Cause: The internal limit on the number of user interrupt handlers has been exceeded.
Action: Reduce the number of simulataneous logons or reduce the number of user interrupt handlers.
Cause: Malloc() failed to allocate space to hold user interrupt handler.
Action: Possible memory resource shortage.
Cause: The handle passed to osncui is out of the valid range.
Action: Use a valid handle.
Cause: The vm_region system call failed to get virual memory region statistics.
Action: Check return code in sercerrno. Possible operating system failure.
Cause: Msg_receive system call returned an error. Internal error.
Action: Check return code in sercerrno. Port name is returned in sercose[0].
Cause: Msg_send system call returned an error. Internal error.
Action: Check return code in sercerrno. Port name is returned in sercose[0].
Cause: The mmap or write system call returned an error. Internal error.
Action: Contact Oracle support.
Cause: The mmap system call returned an error. Internal error.
Action: Contact Oracle support.
Cause: Error in system call vm_allocate. Failed to create SGA as a single shared memory segment.
Action: Check result code returned in sercerrno. Verify that the SGA attach address is valid.
Cause: The vm_allocate system call attached the SGA at an incorrect location.
Action: Verify that the SGA attach address is valid.
Cause: The call pws_detach to (Oracle helper) failed.
Action: Make sure the server is still active. Check the error code returned in sercerrno, and look for error messages in the server log file.
Cause: The pws_look_up call could not fork the (Oracle helper) 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: The pws_look_up could not find a port to (Oracle helper).
Action: Make sure the (Oracle helper) server has been started correctly by pws_look_up, and that the network name server is still running.
Cause: The port_rename system call failed; possible internal error.
Action: Check return code in sercerrno, report to Oracle customer support.
Cause: The call pws_attach to (Oracle helper) failed.
Action: Make sure the server is still active. Check the error code returned in sercerrno, and look for error messages in the server log file.
Cause: The port_allocate system call failed; possible resource exhaustion.
Action: Check return code in sercerrno, report to Oracle customer support.
Cause: Function was passed an invalid oracle process id.
Action: Internal error. Additional information indicates the invalid process id.
Cause: Function was passed an invalid oracle process id.
Action: Internal error. Contact Oracle support.
Cause: The port_allocate system call failed.
Action: Possible system resource shortage; check the error code in sercerrno.
Cause: osnpns could not find the given named port in the name server.
Action: Check the error code in sercerrno. Make sure the shadow process and network name server are still running.
Cause: The port_allocate system call failed.
Action: Possible system resource shortage; check the error code in sercerrno.
Cause: The netname_check_in call failed.
Action: Check the error code in sercerrno. Make sure the network name server is running.
Cause: The msg_receive system call failed, or received a bad message.
Action: Internal error. Report the error code returned in sercerrno.
Cause: The Pipe driver could not send a break message to the ORACLE shadow process break thread.
Action: Contact your customer support representative.
Cause: The call pws_stop_instance to (Oracle helper) failed.
Action: Make sure the server is still active. Check the error code returned in sercerrno, and look for error messages in the server log file.
Cause: A failure was detected while translating the value of ORACLE_SID.
Action: Make sure ORACLE_SID is defined, and that it is of legal length.
Cause: The Mach driver failed to exchange port information with the other side of the connection. Either msg_send (sercose[0] == 1) or msg_receive (sercose[0] == 2) failed.
Action: Check return code in sercerrno. Make sure both sides of the connection are still running.
Cause: The Mach driver could not access the oracle executable.
Action: Check the permissions on the ORACLE executable and each component of the ORACLE_HOME/bin path.
Cause: The Mach driver could not fork the oracle shadow 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: The Mach driver failed to allocate enough vm space for its I/O buffers.
Action: Decrease the value of buffer_size parameter in the Two-Task driver hoststring.
Cause: The msg_send system call failed while flushing the Mach driver’s send buffer.
Action: Internal error. Contact your customer support representative.
Cause: The msg_receive system call returned a failure code while waiting for a message in the Mach driver.
Action: Internal error. Contact your customer support representative.
Cause: The Mach driver could not send a break message to the ORACLE shadow process break thread.
Action: Internal error. Contact your customer support representative.
Cause: The pws_look_up routine failed to translate the name of the (Oracle helper) executable.
Action: Make sure ORACLE_SID and ORACLE_HOME are set and correct. Additional information gives the translation error code.
Cause: The msg_send sytem call failed while sending a Mach driver break.
Action: Internal error. Contact your customer support representative.
Cause: The Mach driver received a message having an unrecognizable message type.
Action: Internal error. Contact your customer support representative.
Cause: The Mach driver received a message having an unrecognizable message type.
Action: Internal error. Contact your customer support representative.
Cause: The Mach driver could not send a break message to the ORACLE shadow process break thread.
Action: Internal error. Contact your customer support representative.
Cause: The Mach two-task driver could not reset the connection.
Action: Internal error. Contact your customer support representative.
Cause: The pws_look_up call could not access the (Oracle helper) executable.
Action: Check the permissions on the (Oracle helper) executable and each component of the ORACLE_HOME/bin path.
Cause: The pipe driver could not send a break message to the ORACLE shadow process break thread.
Action: Internal error. Contact your customer support representative.
Cause: The routine failed to allocate or set the task’s notify port.
Action: Possible operating system error. Contact Oracle support.
Cause: The port_allocate system call failed; system resources might be exhausted.
Action: Possible operating system error. Contact Oracle support.
Cause: Open system call returned an error.
Action: Check errno.
Cause: Processing option passed is of incorrect format.
Action: Consult your IUG for permissible formats.
Cause: Read system call returned an error.
Action: Check errno. Verify file exists.
Cause: Read system call returned an error.
Action: Check errno. Verify file exists.
Cause: Close system call returned an error.
Action: Check errno.
Cause: Additional information indicates error returned from sltln.
Action: Check additional information.
Cause: Malloc system call returned an error. The system might have run out of heap space.
Action: Check additional information for the OS error.
Cause: The length of the name of the user being looked up is longer than size of the buffer provided by the calling routine.
Action: This is an internal error. Contact Oracle Support Services.
Cause: The length of the name of the role being looked up is longer than size of the buffer provided by the calling routine.
Action: This is an internal error. Contact Oracle Support Services.
Cause: The allocation of memory for an internal structure used to hold a role descriptor failed.
Action: Check the UNIX error number for a possible operating system failure.
Cause: The allocation of memory for an internal buffer used to hold the name of a role failed.
Action: Check the UNIX error number for a possible operating system failure.
Cause: The operating system would not allow the retrieval of this process’ privileges.
Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.
Cause: The comparison of two binary labels failed.
Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.
Cause: ORACLE was unable to get a label attached to a file.
Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.
Cause: ORACLE was unable to get the sensitivity label for a process.
Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.