Release 8.0.4
A58312-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
Cause: The environment variable (ORACLE_SID) is not set.
Action: Set ORACLE_SID environment variable.
Cause: $(ORACLE_HOME) environment variable not set.
Action: Set $ORACLE_HOME.
Cause: The sltln name translation routine was called with invalid arguments. The input or output strings were either NULL or 0 length. This is probably an internal error.
Action: Contact Oracle Support.
Cause: A string was passed to sltln containing a long environment variable. sltln accepts environment names of 30 or less characters.
Action: Shorten environment variable name to less than 30 characters.
Cause: The sltln routine is given a maximum length buffer to expand the name into. An overflow of this buffer occurred. This is possibly an internal error.
Action: Verify output buffer length stored in sercose[0]. Path names are limited to 255 characters.
Cause: Time() system call returned an error. This is possibly an OS error.
Action: Examine additional information returned. Contact Oracle Support.
Cause: gettimeofday() system call returned an error. This is possibly an OS error.
Action: Examine additional information returned. Contact Oracle Support.
Cause: The sigpidu routine is given a maximum length buffer to hold process ID string. An overflow of this buffer occurred. This is an internal error.
Action: Contact Oracle Support.
Cause: The fsync system call returned an error. This is possibly an OS error.
Action: Examine additional information returned. Contact Oracle Support.
Cause: The size of the file to be opened exceeded the OS limit imposed on this process.
Action: Run osh to increase the file size limit.
Cause: Getrusage system call returned an error. This is possibly an OS error.
Action: Examine additional information returned. Contact Oracle Support.
Cause: gettimeofday system call returned an error. This is possibly an OS error.
Action: Examine additional information returned in OS reference manual. Contact Oracle Support.
Cause: Times system call returned an error. This is possibly an OS error.
Action: Examine additional information returned. Contact Oracle Support.
Cause: Times system call returned an error. This is possibly an OS error.
Action: Examine additional information returned in OS reference manual. Contact Oracle Support.
Cause: uname system call returned an error. This is possibly an OS error.
Action: Examine additional information returned in OS reference manual. Contact Oracle Support.
Cause: Getrusage 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: Gethostname system call returned an error. This is possibly an OS error.
Action: Examine additional information returned in OS reference manual. Contact Oracle Support.
Cause: Getenv call returned a null pointer.
Action: Set the environment variable and try again.
Cause: UNIX system() call failed.
Action: Examine system error message.
Cause: Malloc failed to allocate space to hold spooler arguments. The process may have run out of heap space.
Action: Examine additional information returned in OS reference manual. Contact Oracle Support.
Cause: Wait returned an error when waiting for spool job to complete. This is possibly a spooler program error.
Action: Examine additional information returned. Refer to the OS reference manual. Contact Oracle Support.
Cause: Exec failed when starting line printer spooler command. It is likely that either the default line printer command, or ORACLE_LPPROG, is incorrectly set.
Action: Verify that the default line printer command and ORACLE_LPPROG are set correctly. Set ORACLE_LPPROG to working line printer spooler.
Cause: The line printer spooler exited with a non-zero return value. This probably indicates an error in spooling file.
Action: Verify that line printer spooler is up. Verify that ORACLE_LPPROG, and ORACLE_LPARG are set properly. Examine exit value returned for additional information.
Cause: Fork system call failed to create additional process. It is probable that the resource limit has been reached.
Action: Examine additional information returned. Retry operation. Contact system administrator.
Cause: The ulimit system call returned an error.
Action: Examine errno. Contact Oracle Support.
Cause: Additional information returned is error returned from sltln.
Action: Examine additional information.
Cause: The ioctl call returned an error. The process may have run out of heap space.
Action: Examine additional information for errno. Contact Oracle Support.
Cause: The ioctl call returned an error. The process may have run out of heap space.
Action: Examine additional information for errno. Contact Oracle Support.
Cause: The ioctl call returned an error. The process may have run out of heap space.
Action: Examine additional information for errno. Contact Oracle Support.
Cause: Error in mpcntl system call.
Action: Examine errno. Contact system administrator.
Cause: Fopen failed to open file.
Action: Try to determine which file was not opened. Verify that the file exists and is accessible.
Cause: Function was called with an invalid argument. The file handle used was not obtained be slemcr. This is an internal error.
Action: Contact Oracle Support.
Cause: An error was encountered when closing the file. The process may have run out of heap space.
Action: Contact system administrator.
Cause: Function was called with an invalid file handle. File handle was not obtained by slemcr. This is an internal error.
Action: Contact Oracle Support.
Cause: Failure to seek to desired position in file. The process may have run out of heap space. This is possibly an internal error.
Action: Verify that the error message file is intact. Try to regenerate error message file. Contact Oracle Support.
Cause: Failure to write item to file. The process may have run out of heap space. This is possibly a permissions problem.
Action: Retry operation.
Cause: Failure to open error file. This is possibly a permissions problem.
Action: Verify permission on error message file. Examine additional information for errno.
Cause: Function was called with an invalid file handle. Handle was not obtained by previous call to slemop. This is an internal error.
Action: Contact Oracle Support.
Cause: Failure to close file. This is possibly an OS error.
Action: Contact system administrator. Examine additional information for errno.
Cause: Function was called with invalid file handle. Handle was not obtained by call to slemop. This is an internal error.
Action: Contact Oracle Support.
Cause: Failure to seek to desired position in file. This is possibly an OS error.
Action: Verify that error file is still intact. Verify space on device. Contact system administrator. Examine additional information for errno.
Cause: Failure to read file. This is possibly an OS error.
Action: Verify that error file is intact. Regenerate error message file. Contact Oracle Support. Examine additional information for errno.
Cause: Additional information indicates error returned from sltln.
Action: Examine additional information.
Cause: The fgets call read only part of the line, because the supplied buffer was not big enough. This is an internal error.
Action: Contact Oracle Support. Additional information indicates how big the supplied buffer was.
Cause: An attempt was made to create a file that exceeds the process's file size limit.
Action: Run osh to raise the file size limit.
Cause: An attempt was made to move and write to a bad device address.
Action: Examine errno. There may be a lack of space on device.
Cause: sfofi returns an error. This is an internal error.
Action: Contact Oracle Support.
Cause: sfrfb returns an error. This is an internal error.
Action: Contact Oracle Support.
Cause: sfwfb returns an error. This is an internal error.
Action: Contact Oracle Support.
Cause: Open() returns an error. This is an internal error.
Action: Verify that /proc has the correct permissions.
Cause: An error occurred when trying to get first semaphore set.
Action: Examine errno. Verify that system is configured to have semaphores. Verify that enough semaphores are available. Additional information indicates how many semaphores were requested.
Cause: Semget failed to even allocate a single semaphore. Either they are all in use, or the system is not configured to have any semaphores.
Action: Verify that all semaphores are in use. Verify that system is configured to have semaphores. Examine errno.
Cause: semget system call returned an error. There is possibly a resource limit problem.
Action: Examine errno. Verify that enough semaphores are available in system. If additional errors occur in destroying the semaphore sets, then sercose[0] will be non-zero. If this occurs, remove the semaphore sets using ipcrm.
Cause: semctl system call returned an error.
Action: Verify semaphore sets. This may require manual cleanup. Examine additional information returned. Consult OS reference manual.
Cause: An error occurred while translating the name of the oracle executable.
Action: Examine sercose[0] for error returned from sltln. Perhaps $(ORACLE_HOME) is not set correctly.
Cause: System failed to set up signal handler.
Action: Examine errno and sercose[0] for the signal number that failed.
Cause: System failed to set up signal handler to catch exceptions.
Action: Examine errno and sercose[0] for the signal number that failed.
Cause: Error occurred when expanding program name ora_PNAME_sid. The result of this translation is put in argv[0] of oracle process.
Action: Examine error returned by sltln returned in sercose[0].
Cause: An error occurred when creating a new process.
Action: Examine errno. Perhaps a system limit on the number of processes has been exceeded.
Cause: An oracle detached process died shortly after startup. Wait() indicates that a child process terminated.
Action: Examine $ORACLE_HOME/dbs directory for trace or core files. Examine errno.
Cause: Wait system call returned an error.
Action: Examine errno.
Cause: Kill system call returned an error. This is possibly an attempt to destroy an already gone process.
Action: Examine errno.
Cause: This is an internal error.
Action: Contact Oracle Support.
Cause: Kill system call returned an error. This is possibly an OS error.
Action: Examine errno. Additional information indicates the process ID tested.
Cause: Semop system call returned an error. Semaphore set may not exist.
Action: Examine errno. Semaphore ID is returned in sercose[0]. Verify semaphore set exists. A possible cause for this error is that a "shutdown abort" was done while this process was running.
Cause: Semop system call returned an error. Semaphore set may not exist.
Action: Examine errno. Semaphore ID is returned in sercose[0]. Verify semaphore set existence. A possible cause for this error is that a "shutdown abort" was done while this process was running.
Cause: Function was passed an invalid oracle process ID. This is an internal error.
Action: 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: Getpwuid() failed to find an entry in the passwd file for a user.
Action: Add an entry for the user in the passwd file.
Cause: Detached process successfully execed, but died shortly thereafter.
Action: Examine termination code for information about why process exited. Look for core dump or trace file. Additional information indicates exit code and termination status.
Cause: An error occurred while trying to set an interval timer. This is probably a porting problem.
Action: Examine errno.
Cause: Function was called with an invalid oracle process number (0). This is an internal error.
Action: Contact Oracle Support.
Cause: Semaphore ID fetched from SGA was not initialized to valid value. Additional information returned is semaphore set index, and oracle process number. This is an internal error.
Action: Verify semaphore set index. Verify oracle process number.
Cause: Semaphore ID fetched from SGA contained an invalid value. Additional information returned is semaphore set index and oracle process number. This is an internal error.
Action: Verify semaphore set index. Verify oracle process number.
Cause: Failure to access oracle program. Verify that $ORACLE_HOME/bin/oracle or $ORABCKPRG exist and are executable.
Action: Examine errno.
Cause: The kill system call returned an error. This is possibly an attempt to signal a process which does not exist.
Action: Examine errno.
Cause: A group has not been set up for dba users.
Action: Contact system administrator. Set up dba group in /etc/group.
Cause: A 0 pid was passed to spdde. This is an internal error.
Action: Contact Oracle Support.
Cause: Splon constructed an ops$username logon which exceeded the allotted buffer space.
Action: Use a shorter UNIX username or use an Oracle username. Contact Oracle Support.
Cause: An error occurred when trying to get first semaphore set.
Action: Examine errno. Verify that system is configured to have semaphores. Verify that enough semaphores are available. Additional information indicates how many semaphores were requested.
Cause: The ioctl call returned an error. This is possibly an OS error.
Action: Examine additional information for errno. Contact Oracle Support.
Cause: Times system call returned an error. This is possibly an OS error.
Action: Examine additional information returned. Contact Oracle Support.
Cause: The internal buffer is not big enough to hold the archive control string. This is an internal restriction.
Action: Try a shorter archive control string.
Cause: An invalid volume size was specified.
Action: Specify a valid volume size in the archive control string.
Cause: Some non-numeric text follows the volume size specification.
Action: Enter a correct archive control string.
Cause: Volume size was specified for a disk file.
Action: If archiving to a disk file, do not specify its volume size.
Cause: Stat on the log archiving device failed.
Action: Examine the returned OSD error for the reason of failure.
Cause: Log archiving to this device is unsupported.
Action: Try log archiving to a supported device.
Cause: The specified path name is not a directory.
Action: Verify that the archive destination directory exists.
Cause: Failure of sltln($ORACLE_HOME/dbs/sgadefsid.dbf) in smscre.
Action: Examine additional return error for more information.
Cause: The sgadef file should not exist when trying to create the SGA. Otherwise a running instance could be clobbered. The error from sltln is stored in sercose[0].
Action: Verify that database is really down, and delete the sgadef file. This should only happen when system has crashed with the database up. Cleaning up sgadef files can be done out of /etc/rc.
Cause: Create() failed when trying to create the sgadef file.
Action: Verify permissions on $(ORACLE_HOME)/dbs directory.
Cause: The database buffer size must be a multiple of the database block size and less than the maximum block size.
Action: DB_BLOCK_SIZE parameter is correct in init.ora.
Cause: The redo buffer size must be a multiple of machine block size.
Action: Verify that the LOG_BUFFER init.ora parameter is correct.
Cause: The ftok() library call failed in sms1sg().
Action: Verify that the $ORACLE_HOME/dbs/sgadefsid.dbf file exists. If it does, then this is a possible system failure. Perhaps System V compatibility is not enabled.
Cause: Error in shmget. The code fails to find a single segment large enough for the entire SGA, but cannot continue to the next allocation model because of a fatal error.
Action: Examine errno. Verify that enough shared memory is available on the system to fit the entire SGA.
Cause: Failed to attach shared memory segment, after having gotten it.
Action: Examine errno. Verify that the SGA attach address is valid.
Cause: Write call failed in smscre. Possibly, the device is out of space.
Action: Examine errno.
Cause: Close system call returned an error. This is possibly an operating system failure.
Action: Examine errno.
Cause: All SGA allocation models have been tried, but none succeeded. This is possibly an Oracle system error.
Action: Try reconfiguring the UNIX kernel to fit the entire SGA into one segment.
Cause: Failure to expand out $ORACLE_HOME/dbs/sgadefsid.dbf file name.
Action: Verify that $(ORACLE_HOME) and (ORACLE_SID) are properly set. Examine error number from sltln returned for additional error.
Cause: Open failed when trying to open sgadef.dbf file. This is possibly a permission problem.
Action: Verify errno. Verify that sgadef.dbf file exists.
Cause: Read system call returned an error when attempting to read $ORACLE_HOME/dbs/sgadefsid.dbf.
Action: Examine errno. Sgadef file may be corrupted or incompatible with Oracle version.
Cause: Shmctl(IPC_RMID) called failed when trying to destroy shared memory segment. This is possibly a permission problem.
Action: Examine errno. Verify that shared exist. It may be necessary to manually remove segments.
Cause: An error occurred in close(), when closing sgadef.dbf file. This is possibly an operating system error.
Action: Verify that sgadef.dbf file has been deleted.
Cause: Unlink() error occurred when attempting to destroy sgadef.dbf file.
Action: Examine errno. Verify that sgadef.dbf file has been destroyed. This may require manual cleanup.
Cause: Error occurred translating $ORACLE_HOME/dbs/sgadefsid.dbf.
Action: Verify that $(ORACLE_HOME) and (ORACLE_SID) are set correctly. Examine error returned from sltln for additional error.
Cause: Failure to open sgadef.dbf file. This is possibly a permission problem.
Action: Examine errno. Verify that sgadef.dbf file exists.
Cause: Read had an error when reading sgadef.dbf file.
Action: Examine errno. Verify that the file exists and is correct size.
Cause: Failure to attach segment. This is possibly an operating system error.
Action: Examine errno. Sercose[0] returns segment ID. Verify that segment exists and that permissions are correct.
Cause: sercose[0] returns segment ID.
Action: Examine errno.
Cause: Failure to close sgadef.dbf file. This is possibly an OS error.
Action: Retry.
Cause: Problem deleting shared segments.
Action: Retry. Examine errno. This may require manual cleanup of shared memory segments.
Cause: Malloc library routine returned an error. Possibly, it is out of swap space.
Action: Examine errno.
Cause: Malloc library routine returned an error. Possibly, it is out of swap space.
Action: Examine errno.
Cause: Smsfre was called when the SGA was not mapped. This is an internal error.
Action: Contact Oracle Support.
Cause: smpdal was called when the PGA had not been previously created. This is an internal error.
Action: Contact Oracle Support.
Cause: shmget system call returned a fatal error.
Action: Examine errno. Additional information indicates the SGA model attempted.
Cause: The internal data structure which holds segment information is full.
Action: Reconfigure the UNIX kernel to have bigger segments.
Cause: The fixed portion of the SGA is too big to fit contiguously into one segment.
Action: Reconfigure the UNIX kernel to have bigger segments.
Cause: The variable portion of the SGA is too big to fit contiguously into one segment.
Action: Reconfigure the UNIX kernel to have bigger segments.
Cause: Redo block size is too big, preventing each buffer from being allocated contiguously.
Action: Reconfigure the UNIX kernel to have bigger segments, or reduce the value of LOG_BUFFER parameter in init.ora.
Cause: Database block size is too big, preventing each buffer from being allocated contiguously.
Action: Reconfigure the UNIX kernel to have bigger segments, or reduce the value of DB_BLOCK_SIZE parameter in init.ora.
Cause: The internal data structure which holds segment information is full.
Action: Reconfigure the UNIX kernel to have bigger segments.
Cause: The ftok() library call failed in smsmat().
Action: Verify that sgadef.dbf file exists. If it does, then this is a possible system failure. Perhaps System V compatibility is not enabled. Additional information indicates the SGA model attempted.
Cause: Error in shmget.
Action: Examine errno. Verify that enough shared memory is available on the system to fit the entire SGA. Additional information indicates the SGA model attempted.
Cause: Failed to attach shared memory segment, after having gotten it.
Action: Examine errno. Verify that SGA attach address is valid. Additional information indicates the SGA model attempted.
Cause: The access system call returned an error. This is possibly an OS error.
Action: Examine errno returned and verify the permission on the sga file.
Cause: The internal buffer is not big enough to hold the number of semaphore set identifiers requested.
Action: Reconfigure OS to have more semaphores per set.
Cause: An error occurred while expanding the file name to open. Additional information returns error generated in translation routine.
Action: Lookup additional error code for further information.
Cause: fopen library routine returned an error.
Action: Verify existence and permissions.
Cause: fclose library routine returned an error. This is possibly an internal error.
Action: Contact Oracle Support.
Cause: The name for the message file overflows internal buffer.
Action: Try making the complete path-name of the message file shorter by reorganizing the directory hierarchy.
Cause: The system failed to restore user exception handlers.
Action: Examine errno and sercose[0] for the signal number that failed.
Cause: The system failed to restore user signal handlers.
Action: Examine errno and sercose[0] for the signal number that failed.
Cause: The DB_WRITERS parameter in init.ora exceeds the system-dependent maximum, or is less than 0.
Action: Change the DB_WRITERS parameter in init.ora.
Cause: The master database writer timed out waiting for a write or close to complete. One of the database writers may have stopped running.
Action: Examine all database writer trace files. Shut down the database and try to warm start.
Cause: An impossible request for binary to decimal conversion was made.
Action: This conversion cannot be performed.
Cause: An impossible request for binary to decimal conversion was made.
Action: This conversion cannot be performed.
Cause: An impossible request for binary to decimal conversion was made.
Action: This conversion cannot be performed.
Cause: An impossible request for decimal to binary conversion was made.
Action: This conversion cannot be performed.
Cause: An impossible request for decimal to binary conversion was made.
Action: This conversion cannot be performed.
Cause: The supplied buffer is not big enough to hold the full path name.
Action: The construction of the full path name cannot be performed.
Cause: One of the database writer processes failed to locate its entry in the SGA.
Action: Contact Oracle Support.
Cause: Malloc() failed to allocate buffer for storing ORACLE_PATH. System has run out of heap space.
Action: Additional information indicates errno.
Cause: The slpath routine is given a maximum length buffer to expand the name into. An overflow of this buffer occurred. This is possibly an internal error.
Action: Examine output buffer length stored in sercose[0] and constructed pathname length in sercose[1].
Cause: One or more of the database writer processes is no longer running.
Action: Examine the trace files for the database writers. Shut down the database and try to warm start.
Cause: An error occurred when the database writer called the system timing function.
Action: Examine the database writer trace file. Shut down database and try to warm start.
Cause: An error occurred when the database writer called the system timing function.
Action: Examine the database writer trace file. Shut down database and try to warm start.
Cause: An oracle error occurred when translating the location of the dump file.
Action: Examine the error code.
Cause: An oracle error occurred when translating the location of the dbs directory.
Action: Examine additional information for the error returned from sltln.
Cause: chdir system call returned an error. This is possibly a permission problem.
Action: Examine additional information for the OS error code.
Cause: The ftok() library call failed in smsgsg().
Action: Verify that the $ORACLE_HOME/sgadefsid.dbf file exists. If it does, this is a possible system failure. Perhaps System V compatibility is not enabled. The additional information indicates the segment where the error occurred.
Cause: A shared memory segment used for all or part of the SGA failed to be retrieved.
Action: Use the system error number in the error message to determine why the segment failed to be retrieved. If it does not exists, shutdown the database using the "abort" option, and then restart it. If the get failed because the permissions are incorrect, verify that the ownership of the oracle executable is the same as that on the shared memory segment.
Cause: When smsgsg() gets a segment, it re-calculates the key for the segment. It then compares the value against the value stored in the sgadef file. If they do not match, then the file is probably corrupt.
Action: Shutdown the database and restart it.
Cause: The server process failed to fork a child 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: An attempt was made to make a process sleep when it was already sleeping. This platform does not support this capability.
Action: Try the SLEEP command when the process is not sleeping.
Cause: The wakeup monitor process died.
Action: Warm start instance.
Cause: An improperly aligned function address was specified.
Action: Use a properly aligned function address.
Cause: An invalid function address was specified.
Action: Use a valid function address.
Cause: An invalid function name was specified.
Action: Use a valid function name.
Cause: An invalid function name/address was specified.
Action: Use a valid function name/address.
Cause: An OS exception occurred which should result in the creation of a core file. This is an internal error.
Action: Contact Oracle Support.
Cause: The directory specified as the value for the stated parameter failed to be used.
Action: Verify that the directory specified is a valid directory/file specification.
Cause: oracle failed to create a shared arena file.
Action: Use sercerrno field to determine cause of failure.
Cause: oracle attempted to create more shared arena files than permitted.
Action: Raise the value for MAX_ARENA in init.ora.
Cause: oracle failed to acquire a shared arena lock.
Action: Examine result code in sercerrno to determine the cause of failure.
Cause: Error in vm_mapmem. Failed to create SGA as a single shared memory segment.
Action: Examine result code returned in sercose[0].
Cause: The vm_mapmem system call attached the SGA at an incorrect location.
Action: Verify that the SGA attach address is valid.
Cause: The vm_inherit system called failed to change the inheritance of the SGA. This is possibly an operating system failure.
Action: Examine result code returned in sercose[0].
Cause: Error in vm_mapmem. Failure to create a segment of the SGA.
Action: Examine result code returned in sercerrno.
Cause: The vm_mapmem system call attached an SGA segment at an incorrect location.
Action: Verify that the SGA attach address is valid.
Cause: The vm_inherit system call failed to change the inheritance of a segment of the SGA. This is possibly an operating system failure.
Action: Examine result code returned in sercerrno.
Cause: The cluster_stat system call failed to return status for the cluster. This is possibly an operating system failure.
Action: Examine result code in sercose[0].
Cause: Failure to expand out $ORACLE_HOME/dbs/sgadefsid.dbf file name.
Action: Verify that $(ORACLE_HOME) and (ORACLE_SID) are properly set. Examine error number returned from sltln in sercose[0].
Cause: An error occurred in close while closing the file $ORACLE_HOME/dbs/sgadefsid.dbf. This is possibly an operating system error.
Action: Verify that the sgadef.dbf file has been deleted.
Cause: Failure to expand out $ORACLE_HOME/dbs/sgadefsid.dbf file name.
Action: Verify that $(ORACLE_HOME) and (ORACLE_SID) are properly set. Examine error number returned from sltln in sercose[0].
Cause: The file $ORACLE_HOME/dbs/sgadefsid.dbf should not exist when trying to create the SGA; otherwise, a running instance could be clobbered.
Action: Verify that the database is down, and delete the sgadef.dbf file. This should only happen when the machine crashed with the database up.
Cause: Open failed when trying to create the file $ORACLE_HOME/dbs/sgadefsid.dbf.
Action: Verify permissions on the $(ORACLE_HOME)/dbs directory.
Cause: Failure to expand out $ORACLE_HOME/dbs/sgadefsid.dbf file name.
Action: Verify that $(ORACLE_HOME) and (ORACLE_SID) are properly set. Examine error number returned from sltln in sercose[0].
Cause: Open failed when opening the file $ORACLE_HOME/dbs/sgadefsid.dbf. This is possibly a permission problem.
Action: Examine errno. Verify that the file $ORACLE_HOME/dbs/sgadefsid.dbf exists.
Cause: The vm_mapmem or vm_allocate system call failed when attempting to attach a segment of the SGA.
Action: Examine result code returned in sercerrno. SGA segment number returned in sercose[1].
Cause: The vm_mapmem system call attached an SGA segment at an incorrect location.
Action: Verify that the segment exists and that the SGA attach address is valid.
Cause: The vm_inherit system call failed to change the inheritance of a segment of the SGA. This is possibly an operating system failure.
Action: Examine result code returned in sercerrno.
Cause: An error occurred in close while closing the file $ORACLE_HOME/dbs/sgadefsid.dbf. This is possibly an operating system failure.
Action: Examine errno.
Cause: The mset routine returned an error. Semaphore may not exist.
Action: Examine result code in sercerrno. Semaphore number returned in sercose[0].
Cause: The mclear routine returned an error. Semaphore may not exist.
Action: Examine result code in sercerrno. Semaphore number returned in sercose[0].
Cause: The cluster_status system call failed to get status information for the current cluster. This is possibly an operating system failure.
Action: Examine result code in sercose[0].
Cause: Failure to expand out $ORACLE_HOME/dbs/sgadefsid.dbf file name.
Action: Verify that $(ORACLE_HOME) and (ORACLE_SID) are properly set. Examine error number returned from sltln in sercose[0].
Cause: Open failed when opening the file $ORACLE_HOME/dbs/sgadefsid.dbf. This is possibly a permission problem.
Action: Examine errno. Verify that the file $ORACLE_HOME/dbs/sgadefsid.dbf exists.
Cause: Read had an error when reading sgadef.dbf file.
Action: Examine errno. Verify that file exists and is correct size.
Cause: An error occurred in close, while closing the file $ORACLE_HOME/dbs/sgadefsid.dbf. This is possibly an operating system failure.
Action: Examine errno.
Cause: The vm_statistics system call failed to get virtual memory statistics. This is possibly an operating system failure.
Action: Examine result code in sercerrno.
Cause: The vm_mapmem system call failed to get mapped memory statistics. This is possibly an operating system failure.
Action: Examine result code in sercerrno.
Cause: Lock manager must be initialized before converting locks. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_stat_lock failed. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_open or lm_open_convert failed. Possible lock manager failure.
Action: Examine result code in sercerrno.
Cause: When creating an instance, snlmini failed to change the permissions on $ORACLE_HOME/dbs/sgalm.dbf.
Action: Contact Oracle Support.
Cause: lm_attach failed to attach to lock manager instance. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_create failed to create lock manager instance.
Action: Verify permissions on $ORACLE_HOME/dbs, and remove $ORACLE_HOME/dbs/sgalm.dbf if it exists, then retry.
Cause: lm_convert failed to convert(get) lock. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_convert failed to put lock value. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_open failed. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_convert failed to get lock value. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_create failed. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: Lock manager must be initialized before releasing locks. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_stat_lock failed during lock release/cancel. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_convert failed during lock release/cancel. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_cancel failed during lock release/cancel. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_close failed during lock release/cancel. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: An error was encountered releasing the lock. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: Unknown or unexpected error code. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_wait failed. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: lm_post failed. This is possibly a lock manager failure.
Action: Examine result code in sercerrno.
Cause: The trace file cannot be created for writing.
Action: Verify if the dump directory exists, and whether it is writable.
Cause: The rescheduling driver /dev/resched is not found or is not working properly.
Action: Examine installation of the Oracle rescheduling driver in the AIX kernel.
Cause: The rescheduling driver /dev/resched is not open. This is an internal error.
Action: Contact Oracle Support.
