Oracle8 Error Messages Release 8.0.4 A58312-01 |
Library | Product | Contents | Index

## 09700-09999: UNIX Messages

##### ORA-09700: sclin: maximum number of latches exceeded

Cause: oracle wants to use more latches then are 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 failed to 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 failed to release.

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 the tasdefsid.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 failed to initialize.

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.This is possibly an OS error.

Action: Examine additional information returned. Look for information in OS reference. Contact Oracle Support.

##### ORA-09708: soacon: failed to bind socket to port

Cause: The bind system call failed on the socket.

Action: Examine 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: Examine 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. This is an internal error.

Action: Contact Oracle Support.

##### 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. This is possibly an OS error.

Action: Verify that the PUs are named (consistent).

##### ORA-09715: orasrv: cannot obtain puname

Cause: Orasrv cannot obtain the name of the PU. This is possibly an OS error.

Action: Verify that the PUs are named (consistent).

##### 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 simultaneous 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: Possibly, there is a 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 virtual memory region statistics.

Action: Examine return code in sercerrno. Possible operating system failure.

##### ORA-09741: spwat: error waiting for a post

Cause: Msg_receive system call returned an error. This is an internal error.

Action: Examine 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. This is an internal error.

Action: Examine 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. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09744: smsget: mmap returned an error

Cause: The mmap system call returned an error. This is an 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: Examine 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: Verify that the server is still active. Examine 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 failed to 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 failed to find a port (to Oracle helper).

Action: Verify that 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. This is possibly an internal error.

Action: Examine return code in sercerrno. Contact Oracle Support.

##### ORA-09751: pw_attachPorts: server call pws_attach failed

Cause: The call pws_attach to (Oracle helper) failed.

Action: Verify that the server is still active. Examine 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. This is possibly due to resource exhaustion.

Action: Examine return code in sercerrno. Contact Oracle Support.

##### ORA-09753: spwat: invalid process number

Cause: Function was passed an invalid oracle process ID. This is an internal error.

Action: 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. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09755: osngpn: port allocation failure

Cause: The port_allocate system call failed. This is possibly due to a system resource shortage.

Action: Examine the error code in sercerrno.

##### ORA-09756: osnpns: no port in the name server

Cause: Osnpns failed to find the given named port in the name server.

Action: Examine the error code in sercerrno. Verify that the shadow process and network name server are still running.

##### ORA-09757: osnipn: port allocation failure

Cause: The port_allocate system call failed. This is possibly due to a system resource shortage.

Action: Examine the error code in sercerrno.

##### ORA-09758: osnipn: could not check port in name server

Cause: The netname_check_in call failed.

Action: Examine the error code in sercerrno. Verify that the network name server is running.

##### ORA-09759: osnsbt: bad message received

Cause: The msg_receive system call failed or received a bad message. This is an internal error.

Action: Report the error code returned in sercerrno.

##### ORA-09760: osnpui: cannot send break message

Cause: The pipe driver failed to send a break message to the oracle shadow process break thread.

Action: Contact Oracle Support.

##### ORA-09761: pw_destroyPorts: server call pws_stop_instance failed

Cause: The call pws_stop_instance to (Oracle helper) failed.

Action: Verify that the server is still active. Examine 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: Verify that 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: Examine return code in sercerrno. Verify that both sides of the connection are still running.

##### ORA-09764: osnmop: access error on oracle executable

Cause: The mach driver failed to access the oracle executable.

Action: Verify the permissions on the oracle executable and each component of the $ORACLE_HOME/bin path.

##### ORA-09765: osnmop: fork failed

Cause: The mach driver failed to 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. This is an internal error.

Action: Contact Oracle Support.

##### 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. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09769: osnmbr: cannot send break message

Cause: The mach driver failed to send a break message to the oracle shadow process break thread. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09770: pws_look_up: translation failure

Cause: The pws_look_up routine failed to translate the name of the (Oracle helper) executable.

Action: Verify that 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 system call failed while sending a mach driver break. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09772: osnpmetbrkmsg: message from host had incorrect message type

Cause: The mach driver received a message having an unrecognizable message type. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09773: osnmgetdatmsg: message from host had incorrect message type

Cause: The mach driver received a message having an unrecognizable message type. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09774: osnmui: cannot send break message

Cause: The mach driver failed to send a break message to the oracle shadow process break thread. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09775: osnmrs: reset protocol error

Cause: The mach two-task driver failed to reset the connection. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09776: pws_look_up: access error on (Oracle helper) executable

Cause: The pws_look_up call failed to access the (Oracle helper) executable.

Action: Verify 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 failed to send a break message to the oracle shadow process break thread. This is an internal error.

Action: Contact Oracle Support.

##### 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. This is possibly an operating system error.

Action: Contact Oracle Support.

##### ORA-09786: sllfop: open error, unable to open file

Cause: Open system call returned an error.

Action: Examine errno.

##### ORA-09787: sllfop: unrecognizable processing option, incorrect format

Cause: Processing option passed is of incorrect format.

Action: Consult IUG for permissible formats.

##### ORA-09788: sllfrb: unable to read file

Cause: Read system call returned an error.

Action: Examine errno. Verify that file exists.

##### ORA-09789: sllfsk: unable to read file

Cause: Read system call returned an error.

Action: Examine errno. Verify that file exists.

##### ORA-09790: sllfcf: unable to close file

Cause: Close system call returned an error.

Action: Examine errno.

##### ORA-09791: slembdf: translation error, unable to translate error file name

Cause: Additional information indicates error returned from sltln.

Action: Examine 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: Examine 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. This is an internal error.

Action: Contact Oracle Support.

##### 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. This is an internal error.

Action: Contact Oracle Support.

##### 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: Examine 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: Examine 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: Examine the UNIX error number for a possible operating system failure. If there is no error, then contact Oracle Support.

##### ORA-09798: label comparison failed

Cause: The comparison of two binary labels failed.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, then contact Oracle Support.

##### ORA-09799: file label retrieval failed

Cause: The oracle executable failed to get a label attached to a file.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, then contact Oracle Support.

##### ORA-09800: process sensitivity label retrieval failed

Cause: The oracle executable failed to get the sensitivity label for a process.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, then contact Oracle Support.

##### ORA-09801: unable to get user ID from connection

Cause: The oracle executable failed to retrieve the user's ID number from the Oracle Net connection.

Action: Examine the UNIX error number for a possible operating system error. Also examine the "additional information" field for the Oracle Net error. If there is no error, then contact Oracle Support.

##### ORA-09802: conversion of binary label to string failed

Cause: The oracle executable failed to convert a binary label to a string.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, then contact Oracle Support.

##### ORA-09803: allocation of string buffer failed

Cause: A buffer used to hold the name of the file for which a label was to be obtained failed to allocate.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, then contact Oracle Support. The number of bytes that oracle attempted to allocate is in the "additional information" field.

##### ORA-09804: class conversion from binary to oracle failed

Cause: The oracle executable failed to convert a class component from binary format to Oracle format.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, then contact Oracle Support.

##### ORA-09805: conversion of category number to string failed

Cause: The oracle executable failed to translate a category number to its corresponding string representation failed.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, then contact Oracle Support. The category number is contained in the "additional information" field.

##### ORA-09806: allocation of label string buffer failed

Cause: A temporary buffer used to hold a label failed to allocate.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, then contact Oracle Support. The number of bytes that oracle attempted to allocate is in the "additional information" field.

##### ORA-09807: conversion of label from string to binary failed

Cause: The oracle executable failed to convert the string representation of a label to binary format.

Action: Re-enter a valid label.

##### ORA-09808: could not obtain user clearance

Cause: The oracle executable failed to get a user's clearance level.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, then contact Oracle Support.

##### ORA-09809: unable to get user's group ID from connection

Cause: The oracle executable failed to retrieve the user's group ID number from the Oracle Net connection.

Action: Examine the UNIX error number for a possible operating system error. Also examine the "additional information" field for the Oracle Net error. If there is no error, then contact Oracle Support.

##### ORA-09810: unable to get process ID from connection

Cause: The oracle executable failed to retrieve the user's process ID number from the Oracle Net connection.

Action: Examine the UNIX error number for a possible operating system error. Also examine the "additional information" field for the Oracle Net error. If there is no error, then contact Oracle Support.

##### ORA-09811: unable to initialize package

Cause: The oracle executable failed to initialize the library used to obtain security information. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09812: unable to get user clearance from connection

Cause: The oracle executable failed to retrieve the user's operating system session clearance from the Oracle Net connection.

Action: Examine the UNIX error number for a possible operating system error. Also examine the "additional information" field for the Oracle Net error. If there is no error, then contact Oracle Support.

##### ORA-09813: unable to get directory status

Cause: The oracle executable failed to determine if a directory is multilevel.

Action: Examine the UNIX error number for a possible operating system error. If there is no error, then contact Oracle Support.

##### ORA-09814: unable to expand file name

Cause: The oracle executable failed to expand the name of a file that resides in multilevel directory.

Action: Examine the UNIX error number for a possible operating system error. If there is no error, then contact Oracle Support. This is an internal error.

##### ORA-09815: file name buffer overflow

Cause: The buffer that oracle uses to hold the expanded name of a too small.

Action: Contact Oracle Support.

##### ORA-09816: unable to set effective privileges

Cause: This is an internal error.

Action: Contact Oracle Support.

##### ORA-09817: write to audit file failed.

Cause: The oracle executable failed to write an entry to the file used for the audit trail.

Action: Examine the UNIX error number for a possible operating system error. If there is no error, then contact Oracle Support.

##### ORA-09818: number is too large

Cause: The oracle executable failed to convert a component string to a number, because the number is larger than the largest possible value for an integer. The additional information field specifies the maximum.

Action: Correct the string and repeat the conversion.

##### ORA-09819: number exceeds maximum legal value

Cause: The number specified for a component was greater than the maximum value allowed for that component.

Action: Change the component to a value less than the maximum and repeat the conversion. The maximum component number is contained in the "additional information" field.

##### ORA-09820: conversion of class string to numeric representation failed

Cause: The oracle executable failed to convert a class string to a number because all of the characters in the string were not numeric.

Action: Change the string to be either all numbers or all non-numeric characters, and repeat the conversion.

##### ORA-09821: numeric label is not valid

Cause: A label specified in Oracle numeric format was found not to be valid.

Action: Re-enter a valid label. Consult system's encodings for valid numeric component values.

##### ORA-09822: translation of audit file name failed

Cause: The oracle executable failed to translate the value of the AUDIT_TRAIL_DEST initialization parameter.

Action: Examine the UNIX error number for a possible operating system error. If there is no error, then contact Oracle Support.

##### ORA-09823: device name is too long

Cause: The name of a device was too long to fit into an internal buffer. The additional information field contains the length of the device name. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09824: unable to enable allowmacaccess privilege

Cause: The oracle executable failed to turn on allowmacaccess privilege, so that it could do a label comparison.

Action: Examine the UNIX error number. If it indicates that Oracle does not have the allowmacaccess privilege, then add the allowmacaccess privilege to the potential privilege set of $ORACLE_HOME/bin/oracle using chpriv (1M). If the executable already has the allowmacaccess privilege, then contact Oracle Support.

##### ORA-09825: unable to disable allowmacaccess privilege

Cause: The oracle executable failed to turn off the allowmacaccess privilege after doing a label comparison. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09826: SCLIN: cannot initialize atomic latch

Cause: System call atomic_op() return error.

Action: Examine additional information in the trace file.

##### ORA-09827: SCLGT: atomic latch return unknown error

Cause: System call atomic_op() return unexpected error.

Action: Examine additional information in the trace file.

##### ORA-09828: SCLFR: atomic latch return error

Cause: System call atomic_op() return unexpected error.

Action: Examine additional information in the trace file.

##### ORA-09829: pw_createPorts: server call pws_start_instance failed

Cause: The call pws_start_instance to (Oracle helper) failed. System resources might be exhausted.

Action: Verify that the server is still active. Examine the error code returned in sercerrno, and look for error messages in the server log file.

##### ORA-09830: snyAddPort: failed to perform a remote procedure call

Cause: The msg_rpc system call returned an error. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09831: snyStartThread: failed to build the server port set

Cause: The routine failed to build a port set on which to listen for requests. This is possibly an operating system failure.

Action: Contact Oracle Support.

##### ORA-09832: infoCallback: bad message format

Cause: The routine received an incorrectly formatted request. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09833: addCallback: bad message format

Cause: The routine received an incorrectly formatted request. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09834: snyGetPortSet: failed to collect info on a port

Cause: The port_status system called failed. This is possibly an operating system error.

Action: Contact Oracle Support.

##### ORA-09835: addCallback: callback port is already in a set

Cause: The port to be added to the callback list is already in a port set. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09836: addCallback: could not add a port to the callback set

Cause: The port_set_add system called failed. This is possibly an operating system error.

Action: Contact Oracle Support.

##### ORA-09837: addCallback: could not add allocate a callback link

Cause: The malloc library call failed to allocate space for a callback link. This is possibly an operating system error.

Action: Contact Oracle Support.

##### ORA-09838: removeCallback: failure removing the callback port

Cause: The port port_set_remove system call failed. This is possibly an operating system error.

Action: Contact Oracle Support.

##### ORA-09839: removeCallback: callback port is not in the callback set

Cause: The port to be removed to the callback list is not in the callback port set. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09840: soacon: name translation failure

Cause: sltln() failed to translate the named pipe $ORACLE_HOME/dbs/mon2arch_sid.

Action: Verify that the $ORACLE_HOME specified for this ORACLE_SID in oratab is correct.

##### ORA-09841: soacon: name translation failure

Cause: sltln() failed to translate the named pipe $ORACLE_HOME/dbs/arch2mon_sid.

Action: Verify that the $ORACLE_HOME specified for this ORACLE_SID in oratab is correct.

##### ORA-09846: soacon: ARCH unable to open named pipe

Cause: Open() failed to open named pipe $ORACLE_HOME/dbs/mon2arch_sid. The max number of open files may have been exceeded.

Action: Verify that the OS userid of the currently running database has search permission for the $ORACLE_HOME/dbs directory.

##### ORA-09847: soacon: ARCH unable to open named pipe

Cause: Open() failed to open named pipe $ORACLE_HOME/dbs/arch2mon_sid. The max number of open files may have been exceeded.

Action: Verify that the OS userid of the currently running database has search permission for the $ORACLE_HOME/dbs directory.

##### ORA-09848: soawrt: unable to write to named pipe

##### ORA-09849: soarcv: unable to read from named pipe

##### ORA-09853: snyRemovePort: bad return code from request

Cause: The request to remove a port from the callback set returned a failure code. This is possibly an operating system error.

Action: Contact Oracle Support.

##### ORA-09854: snyPortInfo: bad return code from request

Cause: The request to collect info on a port in the callback set returned a failure code. This is possibly an operating system error.

Action: Contact Oracle Support.

##### ORA-09855: removeCallback: bad message format

Cause: The routine received an incorrectly formatted request. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09856: smpalo: vm_allocate error while allocating pga

Cause: The vm_allocate system call returned an error. Possibly, there is a shortage of system resources.

Action: Examine error.

##### ORA-09857: smprset: vm_protect error while protecting pga

Cause: The vm_protect system call returned an error. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09870: spini: failure initializing maximum number of open files

Cause: ulimit system call returned an error.

Action: Examine errno.

##### ORA-09871: TASDEF_NAME: translation error while expanding $ORACLE_HOME/dbs/tasdefsid.dbf

Cause: Failure of sltln($ORACLE_HOME/tasdefsid.dbf) while creating test and set pages.

Action: Examine additional return error for more information.

##### ORA-09872: TASDEF_CREATE: create failure in creating $ORACLE_HOME/dbs/tasdefsid.dbf

Cause: Create() failed when trying to create the tasdef file.

Action: Verify permissions on $(ORACLE_HOME)/dbs directory.

##### ORA-09873: TASDEF_OPEN: open error when opening tasdefsid.dbf file

Cause: Failure to open tasdefsid.dbf file. This is possibly a permission problem.

Action: Examine errno. Verify that tasdefsid.dbf file exists.

##### ORA-09874: TASDEF_READ: read error, unable to read tasdefsid.dbf file

Cause: Read system call returned an error when attempting to read $ORACLE_HOME/dbs/tasdefsid.dbf.

Action: Examine errno. sgadef file may be corrupted or incompatible with Oracle version.

##### ORA-09875: TASDEF_WRITE: write error when writing $ORACLE_HOME/dbs/tasdefsid.dbf file

Cause: Write call failed. Possibly, there is a shortage of space on device.

Action: Examine errno.

##### ORA-09876: TASDEF_CLOSE: unable to close $ORACLE_HOME/dbs/tasdefsid.dbf file

Cause: Close system call returned an error. Possibly this is an operating system failure.

Action: Examine errno.

##### ORA-09877: sstascre: shmget error, unable to get a shared memory segment

Cause: Error in shmget.

Action: Examine errno. Verify that enough shared memory is available on the system.

##### ORA-09878: sstascre/sstasat: shmat error, unable to attach tas write page

Cause: Error in shmat.

Action: Examine errno.Verify that enough shared memory is available on the system.

##### ORA-09879: sstascre/sstasat: shmat error, unable to attach tas read page

Cause: Error in shmat.

Action: Examine errno.Verify that enough shared memory is available on the system.

##### ORA-09880: sstasfre/sstasdel: shmdt error, unable to detach tas write page

Cause: Error in shmdt.

Action: Examine errno.

##### ORA-09881: sstasfre/sstasdel: shmdt error, unable to detach tas read page

Cause: Error in shmdt.

Action: Examine errno.

##### ORA-09882: sstasfre/sstasdel: shmctl error, unable to remove tas shm page

Cause: Error in shmctl.

Action: Examine errno.

##### ORA-09883: two task interface: oratab file does not exist

Cause: The oratab file does not exist.

Action: Install Oracle before using it, or recreate the oratab file.

##### ORA-09884: two task interface: SID doesn't match current PU

Cause: The oracle executable is being started on another PU than oracle was configured on, or there is no entry for this SID in oratab file.

Action: Start oracle with this SID on its designated PU (see oratab file). Or install the new database with SID.

##### ORA-09885: osnTXtt: cannot create TXIPC channel

Cause: The TXIPC driver failed to create pipes for two-task communications with the oracle shadow process.

Action: Probably, the maximum number of open file descriptors per user has been exceeded, or the system file table is full. Examine the operating system error code, and contact system administrator.

##### ORA-09886: osnTXtt: translation error while expanding txipcsid.trc

Cause: Failure of sltln(txipcsid.trc) while creating debug channel.

Action: Examine additional return error for more information.

##### ORA-09887: osnTXtt: failed to create/open debug channel

##### ORA-09888: osnTXtt: txipc channel creation failed

Cause: The txipc driver failed to create channels for two-task communications with the oracle shadow process.

Action: Probably, the maximum number of open file descriptors per user has been exceeded. Examine the system file table operating system error code, and contact system administrator.

##### ORA-09889: osnTXtt: access error on oracle executable

Cause: The txipc driver failed to access the oracle executable.

Action: Verify the permissions on the oracle executable and each component of the $ORACLE_HOME/bin path.

##### ORA-09890: osnTXtt: malloc failed

Cause: The txipx driver failed to allocate enough heap space for its context area buffers.

Action: Contact Oracle Support.

##### ORA-09908: slkmnm: gethostname returned error code

Cause: The system call gethostname returned an error. This is most likely an internal error.

Action: Verify that gethostname is successful in other contexts, and if so contact Oracle Support.

##### ORA-09909: malloc of scratch buffer failed

Cause: Memory needed for a temporary buffer failed to allocate. The additional information field contains the number of bytes that oracle attempted to allocate. It is probable that the system has run out of memory.

Action: Examine the UNIX error number. If there is no error, contact Oracle Support.

##### ORA-09910: unable to find oracle password file entry for user

Cause: No entry exists for the user in the oracle password file.

Action: Have the database administrator install a password entry by running orapasswd.

##### ORA-09911: incorrect user password

Cause: The password entered by the user was incorrect.

Action: Enter the correct password.

##### ORA-09912: malloc of name buffer(s) failed

Cause: The oracle executable failed to allocate memory for one or both of the buffers that are used to hold the name of DBA and the operator users. It is probable that the system has run out of memory.

Action: Examine the UNIX error number. If there is no error, contact Oracle Support.

##### ORA-09913: malloc of dummy name failed

Cause: The oracle executable failed to allocate memory for the user name that is to be used in the encryption of the user's password. It is probable that the system has run out of memory.

Action: Examine the UNIX error number. If there is no error, contact Oracle Support.

##### ORA-09914: unable to open the oracle password file

Cause: The oracle executable failed to open the password file for reading.

Action: Examine the UNIX error number. If the error number indicates that the file does not exist, have the database administrator create the file by running orapasswd. If the error number indicates insufficient permissions, ask the database administrator to change the permissions. Otherwise, contact Oracle Support.

##### ORA-09915: password encryption failed

Cause: The oracle executable failed to encrypt a password. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09916: required password was not specified

Cause: A user attempted to connect as "internal", but did not specify a password.

Action: Connect as internal again and specify a password.

##### ORA-09918: unable to get user privileges from Oracle Net

Cause: The oracle executable failed to retrieve the user's privilege set from the Oracle Net connection.

Action: Examine the UNIX error number for a possible operating system error. Also examine the "additional information" field for the Oracle Net error. If there is no error, contact Oracle Support.

##### ORA-09919: unable to set label of dedicated server

Cause: The oracle executable failed to set the label of the dedicated to server to the required value.

Action: Examine the UNIX error number for a possible operating system error. Also, verify the privileges on the oracle executable. It should have at least "allowmacaccess" privilege.

##### ORA-09920: unable to get sensitivity label from connection

Cause: The oracle executable failed to retrieve the user's sensitivity label from the Oracle Net connection.

Action: Examine the UNIX error number for a possible operating system error. Also examine the "additional information" field for the Oracle Net error. If there is no error, contact Oracle Support.

##### ORA-09921: unable to get information label from connection

Cause: The oracle executable failed to retrieve the user's information label from the Oracle Net connection.

Action: Examine the UNIX error number for a possible operating system error. Also examine the "additional information" field for the Oracle Net error. If there is no error, contact Oracle Support.

##### ORA-09922: can't spawn process - background log directory not created properly

Cause: The oracle executable failed to spawn a background process because the directory that will hold trace files of the background processes was not created properly.

Action: Examine the directory pointed to by the initialization parameter BACKGROUND_DUMP_DEST. Verify that all of the following is true: 1) The directory exists. 2) The name indeed points to a directory, and is not a file. 3) The directory is accessible and writable to the Oracle user.

##### ORA-09923: can't spawn process - user log directory not created properly

Cause: The oracle executable failed to spawn a background process because the directory that holds the trace files of the dedicated server processes was not created properly.

Action: Examine the directory pointed to by the initialization parameter USER_DUMP_DEST. Verify that all of the following is true: 1) The directory exists. 2) The name indeed points to a directory, and is not a file. 3) The directory is accessible and writable to the Oracle user.

##### ORA-09924: can't spawn process - core dump directory not created properly

Cause: The oracle executable failed to spawn a background process because the directory that holds the core dumps produced by oracle processes in the event of exceptions was not created properly.

Action: Examine the directory pointed to by the initialization parameter CORE_DUMP_DEST. Verify that all of the following is true: 1) The directory exists. 2) The name indeed points to a directory, and is not a file. 3) The directory is accessible and writable to the Oracle user.

##### ORA-09925: unable to create audit trail file

Cause: The oracle executable failed to create the file being used to hold audit trail records.

Action: Examine the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support.

##### ORA-09926: unable to set effective privilege set of the server

Cause: A dedicated server failed to set it's own privilege set.

Action: Verify that the privileges granted to the oracle executable. It must have at least "allowmacacess" privilege.

##### ORA-09927: Unable to set label of server

Cause: The oracle executable failed to set the label of a server to a new value.

Action: Verify that the privileges on $ORACLE_HOME/bin/oracle. Verify that it has "allowmacaccess" privilege.

##### ORA-09928: unable to restore the label of server

Cause: The oracle executable failed to restore the label of the server to the value that it had before raising it to database high. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09929: GLB of two labels is invalid

Cause: The result of a greatest lower bound operation on two labels was not valid.

Action: Repeat the operation with two different labels. Consult the system encoding file for the values of valid labels.

##### ORA-09930: LUB of two labels is invalid

Cause: The result of a least upper bound operation on two labels was not valid.

Action: Repeat the operation with two different labels. Consult the system encoding file for the values of valid labels.

##### ORA-09931: unable to open oracle password file for reading

Cause: An attempt to open a password file for reading failed.

Action: Verify that the permissions on the file have not been changed so that the Oracle user cannot open it.

##### ORA-09932: close of oracle password file failed

Cause: An attempt to close a password file failed.

Action: Examine the UNIX error number for the specific reason.

##### ORA-09933: deletion of old password file failed

Cause: The removal of the old password file failed.

Action: Examine the UNIX error number for the specific reason.

##### ORA-09934: link of current password file to old failed

Cause: The oracle executable failed to create a link so that the old password file could be saved.

Action: Examine the UNIX error number for the specific reason.

##### ORA-09935: unlink of current password file failed

Cause: The oracle executable failed to complete the saving of the current password file.

Action: Examine the UNIX error number for the specific reason.

##### ORA-09936: open of oracle password file for write failed

Cause: The oracle executable failed to create a password file.

Action: Examine the UNIX error number for the specific reason.

##### ORA-09937: chmod of oracle password file failed

Cause: The oracle executable failed to change a password file to be read only.

Action: Examine the UNIX error number for the specific reason.

##### ORA-09938: save of signal handlers failed

Cause: The oracle executable failed to save the previous values of selected signal handlers. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09939: restoration of signal handlers failed

Cause: The oracle executable failed to restore the previous values of selected signal handlers. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09940: oracle password file header is corrupt

Cause: The header of one of the password files was not in the format that the oracle executable expected.

Action: Examine the headers of both files. The header should be in the format FILE VERSION: N.N.N.N.N EXECUTABLE VERSION: N.N.N.N.N where N is a number. Remove the corrupt file(s) and re-run "orapasswd".

##### ORA-09941: version of orapasswd or installer is older than file

Cause: The version of orapasswd or installer that is being run is older than that of the oracle password file. Since the file version is only changed when the format is changed, this error means that the executable is using a different format than that with which the file was created.

Action: Run a version of the installer or orapasswd whose version is the same or later than that of the file.

##### ORA-09942: write of oracle password file header failed

Cause: The attempt to write out the header of the oracle password file failed.

Action: Examine the operating system error number. It is possible that the file system became full.

##### ORA-09943: allocation of memory for password list component failed

Cause: When it is building a list of password file entries, the oracle executable allocates memory for various components. One of the allocations failed. The system has probably run out of memory.

Action: Examine the operating system error number.

##### ORA-09944: password entry is corrupt

Cause: An entry in an oracle password file was not in the format that the oracle executable expected.

Action: Removed the corrupt file(s) and re-run "orapasswd."

##### ORA-09945: unable to initialize the audit trail file

Cause: The oracle executable failed to write header information to the file being used for the audit trail.

Action: Examine the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support.

##### ORA-09946: file name too long for buffer

Cause: The buffer that was to be used to hold a file name was determined to be too short for the generated name. This will happen if the translated name for either a trace file or an audit file is longer than the maximum allowed, which on many ports is 256 characters.

Action: Use a shorter file name.

##### ORA-09947: unable to allocate connection attributes structure

Cause: The oracle executable failed to allocate the memory needed to hold the attributes of the Oracle Net connection. The "additional information" field holds the number of bytes that oracle attempted to allocate. It is probable that the system has run out of memory.

Action: Examine the UNIX error number.If there is no error, contact Oracle Support.

##### ORA-09948: process information label retrieval failed

Cause: The oracle executable failed to get the information label for a process.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support.

##### ORA-09949: unable to get client operating system privileges

Cause: The oracle executable failed to get the operating system privileges for the client process.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support.

##### ORA-09950: unable to get server operating system privileges

Cause: The oracle executable failed to get its privileges from the operating system.

Action: Contact Oracle Support.

##### ORA-09951: unable to create file

Cause: The oracle executable failed to create a file.

Action: Examine the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support.

##### ORA-09952: scgcmn: lk_open_convert unexpected return: open failed

Cause: The distributed lock manager returned an unexpected value.

Action: Examine for system error message and refer to the distributed lock manager documentation, or contact Oracle Support.

##### ORA-09953: scggc: unexpected return of a lock convert

Cause: The distributed lock manager returned an unexpected value.

Action: Look for lock manager error message and refer to DLM documentation. Refer to the distributed lock manager documentation, or contact Oracle Support.

##### ORA-09954: scgcc: unexpected return status to callback of lock close

Cause: The distributed lock manager returned an unexpected value.

Action: Look for lock manager error message and refer to DLM documentation. Refer to the distributed lock manager documentation, or contact Oracle Support.

##### ORA-09955: scgcan: unexpected return status when canceling a lock

Cause: DLM system service x returned an unexpected value.

Action: Look for system error message and refer to DLM documentation refer to the distributed lock manager documentation, or contact Oracle Support.

##### ORA-09956: scgcm: unexpected lock status condition

Cause: A global locking system service returned an unexpected value.

Action: Look for system error message (if any) and refer to refer to the distributed lock manager documentation, or contact Oracle Support.

##### ORA-09957: unable to send termination request to IMON

Cause: The attempt to send a termination signal to IMON failed. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09958: IMON: two processes with the same oracle pid are active

Cause: The IMON process failed to add an entry for a server process, because another active process occupies the slot. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09959: IMON: deletion of a process failed

Cause: The IMON process failed to delete a server process from its process ID array, because no entry for the process could be found. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09960: unable to establish signal handler for termination signal

Cause: The oracle executable failed to set up a handler for the signal used to notify it that the instance was shutting down. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09961: unable to restore termination signal handler

Cause: The oracle executable failed to set the handler for the termination signal to its previous value. This is an internal error.

Action: Contact Oracle Support.

##### ORA-09962: lk_group_create error in scggrc

##### ORA-09963: lk_group_attach error in scggra

##### ORA-09964: lk_group_detach error in scggrd

##### ORA-09965: scumnt: db lock name space parameter is null

##### ORA-09966: scumnt: translation error while expanding $ORACLE_HOME/dbs/lk

Cause: Failure of sltln in scumnt.

Action: Examine additional return error for more information.

##### ORA-09967: scumnt: unable to create or open file

Cause: Open system call returned an error.

Action: Examine errno

##### ORA-09968: scumnt: unable to lock file

Cause: Lock file operating system call returned an error.

Action: Examine errno.

##### ORA-09974: skxfidini: error initializing SDI channel

Cause: The process failed to initialize the SDI channel properly.

Action: Correct the operating system error and retry the operation.

##### ORA-09975: kxfspini: error initializing SDI process

Cause: The process failed to attach to the SDI channel.

Action: Verify that the SDI process specific limits correctly configured. Correct the operating system error and retry the operation.

##### ORA-09976: skxfqdini: error creating port

Cause: The process failed to create a communications endpoint.

Action: Verify that the SDI port specific limits correctly configured. Correct the operating system error and retry the operation.

##### ORA-09977: skxfqhini: error connecting

Cause: The process failed to connect to another endpoint.

Action: Verify that the SDI port specific limits correctly configured. Verify that the other node(s) is part of the cluster and operating properly. Correct the operating system error and retry the operation.

##### ORA-09978: skxfqhdel: error disconnecting from another endpoint

Cause: The process failed to disconnect cleanly from another endpoint.

Action: Verify that the other node(s) are part of the cluster and operating properly. Verify the instance and processes on the other node(s). Correct the operating system error and retry the operation.

##### ORA-09979: skxfqhsnd: error sending a message to another endpoint

Cause: The process failed to send a message to an existing endpoint.

Action: Verify that the other node(s) are part of the cluster and operating properly. Verify the instance and processes on the other node(s). Correct the operating system error and retry the operation.

##### ORA-09980: skxfqdrcv: error receiving a message from another endpoint

Cause: The process encountered an error while trying to receive a message.

Action: Verify that the other node(s) are part of the cluster and operating properly. Verify the instance and processes on the other node(s). Correct the operating system error and retry the operation.

##### ORA-09981: skxfqdreg: error adding a page to the SDI buffer pool

Cause: The process failed to add a page to the SDI buffer pool.

Action: Correct the operating system error and retry the operation.

##### ORA-09982: skxfqddrg: error removing a page from the SDI buffer pool

Cause: The process failed to remove a page to the SDI buffer pool.

Action: Correct the operating system error and retry the operation.

##### ORA-09983: skxfidsht: error shutting down SDI channel

Cause: The process failed shut down the SDI channel

Action: Examine the SDI persistent resources using SDI tools. Verify that all processes exited cleanly and the instance is safely shut down. Delete any remaining SDI channel IDs associated with the current instance.

##### ORA-09984: SGA file $ORACLE_HOME/dbs/sgadefsid.dbf does not exist

Cause: File does not exist or is not accessible.

Action: Restart the instance to create the SGA definition file.

##### ORA-09985: SGA definition file could not be read

Cause: Read() operation failed.

Action: Examine errno, and take appropriate action.

##### ORA-09986: wrong number of bytes read from SGA definition file

Cause: Struct skgmsdef size differs from number of bytes read from SGA file.

Action: Compare the two struct definitions and ensure that they are identical in size and structure.

##### ORA-09987: unable to attach to SGA in READ-ONLY mode

Cause: The instance is not up, or SGA segments are not read-accessible.

Action: Verify that the instance is up and read permissions for the SGA segments are set.

##### ORA-09988: error while detaching SGA

Cause: skgmsdef struct is corrupted and/or segment addresses are modified.

Action: Safely shut down instance and mount SGA segments again.

##### ORA-09989: attempt to use invalid skgmsdef struct pointer

Cause: Pointer to skgmsdef struct used without validating it.

Action: Assign a valid address to the skgmsdef struct pointer before using it.

Prev | Top | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index