Oracle 11g Error Codes and Solution Suggestions from ORA-09300 to ORA-09800

Posted on by Fatih Acar

Oracle 11g Error Codes and Solution Suggestions from ORA-09300 to ORA-09800

ORA-09300: osncon: unable to connect, DPMI not available
Cause: Unable to detect the presence of DPMI
Action: Restart Windows and retry
ORA-09301: osncon: local kernel only supported in standard mode
Cause: An attempt was made to connect to S: while in enhanced mode
Action: Restart Windows in standard mode
ORA-09310: sclgt: error freeing latch
Cause: Internal error
Action: See OSD error accompanying this message
ORA-09311: slsleep: error temporarily suspending process
Cause: May be out of resources
Action: See OSD error accompanying this message
ORA-09312: slspool: error spooling file to printer
Cause: Could be out of resources
Action: See OSD error accompanying this message
ORA-09313: slsprom: error prompting user
Cause: May be out of resources
Action: See OSD error accompanying this message
ORA-09314: sltln: error translating logical name
Cause: Internal buffer may have overflowed
Action: See OSD error accompanying this message
ORA-09315: sql2tt: two-task error translating ORACLE_EXECUTABLE
Cause: Internal error
Action: See OSD error accompanying this message
ORA-09316: szrpc: unable to verify password for role
Cause: OS roles may not be supported for this platform
Action: See OSD error accompanying this message
ORA-09317: szprv: insufficient privileges
Cause: The password specified is invalid
Action: See OSD error accompanying this message
ORA-09318: slkhst: unable to host out to operating system
Cause: There might not be enough memory for the command or hosting out may not be supported on this platform
Action: See OSD error accompanying this message
ORA-09319: slgtd: unable to obtain the current date and time
Cause: The system time might be set incorrectly
Action: See OSD error accompanying this message
ORA-09320: szrfc: unable to obtain the list of valid OS roles
Cause: OS roles may not be supported on this platform
Action: See OSD error accompanying this message
ORA-09321: slzdtb: unable to convert zoned decimal to binary
Cause: internal error
Action: See OSD error accompanying this message
ORA-09322: slpdtb: unable to convert packed decimal to binary
Cause: internal error
Action: See OSD error accompanying this message
ORA-09330: Session terminated internally by Oracle or by an Oracle DBA
Cause: Oracle to terminate that session after about a minute. This message also appears in the trace file if a shutdown abort is performed.
Action: None
ORA-09340: Specified ORACLE_SID is either invalid or too long
Cause: ORACLE_SID must be at the most 4 alphanumeric characters.
Action: None

ORA-09341: scumnt: unable to mount database
Cause: Another instance is currently mounting the database
Action: None
ORA-09342: Detached process terminated by Oracle during shutdown abort
Cause: The user performed a shutdown abort.
Action: None
ORA-09344: spsig: error signalling thread
Cause: This function may not be implemented.
Action: None
ORA-09350: Windows 32-bit Two-Task driver unable to allocate context area
Cause: See OSD error accompanying this message
Action: None
ORA-09351: Windows 32-bit Two-Task driver unable to allocate shared memory
Cause: See OSD error accompanying this message
Action: None
ORA-09352: Windows 32-bit Two-Task driver unable to spawn new ORACLE task
Cause: See OSD error accompanying this message
Action: None
ORA-09353: Windows 32-bit Two-Task driver unable to open event semaphore
Cause: See OSD error accompanying this message
Action: None
ORA-09354: Windows 32-bit Two-Task driver: ORACLE task unexpectedly died
Cause: See OSD error accompanying this message
Action: None
ORA-09360: Windows 3.1 Two-Task driver unable to allocate context area
Cause: See OSD error accompanying this message
Action: None
ORA-09361: Windows 3.1 Two-Task driver unable to lock context area
Cause: See OSD error accompanying this message
Action: None
ORA-09362: Windows 3.1 Two-Task driver unable to deallocate context area
Cause: See OSD error accompanying this message
Action: None
ORA-09363: Windows 3.1 Two-Task driver invalid context area
Cause: See OSD error accompanying this message
Action: None
ORA-09364: Windows 3.1 Two-Task driver unable to create hidden window
Cause: See OSD error accompanying this message
Action: None
ORA-09365: Windows 3.1 Two-Task driver unable to destroy hidden window
Cause: See OSD error accompanying this message
Action: None
ORA-09366: Windows 3.1 Two-Task driver unable to allocate shared memory
Cause: See OSD error accompanying this message
Action: None
ORA-09367: Windows 3.1 Two-Task driver unable to deallocate shared memory
Cause: See OSD error accompanying this message
Action: None
ORA-09368: Windows 3.1 Two-Task driver unable to spawn ORACLE
Cause: See OSD error accompanying this message
Action: None
ORA-09369: Windows 3.1 Two-Task driver bad instance handle
Cause: See OSD error accompanying this message
Action: None
ORA-09370: Windows 3.1 Two-Task driver ORACLE task timed out
Cause: See OSD error accompanying this message
Action: None
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.
ORA-09701: scnfy: maximum number of processes exceeded
Cause: PROCESSES INIT.ORA parameter exceeded.
Action: Decrease the PROCESSES parameter and restart.
ORA-09702: sem_acquire: cannot acquire latch semaphore
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.
ORA-09703: sem_release: cannot release latch semaphore
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.
ORA-09704: sstascre: ftok error in creating test and set pages.
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.
ORA-09705: spcre: cannot initialize latch semaphore
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.
ORA-09706: slsget: get_process_stats 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.
ORA-09708: soacon: failed to bind socket to port.
Cause: The bind system call failed on the socket.
Action: Check additional information for OS error. Try connecting again.
ORA-09709: soacon: failed to accept a connection.
Cause: The accept system call failed on the socket.
Action: Check additional information for OS error. Try connecting again.
ORA-09710: soarcv: buffer overflow.
Cause: The internal buffer is not big enough to hold the message read.
Action: Internal error. Contact customer support representative.
ORA-09711: orasrv: archmon already connected.
Cause: An existing connection has already been made from archmon to orasrv.
Action: Stop trying to connect.
ORA-09712: orasrv: log archiver already connected.
Cause: An existing connection has already been made from log archiver to orasrv.
Action: Stop trying to connect.
ORA-09714: Two Task interface: cannot obtain puname
Cause: The TXIPC driver cannot obtain the name of the PU. (Possible OS error)
Action: Check if the PUs are named (consistend).
ORA-09715: orasrv: cannot obtain puname
Cause: Orasrv cannot obtain the name of the PU. (Possible OS error)
Action: Check if the PUs are named (consistend).
ORA-09716: kslcll: Unable to fix in-flux lamport latch.
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.
ORA-09717: osnsui: maximum number of user interrupt handlers exceeded.
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.
ORA-09718: osnsui: cannot set up user interrupt handler.
Cause: Malloc() failed to allocate space to hold user interrupt handler.
Action: Possible memory resource shortage.
ORA-09719: osncui: invalid handle.
Cause: The handle passed to osncui is out of the valid range.
Action: Use a valid handle.
ORA-09740: slsget: cannot get virtual memory region statistics.
Cause: The vm_region system call failed to get virual memory region statistics.
Action: Check return code in sercerrno. Possible operating system failure.
ORA-09741: spwat: error waiting for a post.
Cause: Msg_receive system call returned an error. Internal error.
Action: Check return code in sercerrno. Port name is returned in sercose[0].
ORA-09742: sppst: error during a post.
Cause: Msg_send system call returned an error. Internal error.
Action: Check return code in sercerrno. Port name is returned in sercose[0].
ORA-09743: smscre: could not attach shared memory.
Cause: The mmap or write system call returned an error. Internal error.
Action: Contact Oracle support.
ORA-09744: smsget: mmap returned an error.
Cause: The mmap system call returned an error. Internal error.
Action: Contact Oracle support.
ORA-09745: smscre: vm_allocate error, unable to create shared memory.
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.
ORA-09746: smscre: shared memory attach address incorrect.
Cause: The vm_allocate system call attached the SGA at an incorrect location.
Action: Verify that the SGA attach address is valid.
ORA-09747: pw_detachPorts: server call pws_detach failed.
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.
ORA-09748: pws_look_up: fork failed
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.
ORA-09749: pws_look_up: port lookup failure
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.
ORA-09750: pw_attachPorts: port_rename failed.
Cause: The port_rename system call failed; possible internal error.
Action: Check return code in sercerrno, report to Oracle customer support.
ORA-09751: pw_attachPorts: server call pws_attach failed.
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.
ORA-09752: pw_attachPorts: port_allocate failed.
Cause: The port_allocate system call failed; possible resource exhaustion.
Action: Check return code in sercerrno, report to Oracle customer support.
ORA-09753: spwat: invalid process number.
Cause: Function was passed an invalid oracle process id.
Action: Internal error. Additional information indicates the invalid process id.
ORA-09754: sppst: invalid process number passed to sppst.
Cause: Function was passed an invalid oracle process id.
Action: Internal error. Contact Oracle support.
ORA-09755: osngpn: port allocation failure.
Cause: The port_allocate system call failed.
Action: Possible system resource shortage; check the error code in sercerrno.
ORA-09756: osnpns: no port in the name server.
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.
ORA-09757: osnipn: port allocation failure.
Cause: The port_allocate system call failed.
Action: Possible system resource shortage; check the error code in sercerrno.
ORA-09758: osnipn: could not check port in name server.
Cause: The netname_check_in call failed.
Action: Check the error code in sercerrno. Make sure the network name server is running.
ORA-09759: osnsbt: bad message received.
Cause: The msg_receive system call failed, or received a bad message.
Action: Internal error. Report the error code returned in sercerrno.
ORA-09760: osnpui: cannot send break message
Cause: The Pipe driver could not send a break message to the ORACLE shadow process break thread.
Action: Contact your customer support representative.
ORA-09761: pw_destroyPorts: server call pws_stop_instance failed.
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.
ORA-09762: sNeXT_instanceName: translation error.
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.
ORA-09763: osnmpx: send/receive error exchanging Mach ports.
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.
ORA-09764: osnmop: access error on oracle executable
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.
ORA-09765: osnmop: fork failed
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.
ORA-09766: osnmop: buffer allocation failure.
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.
ORA-09767: osnmfs: bad return code from msg_send.
Cause: The msg_send system call failed while flushing the Mach driver’s send buffer.
Action: Internal error. Contact your customer support representative.
ORA-09768: osnmgetmsg: could not read a message
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.
ORA-09769: osnmbr: cannot send break message
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.
ORA-09770: pws_look_up: translation failure.
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.
ORA-09771: osnmwrtbrkmsg: bad return code from msg_send.
Cause: The msg_send sytem call failed while sending a Mach driver break.
Action: Internal error. Contact your customer support representative.
ORA-09772: osnpmetbrkmsg: message from host had incorrect message type
Cause: The Mach driver received a message having an unrecognizable message type.
Action: Internal error. Contact your customer support representative.
ORA-09773: osnmgetdatmsg: message from host had incorrect message type
Cause: The Mach driver received a message having an unrecognizable message type.
Action: Internal error. Contact your customer support representative.
ORA-09774: osnmui: cannot send break message
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.
ORA-09775: osnmrs: reset protocol error
Cause: The Mach two-task driver could not reset the connection.
Action: Internal error. Contact your customer support representative.
ORA-09776: pws_look_up: access error on (Oracle helper) executable
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.
ORA-09777: osnpbr: cannot send break message
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.
ORA-09778: snynfyport: failure allocating the notify port.
Cause: The routine failed to allocate or set the task’s notify port.
Action: Possible operating system error. Contact Oracle support.
ORA-09779: snyGetPort: failure to allocate a port.
Cause: The port_allocate system call failed; system resources might be exhausted.
Action: Possible operating system error. Contact Oracle support.
ORA-09786: sllfop: open error, unable to open file.
Cause: Open system call returned an error.
Action: Check errno.
ORA-09787: sllfop: unrecognizable processing option, incorrect format.
Cause: Processing option passed is of incorrect format.
Action: Consult your IUG for permissible formats.
ORA-09788: sllfrb: unable to read file.
Cause: Read system call returned an error.
Action: Check errno. Verify file exists.
ORA-09789: sllfsk: unable to read file.
Cause: Read system call returned an error.
Action: Check errno. Verify file exists.
ORA-09790: sllfcf: unable to close file.
Cause: Close system call returned an error.
Action: Check errno.
ORA-09791: slembdf: translation error, unable to translate error file name.
Cause: Additional information indicates error returned from sltln.
Action: Check additional information.
ORA-09792: sllfop: cannot allocate read buffer.
Cause: Malloc system call returned an error. The system might have run out of heap space.
Action: Check additional information for the OS error.
ORA-09793: szguns: length of user name is greater than buffer.
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.
ORA-09794: szrbuild: length of role name is greater than buffer.
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.
ORA-09795: szrbuild: malloc of role structure failed.
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.
ORA-09796: szrbuild: malloc of role name failed.
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.
ORA-09797: Failed to get O/S MAC privileges.
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.
ORA-09798: Label comparison failed.
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.
ORA-09799: File label retrieval failed.
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.
ORA-09800: Process sensitivity label retrieval failed.
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.

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload CAPTCHA.