Oracle8 Error Messages Release 8.0.4 A58312-01 |
Library | Product | Contents | Index

## 08200-08399: nCUBE Messages

##### ORA-08200: scggc: failed to open lock

Cause: The lock manager failed to open a lock.

Action: Verify that enough memory is available, and retry the operation.

##### ORA-08201: scggc: failed to convert lock

Cause: The lock manager failed to convert a lock.

Action: Retry the operation.

##### ORA-08202: scgcc: failed to close lock

Cause: The lock manager encountered an error closing a lock.

Action: Examine the lock manager status returned for additional information.

##### ORA-08203: scgcan: failed to cancel a pending convert request

Cause: The lock manager encountered an error cancelling a convert request.

Action: Examine the lock manager status returned for additional information.

##### ORA-08204: scgcm: unexpected lock manager return code

Cause: The lock manager returned an unexpected value.

Action: Examine the lock manager status returned for additional information.

##### ORA-08205: ora_addr: ORACLE_SID not set in environment

Cause: The environment variable ORACLE_SID is not set.

Action: Set the ORACLE_SID environment variable.

##### ORA-08206: ora_addr: cannot translate address file name

Cause: Failure to translate $ORACLE_HOME/dbs/sgadefsid.dbf.

Action: Ensure that $ORACLE_HOME and ORACLE_SID are properly set.

##### ORA-08207: ora_addr: cannot open address file

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.

##### ORA-08208: ora_addr: cannot read from address file

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.

##### ORA-08209: scngrs: SCN not yet initialized

Cause: The System Commit Number has not yet been initialized.

Action: Contact Oracle Support

##### ORA-08210: requested I/O error

Cause: The oracle executable requested that an I/O error be returned for this operation.

Action: Contact Oracle Support.

##### ORA-08230: smscre: failed to allocate SGA

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.

##### ORA-08231: smscre: unable to attach to SGA

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.

##### ORA-08232: smsdes: cannot detach from SGA

Cause: Probably, the listener process has died.

Action: Contact Oracle Support.

##### ORA-08233: smsdes: cannot unmap SGA

Cause: The n_core system call failed while detaching from the SGA.

Action: Note nCX error. Contact Oracle Support.

##### ORA-08234: smsget: cannot get instance listener address

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.

##### ORA-08235: smsget: listener not on this node

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.

##### ORA-08236: smsget: cannot share subcube with listener

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.

##### ORA-08237: smsget: SGA region not yet created

Cause: Attempting to attach to an SGA which has not yet been created.

Action: Verify that the instance is running. Contact Oracle Support.

##### ORA-08238: smsfre: cannot detach from SGA

Cause: The n_core system call failed while detaching from the SGA.

Action: Examine nCX error, and contact Oracle Support.

##### ORA-08240: snlmatt: parallel server name too long

Cause: The file name of the lock manager address file is too long.

Action: Use a shorter parallel server name.

##### ORA-08241: snlmatt: cannot attach to lock manager

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.

##### ORA-08242: snlmdet: cannot detach from lock manager

Cause: An error was encountered detaching from the lock manager.

Action: Additional information is lock manager return code. Contact Oracle Support.

##### ORA-08260: ora_addr: cannot open nameserver

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.

##### ORA-08261: ora_addr: cannot find name in nameserver

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.

##### ORA-08262: ora_addr: ORACLE_PSRV undefined

Cause: The parallel server name ORACLE_PSRV was undefined.

Action: Set the environment variable ORACLE_PSRV, and try again.

##### ORA-08263: ora_addr: cannot free listener address

Cause: The listener nameserver entry failed to free.

Action: Additional information gives nameserver's returned status. Contact Oracle Support.

##### ORA-08264: ora_addr: cannot close nameserver

Cause: The connection to the nameserver failed to close.

Action: Additional information gives nameserver's returned status. Contact Oracle Support.

##### ORA-08265: create_ora_addr: cannot open nameserver

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.

##### ORA-08266: create_ora_addr: cannot register name in nameserver

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.

##### ORA-08267: destroy_ora_addr: cannot close nameserver

Cause: The connection to the nameserver failed to close.

Action: Additional information gives nameserver's returned status. Contact Oracle Support.

##### ORA-08268: create_ora_addr: cannot close nameserver

Cause: The connection to the nameserver failed to close.

Action: Additional information gives nameserver's returned status. Contact Oracle Support.

##### ORA-08269: destroy_ora_addr: cannot destroy name

Cause: The listener's addressing information failed to be removed.

Action: Additional information gives nameserver's returned status. Contact Oracle Support.

##### ORA-08270: sksachk: Illegal archival control string

Cause: Archive files failed to be created with the given archival control string.

Action: Verify that the volume exists.

##### ORA-08271: sksabln: buffer size not large enough for archive control string

Cause: The given archival control string expands into too many characters.

Action: Reduce archive control string length.

##### ORA-08274: out of memory for environment variable

Cause: There is insufficient memory to return the requested value.

Action: Reduce memory usage and retry.

##### ORA-08275: environment variable unset

Cause: The requested environment variable is not set.

Action: Ensure that the variable name requested is correct.

##### ORA-08276: no room in nameserver for pid

Cause: There is no room to record the pid for a background process.

Action: Shutdown abort, and restart the database.

##### ORA-08277: cannot set environment variable

Cause: There is insufficient memory to expand the environment.

Action: Reduce memory usage and retry.

##### ORA-08278: cannot get CPU statistics

Cause: Failure to retrieve CPU times, because n_stat failed.

Action: Contact Oracle Support.

##### ORA-08308: sllfop: cannot open file

Cause: Oracle failed to open a file.

Action: Examine the UNIX errno returned for additional information.

##### ORA-08309: sllfop: cannot fstat file

Cause: Oracle failed to obtain information about an open file.

Action: Examine the UNIX errno returned for additional information.

##### ORA-08310: sllfop: bad value for recsize

Cause: An illegal value for the record size was specified.

Action: Specify a value for the recsize option that is greater than 0.

##### ORA-08311: sllfop: bad value for maxrecsize

Cause: An illegal value for the maximum record size was specified.

Action: Specify a value for the maxrecsize option that is greater than 0.

##### ORA-08312: sllfop: unrecognized processing option

Cause: An unrecognized processing option was specified.

Action: Examine the Oracle for nCUBE 2 User's Guide for valid options.

##### ORA-08313: sllfop: could not allocate buffers

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.

##### ORA-08314: sllfcf: error closing file

Cause: An error occurred trying to close a file.

Action: Examine the UNIX errno returned for additional information.

##### ORA-08315: sllfrb: error reading file

Cause: An error occurred trying to read from a file.

Action: Examine the UNIX errno returned for additional information.

##### ORA-08316: sllfsk: error seeking in file

Cause: The lseek system call returned an error.

Action: Examine the UNIX errno returned for additional information.

##### ORA-08317: sllfsk: error seeking in file

Cause: The lseek system call returned an error.

Action: Examine the UNIX errno returned for additional information.

##### ORA-08318: sllfsk: error reading file

Cause: An error occurred trying to read from a file.

Action: Examine the UNIX errno returned for additional information.

##### ORA-08319: sllfsk: error reading file

Cause: An error occurred trying to read from a file.

Action: Examine the UNIX errno returned for additional information.

##### ORA-08320: scnget: call to scnget before scnset or scnfnd

Cause: This is an internal error.

Action: Contact Oracle Support.

##### ORA-08321: scnmin: NOT IMPLEMENTED YET

Cause: This is an internal error.

Action: Contact Oracle Support.

##### ORA-08322: scnmin: open/convert of bias lock failed

Cause: A call to the lkmgr failed to open and convert the bias lock.

Action: Verify that the lkmgr is up.

##### ORA-08323: scnmin: close of bias lock failed

Cause: A call to the lkmgr failed to close the bias lock.

Action: Verify that the lkmgr is up.

##### ORA-08330: printing not supported

Cause: An attempt was made to automatically spool a file to the printer.

Action: None.

##### ORA-08331: wait operation timed out

Cause: The oracle executable timed out waiting for an event.

Action: Contact Oracle Support.

##### ORA-08332: rollback segment number specified not available

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.

##### ORA-08340: this command not allowed on nCUBE, only one thread is ever used

Cause: An illegal command was executed for the nCUBE platform.

Action: There is no need to issue this command.

##### ORA-08341: on nCUBE, this command can only be executed from instance 1

Cause: A command that can only be issued on instance 1 was issued elsewhere.

Action: Log on to instance 1 and repeat the command.

##### ORA-08342: sropen: failed to open a redo server connection

Cause: An error occurred trying to connect to the redo server.

Action: The OS specific error message should tell you what to do.

##### ORA-08343: srclose: failed to close a redo server connection

Cause: An error occurred trying to close the redo server connection.

Action: The OS specific error message should tell you what to do.

##### ORA-08344: srapp: failed to send redo data to the redo server

Cause: An error occurred trying to send redo to the redo server.

Action: The OS specific error message should tell you what to do.

##### ORA-08362: scgcm: out of memory in lock manager

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.

Prev | Top | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index