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.
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.
No hay comentarios:
Publicar un comentario