Oracle 11g Error Codes and Solution Suggestions from ORA-09800 to ORA-09900
- 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.
- ORA-09801: Unable to get user ID from connection
- Cause: ORACLE was unable to retrieve the user’s ID number from the SQL*Net connection.
- Action: Check the UNIX error number for a possible operating system error. Also check the “additional information” field for the SQL*Net error. If there is no error, contact Oracle Support Services.
- ORA-09802: Conversion of binary label to string failed.
- Cause: ORACLE was unable to convert a binary label to a string.
- Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.
- 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 could not be allocated.
- Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. 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: ORACLE was unable to convert a class component from binary format to ORACLE format.
- Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.
- ORA-09805: conversion of category number to string failed.
- Cause: ORACLE was unable to translate a category number to its corresponding string representation failed.
- Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. 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 could not be allocated.
- Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. 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: ORACLE was unable 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: ORACLE was unable to get a user’s clearance level.
- Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.
- ORA-09809: Unable to get user’s group ID from connection
- Cause: ORACLE was unable to retrieve the user’s group ID number from the SQL*Net connection.
- Action: Check the UNIX error number for a possible operating system error. Also check the “additional information” field for the SQL*Net error. If there is no error, contact Oracle Support Services.
- ORA-09810: Unable to get process ID from connection
- Cause: ORACLE was unable to retrieve the user’s process ID number from the SQL*Net connection.
- Action: Check the UNIX error number for a possible operating system error. Also check the “additional information” field for the SQL*Net error. If there is no error, contact Oracle Support Services.
- ORA-09811: Unable to initialize package.
- Cause: ORACLE was unable to initialize the library used to obtain security information.
- Action: This is an internal error. Contact Oracle Support Services.
- ORA-09812: Unable to get user clearance from connection
- Cause: ORACLE was unable to retrieve the user’s operating system session clearance from the SQL*Net connection.
- Action: Check the UNIX error number for a possible operating system error. Also check the “additional information” field for the SQL*Net error. If there is no error, contact Oracle Support Services.
- ORA-09813: Unable to get directory status
- Cause: ORACLE was unable to determine if a directory is multilevel.
- Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services.
- ORA-09814: Unable to expand file name
- Cause: ORACLE was unable to expand the name of a file that resides in multilevel directory.
- Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services.
- ORA-09815: File name buffer overflow
- Cause: The buffer that ORACLE uses to hold the expanded name of a too small.
- Action: This is an internal error. Contact Oracle Support Services.
- ORA-09817: Write to audit file failed.
- Cause: ORACLE was unable to write an entry to the file used as the audit trail.
- Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services.
- ORA-09818: Number is too large
- Cause: ORACLE was unable 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: ORACLE was unable 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 your system’s encodings for valid numeric component values.
- ORA-09822: Translation of audit file name failed.
- Cause: Oracle was unable to translate the value of the AUDIT_FILE_DEST initialization parameter.
- Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services.
- 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.
- Action: This is an internal error. Contact Oracle Support Services.
- ORA-09824: Unable to enable allowmacaccess privilege.
- Cause: ORACLE was not able to turn on allowmacaccess privilege so that it could do a label comparison.
- Action: Check the UNIX error number. If it indicates that ORACLE does not have the allowmacaccess privilege, 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, contact Oracle Support Services.
- ORA-09825: Unable to disable allowmacaccess privilege.
- Cause: ORACLE was not able to turn off the allowmacaccess privilege after doing a label comparison.
- Action: This is an internal error. Contact Oracle Support Services.
- ORA-09826: SCLIN: cannot initialize atomic latch.
- Cause: System call atomic_op() return error.
- Action: Check additional information in the trace file.
- ORA-09827: SCLGT: atomic latch return unknown error.
- Cause: System call atomic_op() return unexpected error.
- Action: Check additional information in the trace file.
- ORA-09828: SCLFR: atomic latch return error.
- Cause: System call atomic_op() return unexpected error.
- Action: Check 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: 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-09830: snyAddPort: failed to perform a remote procedure call.
- Cause: The msg_rpc system call returned an error.
- Action: Internal error. 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.
- Action: Possible operating system failure. Contact Oracle support.
- ORA-09832: infoCallback: bad message format.
- Cause: The routine received an incorrectly formatted request.
- Action: Internal error. Contact Oracle support.
- ORA-09833: addCallback: bad message format.
- Cause: The routine received an incorrectly formatted request.
- Action: Internal error. Contact Oracle support.
- ORA-09834: snyGetPortSet: failed to collect info on a port.
- Cause: The port_status system called failed.
- Action: Possible operating system error. 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.
- Action: Internal error. Contact Oracle support.
- ORA-09836: addCallback: could not add a port to the callback set.
- Cause: The port_set_add system called failed.
- Action: Possible operating system error. 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.
- Action: Possible operating system error. Contact Oracle support.
- ORA-09838: removeCallback: failure removing the callback port.
- Cause: The port port_set_remove system call failed.
- Action: Possible operating system error. 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.
- Action: Internal error. Contact Oracle support.
- ORA-09840: soacon: Name translation failure.
- Cause: sltln() could not translate the named pipe ?/dbs/mon2arch_@.
- Action: Make sure that the ORACLE_HOME specified for this ORACLE_SID in oratab is correct.
- ORA-09841: soacon: Name translation failure.
- Cause: sltln() could not translate the named pipe ?/dbs/arch2mon_@.
- Action: Make sure that the ORACLE_HOME specified for this ORACLE_SID in oratab is correct.
- ORA-09842: soacon: Archmon unable to create named pipe.
- Cause: mknod() failed to create named pipe ?/dbs/mon2arch_@.
- Action: Your current OS login may lack write permission for the ORACLE_HOME/dbs directory. Only userids in the dba group of a given instance can run archmon for that ORACLE_SID. Make sure that the ORACLE_HOME directory is correct in oratab.
- ORA-09843: soacon: Archmon unable to create named pipe.
- Cause: mknod() failed to create named pipe ?/dbs/arch2mon_@.
- Action: Your current OS login may lack write permission for the ORACLE_HOME/dbs directory. Only userids in the dba group of a given instance can run archmon for that ORACLE_SID. Make sure that the ORACLE_HOME directory is correct in oratab.
- ORA-09844: soacon: Archmon unable to open named pipe.
- Cause: open() failed to open named pipe ?/dbs/mon2arch_@.
- Action: Only the oracle dba can run archmon. Make sure that your current OS login has owner or group search permission for the ORACLE_HOME/dbs directory. The max number of open files may have been exceeded.
- ORA-09845: soacon: Archmon unable to open named pipe.
- Cause: open() failed to open named pipe ?/dbs/arch2mon_@.
- Action: Only the oracle dba can run archmon. Make sure that your current OS login has owner or group search permission for the ORACLE_HOME/dbs directory. The max number of open files may have been exceeded.
- ORA-09846: soacon: ARCH unable to open named pipe.
- Cause: open() failed to open named pipe ?/dbs/mon2arch_@.
- Action: Make sure that the OS userid of the currently running database has search permission for the ORACLE_HOME/dbs directory. The max number of open files may have been exceeded.
- ORA-09847: soacon: ARCH unable to open named pipe.
- Cause: open() failed to open named pipe ?/dbs/arch2mon_@.
- Action: Make sure that the OS userid of the currently running database has search permission for the ORACLE_HOME/dbs directory. The max number of open files may have been exceeded.
- ORA-09850: soacon: Archmon unable to lock named pipe.
- Cause: fcntl() failed to set write lock on named pipe ?/dbs/arch2mon_@.
- Action: Make sure that archmon is not already active on another terminal for this ORACLE_SID. Only one archmon session is allowed at a time for a given instance.
- ORA-09851: soacon: Archmon unable to lock named pipe.
- Cause: fcntl() failed to set read lock on named pipe ?/dbs/mon2arch_@.
- Action: Make sure that archmon is not already active on another terminal for this ORACLE_SID. Only one archmon session is allowed at a time for a given instance.
- ORA-09853: snyRemovePort: bad return code from request.
- Cause: The request to remove a port from the callback set returned a failure code.
- Action: Possible operating system error. 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.
- Action: Possible operating system error. Contact Oracle support.
- ORA-09855: removeCallback: bad message format.
- Cause: The routine received an incorrectly formatted request.
- Action: Internal error. Contact Oracle support.
- ORA-09856: smpalo: vm_allocate error while allocating pga.
- Cause: The vm_allocate system call returned an error.
- Action: Check returned error. Possibly out of system resources.
- ORA-09857: smprset: vm_protect error while protecting pga.
- Cause: The vm_protect system call returned an error.
- Action: Internal error. Contact Oracle support.
- ORA-09858: sfngat: the input file name is not in the OMF format
- Cause: The function sfngat() received a filename which is not an OMF file name.
- Action: Further diagnostic information should be in the error stack.
- ORA-09859: sfngat: the input file name is not in the autobackup OMF format
- Cause: The function sfngat() received a filename which is not an autobackup OMF file name.
- Action: Further diagnostic information should be in the error stack.
- ORA-09870: spini: failure initializing maximum number of open files.
- Cause: ulimit system call returned an error.
- Action: Check errno.
- ORA-09871: TASDEF_NAME: translation error while expanding ?/dbs/tasdef@.dbf.
- Cause: Failure of sltln(?/tasdef@.dbf) while creating test and set pages.
- Action: Check additional return error for more information.
- ORA-09872: TASDEF_CREATE: create failure in creating ?/dbs/tasdef@.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 tasdef@.dbf file.
- Cause: Unable to open tasdef@.dbf file.
- Action: Check errno. Possible permission problem. Verify that tasdef@.dbf file exists.
- ORA-09874: TASDEF_READ: read error, unable to read tasdef@.dbf file.
- Cause: Read system call returned an error when attempting to read ?/dbs/tasdef@.dbf.
- Action: Check errno returned. Sgadef file may be corrupted or incompatible with oracle version.
- ORA-09875: TASDEF_WRITE: write error when writing ?/dbs/tasdef@.dbf file.
- Cause: Write call failed.
- Action: Check errno returned. Possibly out of space on device.
- ORA-09876: TASDEF_CLOSE: unable to close ?/dbs/tasdef@.dbf file.
- Cause: Close system call returned an error.
- Action: Check errno returned. Possible operating system failure.
- ORA-09877: sstascre: shmget error, unable to get a shared memory segment.
- Cause: Error in shmget.
- Action: Check errno returned. 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: Check errno returned.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: Check errno returned.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: Check errno returned.
- ORA-09881: sstasfre/sstasdel: shmdt error, unable to detach tas read page
- Cause: Error in shmdt.
- Action: Check errno returned.
- ORA-09882: sstasfre/sstasdel: shmctl error, unable to remove tas shm page
- Cause: Error in shmctl.
- Action: Check errno returned.
- ORA-09883: Two Task interface: oratab file does not exist
- Cause: The oratab file does not exist.
- Action: Install oracle before you use it or recreate the oratab file.
- ORA-09884: Two Task interface: SID doens’t match current PU
- Cause: You are trying to start oracle on another PU than you configured oracle 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: You have probably exceeded the maximum number of open file descriptors per user or the system file table is full. Note the operating system error code and contact your system administrator.
- ORA-09886: osnTXtt: translation error while expanding txipc@.trc.
- Cause: Failure of sltln(txipc@.trc) while creating debug channel.
- Action: Check additional return error for more information.
- 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: You have probably exceeded the maximum number of open file descriptors per user or the system file table operating system error code and contact your system administrator.
- ORA-09889: osnTXtt: access error on oracle executable
- Cause: The txipc 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-09890: osnTXtt: malloc failed
- Cause: The txipx driver failed to allocate enough heap space for its context area buffers.
- Action: Contact your customer support representative.