Release 8.0.4
A58312-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
Cause: The lock manager failed to open a lock.
Action: Verify that enough memory is available, and retry the operation.
Cause: The lock manager failed to convert a lock.
Action: Retry the operation.
Cause: The lock manager encountered an error closing a lock.
Action: Examine the lock manager status returned for additional information.
Cause: The lock manager encountered an error cancelling a convert request.
Action: Examine the lock manager status returned for additional information.
Cause: The lock manager returned an unexpected value.
Action: Examine the lock manager status returned for additional information.
Cause: The environment variable ORACLE_SID is not set.
Action: Set the ORACLE_SID environment variable.
Cause: Failure to translate $ORACLE_HOME/dbs/sgadefsid.dbf.
Action: Ensure that $ORACLE_HOME and ORACLE_SID are properly set.
Cause: The address file failed to open.
Action: Verify that ORACLE is up. Verify that the file $(ORACLE_HOME)/dbs/sgadefsid.dbf exists and has correct permissions.
Cause: The address file could not be read.
Action: Verify that the file $(ORACLE_HOME)/dbs/sgadefsid.dbf exists and contains a single line of text.
Cause: The System Commit Number has not yet been initialized.
Action: Contact Oracle Support
Cause: The oracle executable requested that an I/O error be returned for this operation.
Action: Contact Oracle Support.
Cause: The n_core system call failed. This is possibly due to insufficient memory.
Action: Specify a smaller number of buffers. Verify init.ora parameters.
Cause: The process cannot attach to the SGA. This happens if either the listener cannot attach, or if the process cannot communicate with the listener.
Action: Verify that the instance is up and running. Contact Oracle Support.
Cause: Probably, the listener process has died.
Action: Contact Oracle Support.
Cause: The n_core system call failed while detaching from the SGA.
Action: Note nCX error. Contact Oracle Support.
Cause: The instance listener address failed to be read from the sgadef file.
Action: Verify that $(ORACLE_HOME) and (ORACLE_SID) are set correctly. Additional information gives error return from ora_addr.
Cause: A process is wishing to attach to the SGA is on a different node from its instance's listener.
Action: Verify that $(ORACLE_HOME) and (ORACLE_SID) are set correctly. Contact Oracle Support.
Cause: The n_share call failed. This is possibly because the listener has died.
Action: Verify that the listener is running, and contact Oracle Support.
Cause: Attempting to attach to an SGA which has not yet been created.
Action: Verify that the instance is running. Contact Oracle Support.
Cause: The n_core system call failed while detaching from the SGA.
Action: Examine nCX error, and contact Oracle Support.
Cause: The file name of the lock manager address file is too long.
Action: Use a shorter parallel server name.
Cause: Failure to attach to lock manager. This is possibly because it is not running.
Action: Additional information is lock manager return code. Verify that lock manager is running.
Cause: An error was encountered detaching from the lock manager.
Action: Additional information is lock manager return code. Contact Oracle Support.
Cause: A process failed to connect to the nameserver.
Action: Verify that the nameserver is up and running. Additional information gives nameserver's returned status.
Cause: The listener nameserver entry for an instance failed to be found.
Action: Verify that the nameserver is up and running. Additional information gives nameserver's returned status.
Cause: The parallel server name ORACLE_PSRV was undefined.
Action: Set the environment variable ORACLE_PSRV, and try again.
Cause: The listener nameserver entry failed to free.
Action: Additional information gives nameserver's returned status. Contact Oracle Support.
Cause: The connection to the nameserver failed to close.
Action: Additional information gives nameserver's returned status. Contact Oracle Support.
Cause: A process failed to connect to the nameserver.
Action: Verify that the nameserver is up and running. Additional information gives nameserver's returned status.
Cause: The listener's addressing information failed to register.
Action: Verify that the nameserver is up and running. Additional information gives nameserver's returned status.
Cause: The connection to the nameserver failed to close.
Action: Additional information gives nameserver's returned status. Contact Oracle Support.
Cause: The connection to the nameserver failed to close.
Action: Additional information gives nameserver's returned status. Contact Oracle Support.
Cause: The listener's addressing information failed to be removed.
Action: Additional information gives nameserver's returned status. Contact Oracle Support.
Cause: Archive files failed to be created with the given archival control string.
Action: Verify that the volume exists.
Cause: The given archival control string expands into too many characters.
Action: Reduce archive control string length.
Cause: There is insufficient memory to return the requested value.
Action: Reduce memory usage and retry.
Cause: The requested environment variable is not set.
Action: Ensure that the variable name requested is correct.
Cause: There is no room to record the pid for a background process.
Action: Shutdown abort, and restart the database.
Cause: There is insufficient memory to expand the environment.
Action: Reduce memory usage and retry.
Cause: Failure to retrieve CPU times, because n_stat failed.
Action: Contact Oracle Support.
Cause: Oracle failed to open a file.
Action: Examine the UNIX errno returned for additional information.
Cause: Oracle failed to obtain information about an open file.
Action: Examine the UNIX errno returned for additional information.
Cause: An illegal value for the record size was specified.
Action: Specify a value for the recsize option that is greater than 0.
Cause: An illegal value for the maximum record size was specified.
Action: Specify a value for the maxrecsize option that is greater than 0.
Cause: An unrecognized processing option was specified.
Action: Examine the Oracle for nCUBE 2 User's Guide for valid options.
Cause: Memory for the load buffers failed to allocate.
Action: Reduce the maximum record size. Eliminate any unnecessary processes on the current node before running SQL*Loader again.
Cause: An error occurred trying to close a file.
Action: Examine the UNIX errno returned for additional information.
Cause: An error occurred trying to read from a file.
Action: Examine the UNIX errno returned for additional information.
Cause: The lseek system call returned an error.
Action: Examine the UNIX errno returned for additional information.
Cause: The lseek system call returned an error.
Action: Examine the UNIX errno returned for additional information.
Cause: An error occurred trying to read from a file.
Action: Examine the UNIX errno returned for additional information.
Cause: An error occurred trying to read from a file.
Action: Examine the UNIX errno returned for additional information.
Cause: This is an internal error.
Action: Contact Oracle Support.
Cause: This is an internal error.
Action: Contact Oracle Support.
Cause: A call to the lkmgr failed to open and convert the bias lock.
Action: Verify that the lkmgr is up.
Cause: A call to the lkmgr failed to close the bias lock.
Action: Verify that the lkmgr is up.
Cause: An attempt was made to automatically spool a file to the printer.
Action: None.
Cause: The oracle executable timed out waiting for an event.
Action: Contact Oracle Support.
Cause: (same as 1545)
Action: (same as 1545). Also, verify that enough rollback segments have been created for the number of instances you are trying to start.
Cause: An illegal command was executed for the nCUBE platform.
Action: There is no need to issue this command.
Cause: A command that can only be issued on instance 1 was issued elsewhere.
Action: Log on to instance 1 and repeat the command.
Cause: An error occurred trying to connect to the redo server.
Action: The OS specific error message should tell you what to do.
Cause: An error occurred trying to close the redo server connection.
Action: The OS specific error message should tell you what to do.
Cause: An error occurred trying to send redo to the redo server.
Action: The OS specific error message should tell you what to do.
Cause: The lock manager ran out of memory.
Action: Reduce the number of locks specified in the GC_FILES_TO_LOCKS and GC_ROLLBACK_LOCKS init.ora parameters, or increase the number of lock manager processes.
