Release 2 (9.2)
Part Number A96525-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
Cause: VMS system service $CANTIM returned an unexpected value.
Action: Check for system error message and refer to VMS documentation.
Cause: VMS system service $DEQ returned an unexpected value.
Action: Check for system error message and refer to VMS documentation.
Cause: VMS system service $ENQ returned an unexpected value.
Action: Check for system error message and refer to VMS documentation.
Cause: VMS system service $SETIMR returned an unexpected value.
Action: Check for system error message and refer to VMS documentation.
Cause: VMS system service $HIBER returned an unexpected value.
Action: Check for system error message and refer to VMS documentation.
Cause: VMS system service $ENQ returned an unexpected value.
Action: Check for system error message and refer to VMS documentation.
Cause: VMS system service $DEQ returned an unexpected value.
Action: Check for system error message and refer to VMS documentation.
Cause: A global locking system service returned an unexpected value.
Action: Check for system error message (if any) and refer to VMS documentation, or contact Oracle Support Services.
Cause: VMS system service $DEQ returned an unexpected value.
Action: Check for system error message and refer to VMS documentation.
Cause: VMS system service $DEQ returned an unexpected value.
Action: Check for system error message and refer to VMS documentation.
Cause: VMS system service $GETLKI returned an unexpected value.
Action: Check for system error message and refer to VMS documentation.
Cause: VMS system service $ENQ returned an unexpected value.
Action: Check for system error message and refer to VMS documentation.
Cause: VMS system service $ENQ returned an unexpected value.
Action: Check for system error message and refer to VMS documentation.
Cause: VMS system service $DEQ returned an unexpected value.
Action: Check for system error message and refer to VMS documentation.
Cause: VMS system service $DEQ returned an unexpected value.
Action: Check for system error message and refer to VMS documentation.
Cause: VMS system service $GETLKI returned an unexpected value.
Action: Check for system error message and refer to VMS documentation.
Cause: Too many test files open. This is an internal error.
Action: Contact Oracle Support Services.
Cause: VMS system service $OPEN failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $CONNECT failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $CLOSE failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $GET failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $IDTOASC failed.
Action: Examine system error message and refer to VMS documentation.
Cause: An extension was found but it is of improper length. This is an internal error.
Action: Contact Oracle Support Services.
Cause: VMS system service $PARSE failed.
Action: Examine system error message and refer to VMS documentation.
Cause: A wildcard was used in the file name.
Action: Re-enter the file name completely.
Cause: VMS system service $SEARCH failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $OPEN failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $CLOSE failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $IDTOASC failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $FIND_HELD failed.
Action: Examine system error message and refer to VMS documentation.
Cause: An OS role name was too long.
Action: Re-define the role name to be of correct length.
Cause: VMS system service LIB$SPAWN failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $GETUAI failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message and refer to VMS documentation.
Cause: An attempt was made to set an INTERNAL password (for either DBA or OPER privilege), but the corresponding VMS account (either ORA_sid_DBA or ORA_sid_OPER) has not been created yet.
Action: Add a VMS account for ORA_sid_DBA and/or ORA_sid_OPER before trying to set a password for them.
Cause: VMS system service $FIND_HELD failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $DCLEXH failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message and refer to VMS documentation.
Cause: A background process did not have name of correct form.
Action: If the job name was changed, restore it. Otherwise, this is an internal error; report it to Oracle Support Services.
Cause: The ORA_SID must exist and be less than 6 characters.
Action: Consult the VMS Installation guide for information on setting the SID.
Cause: A logical name used to set a detached process quota value has an invalid value (probably non-numeric).
Action: Examine the values of these logical names, correct the one in error, and retry.
Cause: VMS system service $PARSE failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $SEARCH failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $CREPRC failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message and refer to VMS documentation.
Cause: The logical name ORA_SID does not translate to a valid value.
Action: Check the value of ORA_SID in the process that gets the error, and correct the installation or command procedures that caused ORA_SID to be set incorrectly.
Cause: VMS system service $DELPRC failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message and refer to VMS documentation.
Cause: While obtaining needed privileges, an error was returned from SYS$SETPRV. This is an internal error.
Action: Contact Oracle Support Services.
Cause: While releasing privileges, an error was returned from SYS$SETPRV. This is an internal error.
Action: Contact Oracle Support Services.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $SETIMR failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $SCHDWK failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $GETSYIW failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $ASCTOID failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $CHKPRO failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $SNDOPR failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $GETUAI failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $HASH_PASSWORD failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $GETUAI failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $GETJPIW failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $CHANGE_CLASS failed.
Action: Examine system error message and refer to SEVMS documentation.
Cause: VMS system service $CHANGE_CLASSS failed.
Action: Examine system error message and refer to SEVMS documentation.
Cause: VMS system service $CHANGE_CLASS failed.
Action: Examine system error message and refer to SEVMS documentation.
Cause: VMS system service $FORMAT_CLASS failed because the given binary classification was not valid.
Action: Examine system error message and refer to SEVMS documentation.
Cause: VMS system service $IDTOASC failed while looking up the string representation in the rights database of a secrecy level.
Action: Define the entry in the rights database which the binary label you specified references.
Cause: VMS system service $IDTOASC failed while looking up the string representation in the rights database of an integrity level.
Action: Define the entry in the rights database which the binary label you specified references.
Cause: An illegal database block size was specified in the parameter file. It must be positive, a multiple of 512, and less than the maximum physical i/o data size.
Action: Change DB_BLOCK_SIZE in the parameter file to conform to these limits.
Cause: An illegal redo log buffer size was specified in the parameter file. It must be positive and a multiple of 512.
Action: Change LOG_BUFFER in the parameter file to conform to these limits.
Cause: While creating the system global area (SGA) backing file, VMS system service $CREATE failed.
Action: Examine the system error message and refer to VMS documentation.
Cause: While creating the system global area (SGA), VMS system service $CRMPSC failed.
Action: Examine the system error message and refer to VMS documentation.
Cause: While deleting the system global area (SGA), VMS system service $DGBLSC failed.
Action: Examine the system error message and refer to VMS documentation.
Cause: While mapping the system global area (SGA) during logon, VMS system service $MGBLSC failed. The usual reason is that Oracle has not been started up.
Action: Examine the system error message and refer to VMS documentation. Start Oracle if it is not already started.
Cause: An attempt to map the SGA during logon failed because it was already mapped. This is an internal error.
Action: Exit your program and try again, and report this to Oracle Support Services.
Cause: While unmapping the system global area (SGA) during logoff, VMS system service $CRETVA failed.
Action: Examine the system error message and refer to VMS documentation.
Cause: An attempt to unmap the SGA during logoff failed because it was not mapped. This is an internal error.
Action: Exit your program and try again, and report this to Oracle Support Services.
Cause: While extending the program global area (PGA), VMS system service $EXPREG failed. This often happens when the virtual memory page count quota is exceeded.
Action: Examine the system error message and refer to VMS documentation.
Cause: While deleting the program global area (PGA) during logoff, VMS system service $DELTVA failed.
Action: Examine the system error message and refer to VMS documentation.
Cause: While creating or extending a context area, VMS system service $EXPREG failed. This often happens when the virtual memory page count quota is exceeded.
Action: Examine the system error message and refer to VMS documentation.
Cause: While deleting a context area, VMS system service $DELTVA failed.
Action: Examine the system error message and refer to VMS documentation.
Cause: The buffer debug function was called with an illegal value. This is an internal error.
Action: Contact Oracle Support Services.
Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $CRETVA failed.
Action: Contact Oracle Support Services.
Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $SETPRT failed.
Action: Contact Oracle Support Services.
Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $MGBLSC failed.
Action: Contact Oracle Support Services.
Cause: An attempt was made to change the buffer protect mode when the SGA was not created with buffer protect debug option. This is an internal error.
Action: Contact Oracle Support Services.
Cause: An attempt was made to map an SGA with software in which the SGA pad area is not large enough.
Action: Create a smaller SGA, or relink the software with a larger pad.
Cause: An attempt was made to create an SGA with software in which the SGA pad area is not large enough.
Action: Create a smaller SGA, or relink the software with a larger pad.
Cause: An attempt was made to map to the SGA while it was being initialized.
Action: Wait until initialization is complete, and try again.
Cause: The system global area (SGA) backing file could not be allocated using the system pagefile because the system-wide limit on global pages has been exceeded.
Action: Either increase the VMS system parameter GBLPAGFIL or use a disk file as the SGA backing file.
Cause: While attempting to set the protection of a region of memory, an error was returned from the $CMKRNL system service.
Action: Examine the system error message and refer to VMS documentation.
Cause: This is an internal error.
Action: Report this error to Oracle Support Services; provide your initialization parameter file.
Cause: While attempting to set the label on a file, SEVMS service $CHANGE_CLASS failed.
Action: Examine the system message and refer to SEVMS system documentation.
Cause: While attempting to create a file, VMS system service $CREATE failed.
Action: Examine the system message and refer to VMS system documentation.
Cause: While attempting to reopen a file, VMS system service $OPEN failed.
Action: Examine the system message and refer to VMS system documentation.
Cause: While attempting to get the user's terminal device name, user name, user program name, or process name during logon, VMS system service $GETJPIW failed.
Action: Examine the system error message and refer to VMS documentation.
Cause: While attempting to translate SYS$INPUT during a prompt for a password, VMS system service $TRNLOG failed.
Action: Examine the system error message and refer to VMS documentation.
Cause: While attempting to get device characteristics during a prompt for a password, VMS system service $GETDVI failed.
Action: Examine the system error message and refer to VMS documentation.
Cause: While prompting for a password, VMS system service $ASSIGN failed.
Action: Examine the system error message and refer to VMS documentation.
Cause: While prompting for a password, VMS system service $QIOW failed.
Action: Examine the system error message and refer to VMS documentation.
Cause: A VMS exception occurred while executing in the Oracle exception handler. The message includes the signal number, first and second signal arguments, and exception PC, PSL and R0. This is an internal error.
Action: Contact Oracle Support Services.
Cause: VMS system service $IDTOASC failed while looking up the string representation in the rights database of a secrecy category.
Action: Define the entry in the rights database which the binary label you specified references.
Cause: VMS system service $IDTOASC failed while looking up the string representation in the rights database of an integrity category.
Action: Define the entry in the rights database which the binary label you specified references.
Cause: SEVMS system service $PARSE_CLASS failed because the given string did not represent a valid classification.
Action: Examine system error message and refer to SEVMS documentation.
Cause: A call to the Oracle shared image entry point occurred from within the shared image. This is an internal error.
Action: Contact Oracle Support Services.
Cause: While attempting to set up the dispatch vectors for the shared image, an error occurred. This is an internal error.
Action: Contact Oracle Support Services.
Cause: During Oracle shared image entry, a dispatch to kernel mode failed.
Action: Make sure that your shared image is installed with the CMKRNL privilege, then contact Oracle Support Services.
Cause: During an attempt to restore user privileges at Oracle shared image exit, VMS system service $SETPRV failed. This is an internal error.
Action: Contact Oracle Support Services.
Cause: During an attempt to restore the supervisor-mode stack at Oracle shared image exit, VMS system service $SETSTK failed. This is an internal error.
Action: Contact Oracle Support Services.
Cause: During an attempt to set the Oracle supervisor-mode stack at Oracle shared image entry, VMS system service $SETSTK failed. This is an internal error.
Action: Contact Oracle Support Services.
Cause: An interrupt was received while archiving the logs.
Action: Retry the operation.
Cause: Overflow of buffer for parsing archive control text string. This is an internal error.
Action: Contact Oracle Support Services.
Cause: Unrecognized device type in archive text. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The archive control text in the ARCHIVE command is invalid; the device type (to indicate a file or tape) must be followed by a '/'.
Action: Refer to the Oracle9i User-Managed Backup and Recovery Guide for the proper syntax of the text.
Cause: The archive control text in the ARCHIVE command is invalid; the device name must be followed by a ':'.
Action: Refer to the Oracle9i User-Managed Backup and Recovery Guide for the proper syntax of the text.
Cause: The buffer supplied for the device name is too small. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The archive control text in the ARCHIVE command is invalid; the disk file name is missing.
Action: Refer to the Oracle9i User-Managed Backup and Recovery Guide for the proper syntax of the text.
Cause: The archive control text in the ARCHIVE command is invalid; the tape label name is missing.
Action: Refer to the Oracle9i User-Managed Backup and Recovery Guide for the proper syntax of the text.
Cause: The buffer supplied for the tape label is too small. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The user specified a remote disk for archiving via DECnet.
Action: Archive to a disk on the local host.
Cause: The buffer supplied for the file name is too small. This is an internal error.
Action: Contact Oracle Support Services.
Cause: VMS system service SYS$MOUNT failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service SYS$DISMNT failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service SYS$GETDVI failed".
Action: Specify a valid device in ARCHIVE control string.
Cause: VMS system service LIB$GET_VM failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service LIB$FREE_VM failed.
Action: Examine system error message and refer to VMS documentation.
Cause: A call to SYS$ENQ returned an error indicating that the operating system lacked the resources necessary to create a lock. This is caused by the messages SS$_EXENQLM or SS$_INSFMEM.
Action: Free up some of the required resource to allow the creation of the required lock.
Cause: Structures used for reading error message files do not match. This is an internal error.
Action: Contact Oracle Support Services.
Cause: VMS system service $OPEN failed.
Action: Examine system error message and refer to VMS documentation.
Cause: VMS system service $CONNECT failed.
Action: Examine system error message and refer to VMS documentation.
Cause: An error message file is of incorrect format.
Action: Unless an error file has been changed, report this to Oracle.
Cause: Seal in passed in handle does not match correct value. This is an internal error.
Action: Contact Oracle Support Services.
Cause: VMS system service $CLOSE failed.
Action: Check system error and refer to VMS documentation.
Cause: seal in passed in handle does not match correct value. This is an internal error.
Action: Contact Oracle Support Services.
Cause: VMS system service $READ failed.
Action: Check system error and refer to VMS documentation.
Cause: An attempt to create a message file failed. This is an internal error.
Action: Contact Oracle Support Services.
Cause: An attempt to allocate a cache for a newly-created message file failed. This is an internal error.
Action: Contact Oracle Support Services.
Cause: An attempt to seek before writing a message file cache element failed. This is an internal error.
Action: Contact Oracle Support Services.
Cause: An attempt to write a message file cache element failed. This is an internal error.
Action: Contact Oracle Support Services.
Cause: An attempt to seek before reading a message file cache element failed. This is an internal error.
Action: Contact Oracle Support Services.
Cause: An attempt to read a message file cache element failed. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The seal in a passed-in handle does not match correct value. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The seal in a passed-in handle does not match correct value. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The destination string provided to the function is too short. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The $open service failed. This is an internal error.
Action: Contact Oracle Support Services.
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: An error was returned from the SYS$CRELNM function.
Action: Check system error and refer to VMS documentation.
Cause: An error was returned from the SYS$DELLNM function.
Action: Check system error and refer to VMS documentation.
Cause: An error was returned from the SYS$CREMBX function while trying to create the process dump mailbox.
Action: Check system error and refer to VMS documentation.
Cause: An error was returned from $QIO while trying to queue a read to the process dump mailbox.
Action: Check system error and refer to VMS documentation.
Cause: An error was returned from SYS$SETIMR while trying to queue a process spin-watch timer.
Action: Check system error and refer to VMS documentation.
Cause: An error was returned from SYS$QIO while trying to read the process dump mailbox.
Action: Check system error and refer to VMS documentation.
Cause: An error was returned from SYS$GETDVIW while trying to get information about the process dump mailbox.
Action: Check system error and refer to VMS documentation.
Cause: An error was returned from LIB$GET_VM while attempting to allocate memory for an I/O vector.
Action: Check system error and refer to VMS documentation.
Cause: An error was returned from SYS$OPEN while attempting to open the datafile for reading.
Action: Check system error and refer to VMS documentation.
Cause: An error was returned from SYS$CLOSE while attempting to close the input datafile.
Action: Check system error and refer to VMS documentation.
Cause: An error was returned from LIB$FREE_VM while attempting to free the memory for the I/O vector.
Action: Check system error and refer to VMS documentation.
Cause: An error was returned from LIB$GET_VM while attempting to allocate memory for data and index buffers.
Action: Check system error and refer to VMS documentation.
Cause: An error was returned from LIB$FREE_VM while attempting to free memory used by data and index buffers.
Action: Check system error and refer to VMS documentation.
Cause: The longest record in the file will not fit into the largest data buffer that can be allocated.
Action: Modify the RMS file to have smaller records.
Cause: An error was returned by SYS$CONNECT while attempting to open the datafile.
Action: Check system error and refer to VMS documentation.
Cause: An error was returned by SYS$GET while attempting to read the datafile.
Action: Check system error and refer to VMS documentation.
Cause: An error was returned by SYS$GET while attempting to skip records in the input file.
Action: Check system error and refer to VMS documentation.
Cause: You are using a bad option to loader Fixed= is one legal option. Check documentation for others.
Action: Check documentation.
Cause: An error occurred while setting up the control interrupt handler. This is an internal error.
Action: Contact Oracle Support Services.
Cause: A list of all files open by this process could not be obtained. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The sequence parent state objects for this session are all used. This is an internal error.
Action: Quit the session and begin a new one.
Cause: The limit on the number of sequences usable by session has been hit.
Action: Increase initialization parameter USER_SEQUENCES to get more.
Cause: Sequence CURRVAL has been selected before sequence NEXTVAL.
Action: Select NEXTVAL from the sequence before selecting CURRVAL.
Cause: The sequence was created with unsafe values for some of the parameters. The calculation of NEXTVAL cannot be made because it exceeds the legal representation size.
Action: Alter or re-create the sequence number with legal limits.
Cause: Instantiating NEXTVAL would violate one of MAX/MINVALUE.
Action: Alter the sequence so that a new value can be requested.
Cause: A row with the given ROWID does not exist in any of the tables given.
Action: Check the query for misspellings of table names and the ROWID.
Cause: The row has been deleted by another user since the operation began.
Action: Retry the operation.
Cause: The shared instance being started does not have the same value for USE_ROW_ENQUEUES as already running instances.
Action: Ensure that all instances' INIT.ORA files specify the same value for the parameter USE_ROW_ENQUEUES.
Cause: Validate Index detected an inconsistency in its argument index.
Action: Send trace file to Oracle Support Services.
Cause: This is an internal error; possible inconsistency in index.
Action: Send trace file to Oracle Support Services, along with information on reproducing the error.
Cause: This is an internal error; possible inconsistency in index.
Action: Send trace file to Oracle Support Services, along with information on reproducing the error.
Cause: The object has been deleted by another user since the operation began.
Action: Remove references to the object.
Cause: The index is being created or rebuild or waited for recovering from the online (re)build.
Action: Wait the online index build or recovery to complete.
Cause: Set this event only under the supervision of Oracle development.
Action: Debugging only.
Cause: Online index builder cannot create its journal table.
Action: Rename your table in conflict.
Cause: Only support normal index or IOT top-level index.
Action: Change your index type.
Cause: May not specify NOSORT for online index build.
Action: Get rid of NOSORT in the index creation command.
Cause: Oracle Kernel test only.
Action: Do not set this event (for test only).
Cause: User attempted to coalesce a partitioned index using ALTER INDEX COALESCE statement, which is illegal.
Action: Coalesce the index a (sub)partition at a time (using ALTER INDEX MODIFY (sub)PARTITION COALESCE).
Cause: User attempted to coalesce a composite partition.
Action: Coalesce the index a subpartition at a time (using ALTER INDEX MODIFY SUBPARTITION COALESCE).
Cause: User attempted to compress a composite partition index.
Action: Create uncompressed composite partition index.
Cause: An attempt was made to alter a fake index.
Action: Drop the fake index.
Cause: User attempted to create index type that online does not support.
Action: Use offline index create/rebuild command.
Cause: User attempted to create index online without allowing DML Share lock.
Action: Allow DML share lock on the base table.
Cause: Block maintenance forced the release of a block pin.
Action: Contact Oracle Support Services.
Cause: Deferred Foreign Key constraints cannot be enforced due to the index key being too big and built on a non-default DB_BLOCK_SIZE.
Action: First try to drop the Foreign Key and then the primary key.
Cause: The specified initrans needs additional space to hold the index key, which might make the index too big.
Action: Try specifying a smaller initrans value.
Cause: An attempt was made to perform an action that is not currently supported in a discrete transaction.
Action: Roll back the transaction, and retry it as a normal transaction.
Cause: Encountered data changed by an operation that does not generate rollback data: create index, direct load or discrete transaction.
Action: In read/write transactions, retry the intended operation. Read-only transactions must be restarted.
Cause: Encountered data changed by an operation that occurred after the start of this serializable transaction.
Action: In read/write transactions, retry the intended operation or transaction.
Cause: Serializable mode is not supported for user INTERNAL.
Action: Reconnect as another user and retry the SET TRANSACTION command.
Cause: Encountered data changed by an operation that occurred after a specific snapshot. This is usually used to indicate that a particular cached copy of a data block is stale. This is used for internal use for now.
Action: Refresh the cached copy of the data block and retry operation.
Cause: Could not match the time to an SCN from the mapping table.
Action: Try using a larger time.
Cause: The supplied scn was beyond the bounds of a valid scn.
Action: Use a valid scn.
Cause: User tried to do DML or DDL while in Flashback mode.
Action: Disable Flashback and re-attempt the operation.
Cause: User tried to do Flashback in the middle of a transaction.
Action: Issue a COMMIT statement.
Cause: An attempt was made to re-enable Flashback while in Flashback mode.
Action: Disable Flashback before re-enabling Flashback mode.
Cause: User logged in as SYS.
Action: Log in as a different user.
Cause: An invalid timestamp was specified.
Action: Enter a valid timestamp.
Cause: A snapshot expression using AS OF was specified when not allowed.
Action: Do not use the AS OF clause.
Cause: The environment variable ORACLE_SID is not set.
Action: Set the ORACLE_SID environment variable.
Cause: Cannot translate $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf.
Action: Ensure that ORACLE_HOME and ORACLE_SID are properly set.
Cause: The address file could not be opened.
Action: Check that Oracle is up. Check that the file $(ORACLE_HOME)/dbs/sgadef$(ORACLE_SID).dbf exists and has correct permissions.
Cause: The address file could not be read.
Action: Check that the file $(ORACLE_HOME)/dbs/sgadef$(ORACLE_SID).dbf exists and contains a single line of text.
Cause: The System Commit Number has not yet been initialized.
Action: Contact Oracle Support Services.
Cause: Oracle requested that an I/O error be returned for this operation.
Action: This should not occur in normal Oracle operation. Contact support.
Cause: The N_CORE system call failed, maybe due to insufficient memory.
Action: Specify a smaller number of buffers. Check INIT.ORA parameters.
Cause: The process cannot attach to the SGA. This can happen if either the listener cannot attach, or the process cannot communicate with the listener.
Action: Verify that the instance is up and running. Contact Oracle Support Services.
Cause: Probably the listener process has died.
Action: Contact Oracle Support Services.
Cause: The N_CORE system call failed while detaching from the SGA.
Action: Note NCX error returned; contact Oracle Support Services.
Cause: The instance listener address cannot be read from the SGADEF file.
Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are set correctly. Additional information gives error return from ORA_ADDR.
Cause: A process wishing to attach to the SGA is on a different node from its instance's listener.
Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are set correctly. Contact Oracle Support Services.
Cause: The N_SHARE call failed, probably because the listener has died.
Action: Check if the listener is running, and contact Oracle Support Services.
Cause: An attempt was made to attach to an SGA which has not yet been created.
Action: Verify that the instance is running. Contact Oracle Support Services.
Cause: The N_CORE system call failed while detaching from the SGA.
Action: Check NCX error, and contact Oracle Support Services.
Cause: A process could not connect to the name server.
Action: Make sure the name server is up and running. Additional information gives name server's returned status.
Cause: The listener name server entry for an instance could not be found.
Action: Make sure the name server is up and running. Additional information gives name server's returned status.
Cause: The listener name server entry could not be freed.
Action: Additional information gives name server's returned status. Contact Oracle Support Services.
Cause: The connection to the name server could not be closed.
Action: Additional information gives name server's returned status. Contact Oracle Support Services.
Cause: A process could not connect to the name server.
Action: Make sure the name server is up and running. Additional information gives name server's returned status.
Cause: The listener's addressing information could not be registered.
Action: Make sure the name server is up and running. Additional information gives name server's returned status.
Cause: The connection to the name server could not be closed.
Action: Additional information gives name server's returned status. Contact Oracle Support Services.
Cause: The connection to the name server could not be closed.
Action: Additional information gives name server's returned status. Contact Oracle Support Services.
Cause: The listener's addressing information could not be removed.
Action: Additional information gives name server's returned status. Contact Oracle Support Services.
Cause: Archive files cannot be created with the given archival control string.
Action: Check 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: Could not retrieve CPU times because N_STAT failed.
Action: Contact Oracle Support Services.
Cause: Oracle could not open a file.
Action: Check the UNIX errno returned as additional information.
Cause: Oracle could not obtain information about an open file.
Action: Check the UNIX errno returned as 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: Check the Oracle for nCUBE 2 Installation and User's Guide for valid options.
Cause: Memory for the load buffers could not be allocated.
Action: Reduce the maximum record size. Eliminate any unnecessary processes on your current node before running SQL*Loader again.
Cause: An error occurred trying to close a file.
Action: Check the UNIX errno returned as additional information.
Cause: An error occurred trying to read from a file.
Action: Check the UNIX errno returned as additional information.
Cause: The LSEEK system call returned an error.
Action: Check the UNIX errno returned as additional information.
Cause: The LSEEK system call returned an error.
Action: Check the UNIX errno returned as additional information.
Cause: An error occurred trying to read from a file.
Action: Check the UNIX errno returned as additional information.
Cause: An error occurred trying to read from a file.
Action: Check the UNIX errno returned as additional information.
Cause: This is an internal error
Action: Contact Oracle Support Services.
Cause: This is an internal error
Action: Contact Oracle Support Services.
Cause: A call to the LKMGR failed to open and convert the bias lock.
Action: Check to make sure the LKMGR is up.
Cause: A call to the LKMGR failed to close the bias lock.
Action: Check to make sure the LKMGR is up.
Cause: An attempt was made to automatically spool a file to the printer.
Action: No action required.
Cause: Oracle timed out waiting for an event.
Action: Contact Oracle Support Services.
Cause: See ORA-01545.
Action: See ORA-1545. Also, make sure you have created enough rollback segments 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 operating system-specific error message should tell you what to do.
Cause: An error occurred trying to close the redo server connection.
Action: The operating system-specific error message should tell you what to do.
Cause: An error occurred trying to send redo to the redo server.
Action: The operating system-specific error message should tell you what to do.
Cause: An invalid compiler name comp_name was passed to a UTL_PG conversion routine.
Action: Correct the compiler name parameter in the PL/SQL code that called the conversion routine.
Cause: The WMSGBSIZ is the maximum size for warning message block, it is recommended to be 1024 bytes to 8 kilobytes.
Action: Defined WMSGBLK of size between 1k to 8k bytes and update the WMSGBSIZ to the sizeof(WMSGBLK).
Cause: An invalid compiler type is defined in format control block. The format control block is invalid.
Action: Check to be sure that the format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT, and that it was not accidentally overwritten or modified by the PL/SQL procedure.
Cause: The function routine returned an error. Where routine may be:
Action: This message will be preceded by messages providing details about the error. Check those messages to determine what action to take.
Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contained invalid data. The picture mask parameter specified a digit, but the corresponding input from the raw data did not contain a valid digit.
Action: Either the input data is incorrect, or the picture mask is incorrect. Correct the appropriate item.
Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine had no leading sign, but the mask options parameter specified a leading sign.
Action: Correct the input raw data or the mask options so that they match.
Cause: The picture mask parameter passed to a UTL_PG RAW_TO_NUMBER conversion routine contained a zero, but the corresponding input from the raw data was not a zero.
Action: Either the input data is incorrect, or the picture mask is incorrect. Correct the appropriate item.
Cause: The input raw data passed to a UTL_PG RAW_TO_NUMBER conversion routine contained invalid floating point data.
Action: Correct the input raw data.
Cause: The picture mask parameter passed to a UTL_PG RAW_TO_NUMBER conversion routine contained non-numeric characters, but the conversion was to a numeric data type.
Action: Correct the picture mask parameter.
Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine had no trailing sign, but the mask options parameter specified a trailing sign.
Action: Correct the input raw data or the mask options so that they match.
Cause: The input MASK passed to a UTL_PG RAW_TO_NUMBER conversion routine had no leading sign, but the mask options parameter specified a leading sign.
Action: Correct the input raw data or the mask options so that they match.
Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine had an invalid sign digit in the position where the picture mask specified a sign.
Action: Correct the input raw data or the picture mask so that they match.
Cause: The picture mask parameter passed to a UTL_PG NUMBER_TO_RAW conversion routine contained non-numeric characters, but the conversion was to a numeric data type.
Action: Correct the picture mask parameter.
Cause: The output raw buffer passed to a UTL_PG NUMBER_TO_RAW conversion routine was not large enough to contain the results of the conversion based on the picture mask.
Action: Increase the raw buffer size to the size necessary to hold the entire result of the conversion.
Cause: A closed parenthesis was missing from the picture mask passed to a UTL_PG conversion routine.
Action: Correct the picture mask.
Cause: A syntax error was found in the BLANK WHEN ZERO clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are:
Action: Correct the mask options parameter.
Cause: A syntax error was found in the JUSTIFIED clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are:
Action: Correct the mask options parameter.
Cause: A syntax error was found in the SIGN clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are:
Action: Correct the mask options parameter.
Cause: A syntax error was found in the SYNCHRONIZED clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are:
Action: Correct the mask options parameter.
Cause: A syntax error was found in the USAGE clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are:
Action: Correct the mask options parameter.
Cause: A syntax error was found in the DECIMAL-POINT environment clause parameter passed to a UTL_PG conversion routine. Valid specifications are: DECIMAL-POINT IS COMMA.
Action: Correct the environment clause parameter.
Cause: An invalid numeric symbol was found in the picture mask parameter passed to a UTL_PG conversion routine.
Action: Correct the picture mask parameter.
Cause: The CR suffix was incorrectly specified in the picture mask parameter passed to a UTL_PG conversion routine. The CR suffix can only appear at the end of a picture mask.
Action: Correct the picture mask parameter.
Cause: The DB suffix was incorrectly specified in the picture mask parameter passed to a UTL_PG conversion routine. The DB suffix can only appear at the end of a picture mask.
Action: Correct the picture mask parameter.
Cause: The floating point exponent symbol 'E' was specified in the picture mask parameter passed to a UTL_PG conversion routine. The floating point data type is currently not supported by the UTL_PG conversion routines.
Action: Correct the picture mask parameter, and the data, if necessary.
Cause: The picture mask passed to a UTL_PG conversion routine contained more than one decimal point indicator ('V'). Only one decimal point indicator is allowed in the picture mask.
Action: Correct the picture mask parameter.
Cause: The picture mask passed to a UTL_PG conversion routine contained more than one operational sign indicator ('S'). Only one operational sign indicator is allowed in the picture mask.
Action: Correct the picture mask parameter.
Cause: A syntax error was found in the CURRENCY SIGN environment clause parameter passed to a UTL_PG conversion routine. Valid specifications are: CURRENCY SIGN IS x where x is a valid currency sign.
Action: Correct the environment clause parameter.
Cause: The picture mask parameter passed to a UTL_PG conversion routine contained no sign symbol ('S', '+', or '-'), but the mask options parameter contained a SIGN clause. A sign symbol is required in the picture mask parameter when the mask options parameter contains a SIGN clause.
Action: Correct the picture mask parameter or the mask options parameter.
Cause: A syntax error was found in the SEPARATE CHARACTER option of the SIGN clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: SEPARATE, SEPARATE CHARACTER.
Action: Correct the mask options parameter.
Cause: The format parameter passed to a UTL_PG conversion routine was invalid. The format parameter should have been built by a prior call to either MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT.
Action: Check to be sure that the format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT, and that it was not accidentally overwritten or modified by the PL/SQL procedure.
Cause: The format parameter passed to a UTL_PG conversion routine was not the correct length. Format parameters must be 2048 bytes in length.
Action: Check to be sure that the format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT, and that it was not accidentally overwritten or modified by the PL/SQL procedure.
Cause: The environment parameter passed to a UTL_PG conversion routine contained an unsupported or invalid environment clause. Only the CURRENCY SIGN and the DECIMAL-POINT IS COMMA environment clauses are supported.
Action: Correct the environment parameter.
Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contains invalid decimal data.
Action: Correct the input data.
Cause: The output variable passed to a UTL_PG RAW_TO_NUMBER was not large enough to hold the Oracle number resulting from the input decimal number.
Action: Be sure that the input decimal number is valid, and be sure that the output variable is large enough to hold the Oracle number value.
Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contained more than 42 digits. This exceeds the maximum size of an Oracle number.
Action: Correct the raw input buffer.
Cause: The input mask passed to UTL_PG numeric conversion routine contained more the 32 characters.
Action: Correct the mask input buffer.
Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine was less than string bytes long, but the picture mask parameter specified that string bytes of input data were to be converted.
Action: Either the input data is incorrect, or the picture mask is incorrect. Correct the appropriate item.
Cause: An error occurred when converting an Oracle number to a COBOL type of: DISPLAY COMP-3 or character variable. The Oracle number was not in the correct format.
Action: Correct the call to the conversion routine. The input must be a valid Oracle number variable.
Cause: The mask option clause was passed to a UTL_PG conversion routine, but is not supported by UTL_PG. The clause can be:
Action: Remove the clause from the mask options parameter in the PL/SQL call to UTL_PG.
Cause: Picture mask USAGE option was overridden by the picture mask.
Action: This is an informational message only. The message may be eliminated by changing the USAGE option to match the picture mask.
Cause: Picture mask options such as OCCUR, SYNC and others are not processed by the UTL_PG numeric conversion routines.
Action: This is an informational message only. The message may be eliminated by removing the unnecessary picture mask options from the parameter list passed to the UTL_PG routine.
Cause: Could be out of disk space.
Action: See OSD error accompanying this message.
Cause: Block sizes may not match.
Action: See OSD error accompanying this message.
Cause: DB_BLOCK_SIZE specified in the INIT.ORA file could be incorrect.
Action: See OSD error accompanying this message.
Cause: File attributes may have changed.
Action: See OSD error accompanying this message.
Cause: Incorrect path may have been specified for the file.
Action: See OSD error accompanying this message.
Cause: File may have been truncated or corrupted.
Action: See OSD error accompanying this message.
Cause: File may have been truncated or corrupted.
Action: See OSD error accompanying this message.
Cause: File may have been truncated or corrupted.
Action: See OSD error accompanying this message.
Cause: File may have been corrupted.
Action: See OSD error accompanying this message.
Cause: File may have been truncated or corrupted.
Action: See OSD error accompanying this message.
Cause: Incorrect path may have been specified for the file.
Action: See OSD error accompanying this message.
Cause: File may have been truncated or corrupted.
Action: See OSD error accompanying this message.
Cause: File may have been truncated or corrupted.
Action: See OSD error accompanying this message.
Cause: File name may be too long.
Action: See OSD error accompanying this message.
Cause: File may have been truncated or corrupted.
Action: See OSD error accompanying this message.
Cause: File may have been truncated or corrupted.
Action: See OSD error accompanying this message.
Cause: The directory specified as the value for the stated parameter could not be used.
Action: Make sure the directory you have specified is a valid directory/file specification.
Cause: Could be out of disk space.
Action: See OSD error accompanying this message.
Cause: File may be corrupted or truncated.
Action: See OSD error accompanying this message.
Cause: Could be out of memory.
Action: See OSD error accompanying this message.
Cause: Could be out of memory.
Action: See OSD error accompanying this message.
Cause: An error occurred while creating SGA.
Action: See OSD error accompanying this message.
Cause: SGA may not have been created (database not started).
Action: See OSD error accompanying this message.
Cause: An error occurred while setting memory protections.
Action: See OSD error accompanying this message.
Cause: An error occurred while switching stacks.
Action: See OSD error accompanying this message.
Cause: Unable to map SGA.
Action: See OSD error accompanying this message.
Cause: An error occurred while destroying the SGA.
Action: See OSD error accompanying this message.
Cause: May be out of resources.
Action: See OSD error accompanying this message.
Cause: Could be out of resources.
Action: See OSD error accompanying this message.
Cause: Could be out of resources.
Action: See OSD error accompanying this message.
Cause: Could be out of memory.
Action: See OSD error accompanying this message.
Cause: Could be out of resources.
Action: See OSD error accompanying this message.
Cause: Could be out of resources.
Action: See OSD error accompanying this message.
Cause: Could be out memory.
Action: See OSD error accompanying this message.
Cause: Could be out of memory.
Action: See OSD error accompanying this message.
Cause: Username may be too long.
Action: See OSD error accompanying this message.
Cause: Remote operating system login attempted when not allowed.
Action: See OSD error accompanying this message.
Cause: An operating system error was returned when verifying the role name.
Action: See OSD error accompanying this message.
Cause: An OS role name was too long.
Action: See OSD error accompanying this message.
Cause: CONNECT INTERNAL is no longer supported for DBA connections.
Action: Please try to connect AS SYSDBA or AS SYSOPER.
Cause: File may be corrupted.
Action: See OSD error accompanying this message.
Cause: Possibly incorrect path specified to the file.
Action: See OSD error accompanying this message.
Cause: File could be corrupted.
Action: See OSD error accompanying this message.
Cause: File could be corrupted.
Action: See OSD error accompanying this message.
Cause: MALLOC() system call returned an error. The system might have run out of heap space.
Action: Check additional information for the operating system error.
Cause: Processing option passed is of incorrect format.
Action: Consult your IUG for permissible formats.
Cause: Could be out of memory.
Action: See OSD error accompanying this message.
Cause: Unable to access directory.
Action: Specify a valid device in ARCHIVE control string.
Cause: Bad directory or format specified.
Action: Specify a valid directory in LOG_ARCHIVE_FORMAT and a valid format string in LOG_ARCHIVE_FORMAT in the INIT.ORA file.
Cause: An error was returned while attempting to send a message to the console operator.
Action: See OSD error accompanying this message.
Cause: Unable to detect the presence of DPMI.
Action: Restart Windows and retry.
Cause: An attempt was made to connect to S: while in enhanced mode.
Action: Restart Windows in standard mode.
Cause: This is an internal error.
Action: See OSD error accompanying this message.
Cause: May be out of resources.
Action: See OSD error accompanying this message.
Cause: Could be out of resources.
Action: See OSD error accompanying this message.
Cause: May be out of resources.
Action: See OSD error accompanying this message.
Cause: Internal buffer may have overflowed.
Action: See OSD error accompanying this message.
Cause: This is an internal error.
Action: See OSD error accompanying this message.
Cause: OS roles may not be supported for this platform.
Action: See OSD error accompanying this message.
Cause: The password specified is invalid.
Action: See OSD error accompanying this message.
Cause: There might not be enough memory for the command or hosting out may not be supported on this platform.
Action: See OSD error accompanying this message.
Cause: The system time might be set incorrectly.
Action: See OSD error accompanying this message.
Cause: OS roles may not be supported on this platform.
Action: See OSD error accompanying this message.
Cause: This is an internal error.
Action: See OSD error accompanying this message.
Cause: This is an internal error.
Action: See OSD error accompanying this message.
Cause: A client workstation that is abnormally disconnected would cause Oracle to terminate that session after about a minute. This message also appears in the trace file if a SHUTDOWN ABORT is performed.
Action: No action required.
Cause: ORACLE_SID must be at the most 4 alphanumeric characters.
Action: Specify an ORACLE_SID with the correct format.
Cause: Another instance is currently mounting the database.
Action: Try again later.
Cause: The user performed a SHUTDOWN ABORT.
Action: No action required.
Cause: This function may not be implemented.
Action: No action required.
Cause: See OSD error accompanying this message.
Action: See OSD error accompanying this message.
Cause: See OSD error accompanying this message.
Action: See OSD error accompanying this message.
Cause: See OSD error accompanying this message.
Action: See OSD error accompanying this message.
Cause: See OSD error accompanying this message.
Action: See OSD error accompanying this message.
Cause: See OSD error accompanying this message.
Action: See OSD error accompanying this message.
Cause: See OSD error accompanying this message.
Action: See OSD error accompanying this message.
Cause: See OSD error accompanying this message.
Action: See OSD error accompanying this message.
Cause: See OSD error accompanying this message.
Action: See OSD error accompanying this message.
Cause: See OSD error accompanying this message.
Action: See OSD error accompanying this message.
Cause: See OSD error accompanying this message.
Action: See OSD error accompanying this message.
Cause: See OSD error accompanying this message.
Action: See OSD error accompanying this message.
Cause: See OSD error accompanying this message.
Action: See OSD error accompanying this message.
Cause: See OSD error accompanying this message.
Action: See OSD error accompanying this message.
Cause: See OSD error accompanying this message.
Action: See OSD error accompanying this message.
Cause: See OSD error accompanying this message.
Action: See OSD error accompanying this message.
Cause: See OSD error accompanying this message.
Action: See OSD error accompanying this message.
Cause: Oracle wants to use more latches then available.
Action: Increase the value of the initialization parameter LATCH_PAGES or decrease the amount of shared memory you are using.
Cause: The value of the PROCESSES initialization parameter was exceeded.
Action: Decrease the PROCESSES parameter and restart.
Cause: The semaphore used for accessing latches could not be seized.
Action: Send trace file to Oracle Support Services, along with information on reproducing the error.
Cause: The semaphore used for accessing latches could not be released.
Action: Send trace file to Oracle Support Services, along with information on reproducing the error.
Cause: the FTOK() library call failed in SSTASTCRE().
Action: Verify that TASDEF@.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 could not be initialized.
Action: Send trace file to Oracle Support Services, along with information on reproducing the error.
Cause: GET_PROCESS_STATS system call returned an error. Possible operating system error.
Action: Check additional information returned. Look for information in operating system reference. Contact Oracle Support Services.
Cause: The bind system call failed on the socket.
Action: Check additional information for operating system error. Try connecting again.
Cause: The accept system call failed on the socket.
Action: Check additional information for operating system 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 Services.
Cause: An existing connection has already been made from ARCHMON to ORASRV.
Action: Stop trying to connect.
Cause: An existing connection has already been made from log archiver to ORASRV.
Action: Stop trying to connect.
Cause: The global hardware clock used to generate the System Change Number for Oracle has failed.
Action: Check the global hardware clock.
Cause: The TXIPC driver cannot obtain the name of the PU. (Possible operating system error.)
Action: Check if the PUs are named (consistent).
Cause: ORASRV cannot obtain the name of the PU (possible operating system error).
Action: Check if 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: Possible 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: Check return code in SERCERRNO. Possible operating system failure.
Cause: MSG_RECEIVE system call returned an error. This is an internal error.
Action: Check 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: Check 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 Services.
Cause: The MMAP system call returned an error. This is an internal error.
Action: Contact Oracle Support Services.
Cause: Error in system call VM_ALLOCATE. Failed to create SGA as a single shared memory segment.
Action: Check result code returned in SERCERRNO. Verify that the SGA attach address is valid.
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: Make sure the server is still active. Check the error code returned in SERCERRNO, and look for error messages in the server log file.
Cause: The PWS_LOOK_UP call could not fork the (Oracle helper) process.
Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient.
Cause: The PWS_LOOK_UP could not find a port to (Oracle helper).
Action: Make sure the (Oracle helper) server has been started correctly by PWS_LOOK_UP, and that the network name server is still running.
Cause: The PORT_RENAME system call failed; possible internal error.
Action: Check return code in SERCERRNO, report to Oracle Support Services.
Cause: The call PWS_ATTACH to (Oracle helper) failed.
Action: Make sure the server is still active. Check the error code returned in SERCERRNO, and look for error messages in the server log file.
Cause: The PORT_ALLOCATE system call failed; possible resource exhaustion.
Action: Check return code in SERCERRNO, report to Oracle Support Services.
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 Services.
Cause: The PORT_ALLOCATE system call failed.
Action: Possible system resource shortage; check the error code in SERCERRNO.
Cause: OSNPNS could not find the given named port in the name server.
Action: Check the error code in SERCERRNO. Make sure the shadow process and network name server are still running.
Cause: The PORT_ALLOCATE system call failed.
Action: Possible system resource shortage; check the error code in SERCERRNO.
Cause: The NETNAME_CHECK_IN call failed.
Action: Check the error code in SERCERRNO. Make sure 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 could not send a break message to the Oracle shadow process break thread.
Action: Contact Oracle Support Services.
Cause: The call PWS_STOP_INSTANCE to (Oracle helper) failed.
Action: Make sure the server is still active. Check the error code returned in SERCERRNO, and look for error messages in the server log file.
Cause: A failure was detected while translating the value of ORACLE_SID.
Action: Make sure ORACLE_SID is defined, and that it is of legal length.
Cause: The Mach driver failed to exchange port information with the other side of the connection. Either MSG_SEND (sercose[0] == 1) or MSG_RECEIVE (sercose[0] == 2) failed.
Action: Check return code in SERCERRNO. Make sure both sides of the connection are still running.
Cause: The Mach driver could not access the Oracle executable.
Action: Check the permissions on the Oracle executable and each component of the ORACLE_HOME/bin path.
Cause: The Mach driver could not fork the Oracle shadow process.
Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient.
Cause: The Mach driver failed to allocate enough virtual memory space for its I/O buffers.
Action: Decrease the value of BUFFER_SIZE parameter in the Two-Task driver host string.
Cause: The MSG_SEND system call failed while flushing the Mach driver's send buffer. This is an internal error.
Action: Contact Oracle Support Services.
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 Services.
Cause: The Mach driver could not send a break message to the Oracle shadow process break thread. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The PWS_LOOK_UP routine failed to translate the name of the (Oracle helper) executable.
Action: Make sure ORACLE_SID and ORACLE_HOME are set and correct. Additional information gives the translation error code.
Cause: The MSG_SEND system call failed while sending a Mach driver break. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The Mach driver received a message having an unrecognizable message type. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The Mach driver received a message having an unrecognizable message type. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The Mach driver could not send a break message to the Oracle shadow process break thread. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The Mach two-task driver could not reset the connection. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The PWS_LOOK_UP call could not access the (Oracle helper) executable.
Action: Check the permissions on the (Oracle helper) executable and each component of the ORACLE_HOME/bin path.
Cause: The pipe driver could not send a break message to the Oracle shadow process break thread. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The routine failed to allocate or set the task's notify port.
Action: Possible operating system error. Contact Oracle Support Services.
Cause: The PORT_ALLOCATE system call failed; system resources might be exhausted.
Action: Possible operating system error. Contact Oracle Support Services.
Cause: Open system call returned an error.
Action: Check errno.
Cause: Processing option passed is of incorrect format.
Action: Consult your IUG for permissible formats.
Cause: Read system call returned an error.
Action: Check errno. Verify file exists.
Cause: Read system call returned an error.
Action: Check errno. Verify file exists.
Cause: Close system call returned an error.
Action: Check errno.
Cause: Additional information indicates error returned from SLTLN.
Action: Check additional information.
Cause: MALLOC system call returned an error. The system might have run out of heap space.
Action: Check additional information for the operating system 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 Services.
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 Services.
Cause: The allocation of memory for an internal structure used to hold a role descriptor failed.
Action: Check the UNIX error number for a possible operating system failure.
Cause: The allocation of memory for an internal buffer used to hold the name of a role failed.
Action: Check the UNIX error number for a possible operating system failure.
Cause: The operating system would not allow the retrieval of this process' privileges.
Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.
Cause: The comparison of two binary labels failed.
Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.
Cause: Oracle was unable to get a label attached to a file.
Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.
Cause: Oracle was unable to get the sensitivity label for a process.
Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.
Cause: Oracle was unable to retrieve the user's ID number from the SQL*Net connection.
Action: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Support Services.
Cause: Oracle was unable to convert a binary label to a string.
Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.
Cause: a buffer used to hold the name of the file for which a label was to be obtained could not be allocated.
Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. The number of bytes that Oracle attempted to allocate is in the "Additional Information" field.
Cause: Oracle was unable to convert a class component from binary format to Oracle format.
Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.
Cause: Oracle was unable to translate a category number to its corresponding string representation failed.
Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. The category number is contained in the "Additional information" field.
Cause: A temporary buffer used to hold a label could not be allocated.
Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. The number of bytes that Oracle attempted to allocate is in the "Additional Information" field.
Cause: Oracle was unable to convert the string representation of a label to binary format.
Action: Re-enter a valid label.
Cause: Oracle was unable to get a user's clearance level.
Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.
Cause: Oracle was unable to retrieve the user's group ID number from the SQL*Net connection.
Action: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Support Services.
Cause: Oracle was unable to retrieve the user's process ID number from the SQL*Net connection.
Action: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Support Services.
Cause: Oracle was unable to initialize the library used to obtain security information. This is an internal error.
Action: Contact Oracle Support Services.
Cause: Oracle was unable to retrieve the user's operating system session clearance from the SQL*Net connection.
Action: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Support Services.
Cause: Oracle was unable to determine if a directory is multilevel.
Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services.
Cause: Oracle was unable to expand the name of a file that resides in multilevel directory.
Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services.
Cause: The buffer that Oracle uses to hold the expanded name of a too small. This is an internal error.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
Cause: Oracle was unable to write an entry to the file used as the audit trail.
Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services.
Cause: Oracle was unable to convert a component string to a number because the number is larger than the largest possible value for an integer. The additional information field specifies the maximum.
Action: Correct the string and repeat the conversion.
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: Oracle was unable to convert a class string to a number because all of the characters in the string were not numeric.
Action: Change the string to be either all numbers or all non-numeric characters and repeat the conversion.
Cause: A label specified in Oracle numeric format was found not to be valid.
Action: Re-enter a valid label. Consult your system's encodings for valid numeric component values.
Cause: Oracle was unable to translate the value of the AUDIT_TRAIL_DEST initialization parameter.
Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services.
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 Services.
Cause: Oracle was not able to turn on ALLOWMACACCESS privilege so that it could do a label comparison.
Action: Check the UNIX error number. If it indicates that Oracle does not have the ALLOWMACACCESS privilege, add the ALLOWMACACCESS privilege to the potential privilege set of $ORACLE_HOME/bin/oracle using CHPRIV (1M). If the executable already has the ALLOWMACACCESS privilege, contact Oracle Support Services.
Cause: Oracle was not able to turn off the ALLOWMACACCESS privilege after doing a label comparison. This is an internal error.
Action: Contact Oracle Support Services.
Cause: System call ATOMIC_OP() return error.
Action: Check additional information in the trace file.
Cause: System call ATOMIC_OP() return unexpected error.
Action: Check additional information in the trace file.
Cause: System call ATOMIC_OP() return unexpected error.
Action: Check additional information in the trace file.
Cause: The call PWS_START_INSTANCE to (Oracle helper) failed; system resources might be exhausted.
Action: Make sure the server is still active. Check the error code returned in SERCERRNO, and look for error messages in the server log file.
Cause: The MSG_RPC system call returned an error. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The routine failed to build a port set on which to listen for requests. Possible operating system failure.
Action: Contact Oracle Support Services.
Cause: The routine received an incorrectly formatted request. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The routine received an incorrectly formatted request. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The PORT_STATUS system called failed. Possible operating system error.
Action: Contact Oracle Support Services.
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 Services.
Cause: The PORT_SET_ADD system called failed. Possible operating system error.
Action: Contact Oracle Support Services.
Cause: The MALLOC library call failed to allocate space for a callback link. Possible operating system error.
Action: Contact Oracle Support Services.
Cause: The port PORT_SET_REMOVE system call failed. Possible operating system error.
Action: Contact Oracle Support Services.
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 Services.
Cause: SLTLN() could not translate the named pipe ?/dbs/mon2arch_@.
Action: Make sure that the ORACLE_HOME specified for this ORACLE_SID in oratab is correct.
Cause: SLTLN() could not translate the named pipe ?/dbs/arch2mon_@.
Action: Make sure that the ORACLE_HOME specified for this ORACLE_SID in ORATAB is correct.
Cause: MKNOD() failed to create named pipe ?/dbs/mon2arch_@.
Action: Your current operating system login may lack write permission for the ORACLE_HOME/dbs directory. Only USERIDs in the DBA group of a given instance can run ARCHMON for that ORACLE_SID. Make sure that the ORACLE_HOME directory is correct in ORATAB.
Cause: MKNOD() failed to create named pipe ?/dbs/arch2mon_@.
Action: Your current operating system login may lack write permission for the ORACLE_HOME/dbs directory. Only USERIDs in the dba group of a given instance can run ARCHMON for that ORACLE_SID. Make sure that the ORACLE_HOME directory is correct in ORATAB.
Cause: OPEN() failed to open named pipe ?/dbs/mon2arch_@.
Action: Only the Oracle DBA can run ARCHMON. Make sure that your current operating system login has owner or group search permission for the ORACLE_HOME/dbs directory. The maximum number of open files may have been exceeded.
Cause: OPEN() failed to open named pipe ?/dbs/arch2mon_@.
Action: Only the Oracle DBA can run ARCHMON. Make sure that your current operating system login has owner or group search permission for the ORACLE_HOME/dbs directory. The maximum number of open files may have been exceeded.
Cause: OPEN() failed to open named pipe ?/dbs/mon2arch_@.
Action: Make sure that the operating system USERID of the currently running database has search permission for the ORACLE_HOME/dbs directory. The maximum number of open files may have been exceeded.
Cause: OPEN() failed to open named pipe ?/dbs/arch2mon_@.
Action: Make sure that the operating system USERID of the currently running database has search permission for the ORACLE_HOME/dbs directory. The maximum number of open files may have been exceeded.
Cause: FCNTL() failed to set write lock on named pipe ?/dbs/arch2mon_@.
Action: Make sure that ARCHMON is not already active on another terminal for this ORACLE_SID. Only one ARCHMON session is allowed at a time for a given instance.
Cause: FCNTL() failed to set read lock on named pipe ?/dbs/mon2arch_@.
Action: Make sure that ARCHMON is not already active on another terminal for this ORACLE_SID. Only one ARCHMON session is allowed at a time for a given instance.
Cause: The request to remove a port from the callback set returned a failure code. Possible operating system error.
Action: Contact Oracle Support Services.
Cause: The request to collect information on a port in the callback set returned a failure code. Possible operating system error.
Action: Contact Oracle Support Services.
Cause: The routine received an incorrectly formatted request. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The VM_ALLOCATE system call returned an error.
Action: Check returned error. Possibly out of system resources.
Cause: The VM_PROTECT system call returned an error. This is an internal error.
Action: Contact Oracle Support Services.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
