Release 8.0.4
A58312-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
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.
Cause: PROCESSES init.ora parameter exceeded.
Action: Decrease the PROCESSES parameter and restart.
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.
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.
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.
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.
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.
Cause: The bind system call failed on the socket.
Action: Examine additional information for OS error. Try connecting again.
Cause: The accept system call failed on the socket.
Action: Examine additional information for OS error. Try connecting again.
Cause: The internal buffer is not big enough to hold the message read. This is an internal error.
Action: Contact Oracle Support.
Cause: An existing connection has already been made from log archiver to orasrv.
Action: Stop trying to connect.
Cause: The TXIPC driver cannot obtain the name of the PU. This is possibly an OS error.
Action: Verify that the PUs are named (consistent).
Cause: Orasrv cannot obtain the name of the PU. This is possibly an OS error.
Action: Verify that the PUs are named (consistent).
Cause: One oracle process died while still holding a lamport latch.
Action: Exit (kill) all oracle user processes. Shutdown (abort) and restart Oracle RDBMS kernel.
Cause: The internal limit on the number of user interrupt handlers has been exceeded.
Action: Reduce the number of simultaneous logons, or reduce the number of user interrupt handlers.
Cause: Malloc() failed to allocate space to hold user interrupt handler.
Action: Possibly, there is a memory resource shortage.
Cause: The handle passed to osncui is out of the valid range.
Action: Use a valid handle.
Cause: The vm_region system call failed to get virtual memory region statistics.
Action: Examine return code in sercerrno. Possible operating system failure.
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].
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].
Cause: The mmap or write system call returned an error. This is an internal error.
Action: Contact Oracle Support.
Cause: The mmap system call returned an error. This is an internal error.
Action: Contact Oracle Support.
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.
Cause: The vm_allocate system call attached the SGA at an incorrect location.
Action: Verify that the SGA attach address is valid.
Cause: The call pws_detach to (Oracle helper) failed.
Action: Verify that the server is still active. Examine the error code returned in sercerrno, and look for error messages in the server log file.
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.
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.
Cause: The port_rename system call failed. This is possibly an internal error.
Action: Examine return code in sercerrno. Contact Oracle Support.
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.
Cause: The port_allocate system call failed. This is possibly due to resource exhaustion.
Action: Examine return code in sercerrno. Contact Oracle Support.
Cause: Function was passed an invalid oracle process ID. This is an internal error.
Action: Additional information indicates the invalid process ID.
Cause: Function was passed an invalid oracle process ID. This is an internal error.
Action: Contact Oracle Support.
Cause: The port_allocate system call failed. This is possibly due to a system resource shortage.
Action: Examine the error code in sercerrno.
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.
Cause: The port_allocate system call failed. This is possibly due to a system resource shortage.
Action: Examine the error code in sercerrno.
Cause: The netname_check_in call failed.
Action: Examine the error code in sercerrno. Verify that the network name server is running.
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.
Cause: The pipe driver failed to send a break message to the oracle shadow process break thread.
Action: Contact Oracle Support.
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.
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.
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.
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.
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.
Cause: The mach driver failed to allocate enough vm space for its I/O buffers.
Action: Decrease the value of buffer_size parameter in the two-task driver hoststring.
Cause: The msg_send system call failed while flushing the mach driver's send buffer. This is an internal error.
Action: Contact Oracle Support.
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.
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.
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.
Cause: The msg_send system call failed while sending a mach driver break. This is an internal error.
Action: Contact Oracle Support.
Cause: The mach driver received a message having an unrecognizable message type. This is an internal error.
Action: Contact Oracle Support.
Cause: The mach driver received a message having an unrecognizable message type. This is an internal error.
Action: Contact Oracle Support.
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.
Cause: The mach two-task driver failed to reset the connection. This is an internal error.
Action: Contact Oracle Support.
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.
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.
Cause: The routine failed to allocate or set the task's notify port.
Action: Possible operating system error. Contact Oracle Support.
Cause: The port_allocate system call failed; system resources might be exhausted. This is possibly an operating system error.
Action: Contact Oracle Support.
Cause: Open system call returned an error.
Action: Examine errno.
Cause: Processing option passed is of incorrect format.
Action: Consult IUG for permissible formats.
Cause: Read system call returned an error.
Action: Examine errno. Verify that file exists.
Cause: Read system call returned an error.
Action: Examine errno. Verify that file exists.
Cause: Close system call returned an error.
Action: Examine errno.
Cause: Additional information indicates error returned from sltln.
Action: Examine additional information.
Cause: Malloc system call returned an error. The system might have run out of heap space.
Action: Examine additional information for the OS error.
Cause: The length of the name of the user being looked up is longer than size of the buffer provided by the calling routine. This is an internal error.
Action: Contact Oracle Support.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: The oracle executable failed to convert the string representation of a label to binary format.
Action: Re-enter a valid label.
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.
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.
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.
Cause: The oracle executable failed to initialize the library used to obtain security information. This is an internal error.
Action: Contact Oracle Support.
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.
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.
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.
Cause: The buffer that oracle uses to hold the expanded name of a too small.
Action: Contact Oracle Support.
Cause: This is an internal error.
Action: Contact Oracle Support.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: System call atomic_op() return error.
Action: Examine additional information in the trace file.
Cause: System call atomic_op() return unexpected error.
Action: Examine additional information in the trace file.
Cause: System call atomic_op() return unexpected error.
Action: Examine additional information in the trace file.
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.
Cause: The msg_rpc system call returned an error. This is an internal error.
Action: Contact Oracle Support.
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.
Cause: The routine received an incorrectly formatted request. This is an internal error.
Action: Contact Oracle Support.
Cause: The routine received an incorrectly formatted request. This is an internal error.
Action: Contact Oracle Support.
Cause: The port_status system called failed. This is possibly an operating system error.
Action: Contact Oracle Support.
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.
Cause: The port_set_add system called failed. This is possibly an operating system error.
Action: Contact Oracle Support.
Cause: The malloc library call failed to allocate space for a callback link. This is possibly an operating system error.
Action: Contact Oracle Support.
Cause: The port port_set_remove system call failed. This is possibly an operating system error.
Action: Contact Oracle Support.
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.
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.
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.
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.
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.
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.
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.
Cause: The routine received an incorrectly formatted request. This is an internal error.
Action: Contact Oracle Support.
Cause: The vm_allocate system call returned an error. Possibly, there is a shortage of system resources.
Action: Examine error.
Cause: The vm_protect system call returned an error. This is an internal error.
Action: Contact Oracle Support.
Cause: ulimit system call returned an error.
Action: Examine errno.
Cause: Failure of sltln($ORACLE_HOME/tasdefsid.dbf) while creating test and set pages.
Action: Examine additional return error for more information.
Cause: Create() failed when trying to create the tasdef file.
Action: Verify permissions on $(ORACLE_HOME)/dbs directory.
Cause: Failure to open tasdefsid.dbf file. This is possibly a permission problem.
Action: Examine errno. Verify that tasdefsid.dbf file exists.
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.
Cause: Write call failed. Possibly, there is a shortage of space on device.
Action: Examine errno.
Cause: Close system call returned an error. Possibly this is an operating system failure.
Action: Examine errno.
Cause: Error in shmget.
Action: Examine errno. Verify that enough shared memory is available on the system.
Cause: Error in shmat.
Action: Examine errno.Verify that enough shared memory is available on the system.
Cause: Error in shmat.
Action: Examine errno.Verify that enough shared memory is available on the system.
Cause: Error in shmdt.
Action: Examine errno.
Cause: Error in shmdt.
Action: Examine errno.
Cause: Error in shmctl.
Action: Examine errno.
Cause: The oratab file does not exist.
Action: Install Oracle before using it, or recreate the oratab file.
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.
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.
Cause: Failure of sltln(txipcsid.trc) while creating debug channel.
Action: Examine additional return error for more information.
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.
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.
Cause: The txipx driver failed to allocate enough heap space for its context area buffers.
Action: Contact Oracle Support.
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.
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.
Cause: No entry exists for the user in the oracle password file.
Action: Have the database administrator install a password entry by running orapasswd.
Cause: The password entered by the user was incorrect.
Action: Enter the correct password.
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.
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.
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.
Cause: The oracle executable failed to encrypt a password. This is an internal error.
Action: Contact Oracle Support.
Cause: A user attempted to connect as "internal", but did not specify a password.
Action: Connect as internal again and specify a password.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: An attempt to close a password file failed.
Action: Examine the UNIX error number for the specific reason.
Cause: The removal of the old password file failed.
Action: Examine the UNIX error number for the specific reason.
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.
Cause: The oracle executable failed to complete the saving of the current password file.
Action: Examine the UNIX error number for the specific reason.
Cause: The oracle executable failed to create a password file.
Action: Examine the UNIX error number for the specific reason.
Cause: The oracle executable failed to change a password file to be read only.
Action: Examine the UNIX error number for the specific reason.
Cause: The oracle executable failed to save the previous values of selected signal handlers. This is an internal error.
Action: Contact Oracle Support.
Cause: The oracle executable failed to restore the previous values of selected signal handlers. This is an internal error.
Action: Contact Oracle Support.
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".
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.
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.
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.
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."
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.
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.
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.
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.
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.
Cause: The oracle executable failed to get its privileges from the operating system.
Action: Contact Oracle Support.
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.
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.
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.
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.
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.
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.
Cause: The attempt to send a termination signal to IMON failed. This is an internal error.
Action: Contact Oracle Support.
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.
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.
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.
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.
Cause: Failure of sltln in scumnt.
Action: Examine additional return error for more information.
Cause: Open system call returned an error.
Action: Examine errno
Cause: Lock file operating system call returned an error.
Action: Examine errno.
Cause: The process failed to initialize the SDI channel properly.
Action: Correct the operating system error and retry the operation.
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.
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.
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.
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.
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.
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.
Cause: The process failed to add a page to the SDI buffer pool.
Action: Correct the operating system error and retry the operation.
Cause: The process failed to remove a page to the SDI buffer pool.
Action: Correct the operating system error and retry the operation.
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.
Cause: File does not exist or is not accessible.
Action: Restart the instance to create the SGA definition file.
Cause: Read() operation failed.
Action: Examine errno, and take appropriate action.
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.
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.
Cause: skgmsdef struct is corrupted and/or segment addresses are modified.
Action: Safely shut down instance and mount SGA segments again.
Cause: Pointer to skgmsdef struct used without validating it.
Action: Assign a valid address to the skgmsdef struct pointer before using it.
