Cause: VMS system service $DEQ returned an unexpected value
Action: Check for system error message and refer to VMS documentation
ORA-07510: scgbrm: $getlki unexpected return on lockid string
Cause: VMS system service $GETLKI returned an unexpected value
Action: Check for system error message and refer to VMS documentation
ORA-07511: sscggtl: $enq unexpected return for master termination lock
Cause: VMS system service $ENQ returned an unexpected value
Action: Check for system error message and refer to VMS documentation
ORA-07512: sscggtl: $enq unexpected return for client termination lock
Cause: VMS system service $ENQ returned an unexpected value
Action: Check for system error message and refer to VMS documentation
ORA-07513: sscgctl: $deq unexpected return on cancel of term. lock
Cause: VMS system service $DEQ returned an unexpected value
Action: Check for system error message and refer to VMS documentation
ORA-07514: scgcan: $deq unexpected return while canceling lock
Cause: VMS system service $DEQ returned an unexpected value
Action: Check for system error message and refer to VMS documentation
ORA-07534: scginq: $getlki unexpected return on lockid string
Cause: VMS system service $GETLKI returned an unexpected value
Action: Check for system error message and refer to VMS documentation
ORA-07548: sftopn: Maximum number of files already open
Cause: Too many test files open
Action: This is an internal error, please report to Oracle
ORA-07549: sftopn: $OPEN failure
Cause: VMS system service $OPEN failed
Action: Examine system error message and refer to VMS documentation
ORA-07550: sftopn: $CONNECT failure
Cause: VMS system service $OPEN failed
Action: Examine system error message and refer to VMS documentation
ORA-07551: sftcls: $CLOSE failure
Cause: VMS system service $CLOSE failed
Action: Examine system error message and refer to VMS documentation
ORA-07552: sftget: $GET failure
Cause: VMS system service $GET failed
Action: Examine system error message and refer to VMS documentation
ORA-07561: szprv: $IDTOASC failure
Cause: VMS system service $IDTOASC failed
Action: Examine system error message and refer to VMS documentation
ORA-07562: sldext: extension must be 3 characters
Cause: An extension was found but it is of improper length
Action: This is an internal error, please report to Oracle
ORA-07563: sldext: $PARSE failure
Cause: VMS system service $PARSE failed
Action: Examine system error message and refer to VMS documentation
ORA-07564: sldext: wildcard in filename or extension
Cause: A wildcard was used in the file name
Action: Reenter the file name completely
ORA-07565: sldext: $SEARCH failure
Cause: VMS system service $SEARCH failed
Action: Examine system error message and refer to VMS documentation
ORA-07568: slspool: $OPEN failure
Cause: VMS system service $OPEN failed
Action: Examine system error message and refer to VMS documentation
ORA-07569: slspool: $CLOSE failure
Cause: VMS system service $CLOSE failed
Action: Examine system error message and refer to VMS documentation
ORA-07570: szrfc: $IDTOASC failure
Cause: VMS system service $IDTOASC failed
Action: Examine system error message and refer to VMS documentation
ORA-07571: szrfc: $FIND_HELD failure
Cause: VMS system service $FIND_HELD failed
Action: Examine system error message and refer to VMS documentation
ORA-07572: szrfc: insufficient rolename buffer space
Cause: An OS role name was too long.
Action: Re-define the role name to be of correct length.
ORA-07573: slkhst: could not perform host operation
Cause: VMS system service LIB$SPAWN failed
Action: Examine system error message and refer to VMS documentation
ORA-07574: szrfc: $GETUAI failure
Cause: VMS system service $GETUAI failed
Action: Examine system error message and refer to VMS documentation
ORA-07576: sspexst: $GETJPIW failure on process ID string
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
ORA-07577: no such user in authorization file
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) hasn"t 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.
ORA-07578: szprv: $FIND_HELD failure
Cause: VMS system service $FIND_HELD failed
Action: Examine system error message and refer to VMS documentation
ORA-07579: spini: $DCLEXH failure
Cause: VMS system service $PARSE failed
Action: Examine system error message and refer to VMS documentation
ORA-07580: spstp: $GETJPIW failure
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
ORA-07581: spstp: cannot derive SID from unexpected process name
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, please report to Oracle.
ORA-07582: spstp: ORA_SID has illegal value
Cause: The ORA_SID must exist and be less than 6 characters
Action: Consult the VMS Installation guide for information on setting the SID.
ORA-07584: spdcr: invalid value for ORA_sid_(proc_)PQL$_item
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.
ORA-07585: spdcr: $PARSE failure
Cause: VMS system service $PARSE failed
Action: Examine system error message and refer to VMS documentation
ORA-07586: spdcr: $SEARCH failure
Cause: VMS system service $SEARCH failed
Action: Examine system error message and refer to VMS documentation
ORA-07587: spdcr: $CREPRC failure
Cause: VMS system service $CREPRC failed
Action: Examine system error message and refer to VMS documentation
ORA-07588: spdcr: $GETJPIW get image name failure
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
ORA-07589: spdde: system ID not set
Cause: The logical name ORA_SID doesn"t 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.
ORA-07590: spdde: $DELPRC failure
Cause: VMS system service $DELPRC failed
Action: Examine system error message and refer to VMS documentation
ORA-07591: spdde: $GETJPIW failure
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.
Action: This is an internal error. Please report to Oracle
ORA-07593: ssprprv: Error release privileges
Cause: While releasing privileges, an error was returned from SYS$SETPRV.
Action: This is an internal error. Please report to Oracle
ORA-07594: spiip: $GETJPIW failure
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
ORA-07595: sppid: $GETJPIW failure
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
ORA-07596: sptpa: $GETJPIW failure
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
ORA-07597: spguns: $GETJPIW failure
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
ORA-07598: spwat: $SETIMR failure
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
ORA-07599: spwat: $SCHDWK failure
Cause: VMS system service $SCHDWK failed
Action: Examine system error message and refer to VMS documentation
ORA-07600: slkmnm: $GETSYIW failure
Cause: VMS system service $GETSYIW failed
Action: Examine system error message and refer to VMS documentation
ORA-07601: spguno: $GETJPIW failure
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
ORA-07602: spgto: $GETJPIW failure
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
ORA-07605: szprv: $ASCTOID failure
Cause: VMS system service $ASCTOID failed
Action: Examine system error message and refer to VMS documentation
ORA-07606: szprv: $CHKPRO failure
Cause: VMS system service $CHKPRO failed
Action: Examine system error message and refer to VMS documentation
ORA-07607: szaud: $SNDOPR failure
Cause: VMS system service $SNDOPR failed
Action: Examine system error message and refer to VMS documentation
ORA-07608: szprv: $GETUAI failure
Cause: VMS system service $GETUAI failed
Action: Examine system error message and refer to VMS documentation
ORA-07609: szprv: $HASH_PASSWORD failure
Cause: VMS system service $HASH_PASSWORD failed
Action: Examine system error message and refer to VMS documentation
ORA-07610: $GETJPIW failed in retrieving the user"s MAC priviledges
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
ORA-07612: $GETUAI failed in retrieving the user"s clearance level
Cause: VMS system service $GETUAI failed
Action: Examine system error message and refer to VMS documentation
ORA-07613: $GETJPIW failed in retrieving the user"s process label
Cause: VMS system service $GETJPIW failed
Action: Examine system error message and refer to VMS documentation
ORA-07614: $CHANGE_CLASS failed in retrieving the user"s process label
Cause: VMS system service $CHANGE_CLASS failed
Action: Examine system error message and refer to SEVMS documentation
ORA-07615: $CHANGE_CLASS failed in retrieving the specified file label
Cause: VMS system service $CHANGE_CLASSS failed
Action: Examine system error message and refer to SEVMS documentation
ORA-07616: $CHANGE_CLASS failed in retrieving the specified device label
Cause: VMS system service $CHANGE_CLASS failed
Action: Examine system error message and refer to SEVMS documentation
ORA-07617: $FORMAT_CLASS failed translating the binary label to a string
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
ORA-07618: $IDTOASC failed translating a secrecy level
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.
ORA-07619: $IDTOASC failed translating an integrity level
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.
ORA-07620: smscre: illegal database block size
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.
ORA-07621: smscre: illegal redo block size
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.
ORA-07622: smscre: $CREATE failure
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.
ORA-07623: smscre: $CRMPSC failure
Cause: While creating the system global area (SGA), VMS system service $CRMPSC failed.
Action: Examine the system error message and refer to VMS documentation.
ORA-07624: smsdes: $DGBLSC failure
Cause: While deleting the system global area (SGA), VMS system service $DGBLSC failed.
Action: Examine the system error message and refer to VMS documentation.
ORA-07625: smsget: $MGBLSC failure
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 up Oracle if it is not already started.
ORA-07626: smsget: sga already mapped
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 your customer support representative.
ORA-07627: smsfre: $CRETVA failure
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.
ORA-07628: smsfre: sga not mapped
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 your customer support representative.
ORA-07629: smpall: $EXPREG failure
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.
ORA-07630: smpdal: $DELTVA failure
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.
ORA-07631: smcacx: $EXPREG failure
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.
ORA-07632: smsrcx: $DELTVA failure
Cause: While deleting a context area, VMS system service $DELTVA failed.
Action: Examine the system error message and refer to VMS documentation.
ORA-07633: smsdbp: illegal protection value
Cause: The buffer debug function was called with an illegal value. This is an internal error.
Action: Contact your customer support representative.
ORA-07634: smsdbp: $CRETVA failure
Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $CRETVA failed.
Action: Contact your customer support representative.
ORA-07635: smsdbp: $SETPRT failure
Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $SETPRT failed.
Action: Contact your customer support representative.
ORA-07636: smsdbp: $MGBLSC failure
Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $MGBLSC failed.
Action: Contact your customer support representative.
ORA-07637: smsdbp: buffer protect option not specified when sga created
Cause: Trying to change the buffer protect mode when the SGA was not created with buffer protect debug option. This is an internal error.
Action: Contact your customer support representative.
ORA-07638: smsget: SGA pad area not large enough for created SGA
Cause: An attempt was made to map an SGA with software in which the SGA pad area isn"t large enough.
Action: Create a smaller SGA, or relink the software with a larger pad.
ORA-07639: smscre: SGA pad area not large enough (string bytes required)
Cause: An attempt was made to create an SGA with software in which the SGA pad area isn"t large enough.
Action: Create a smaller SGA, or relink the software with a larger pad.
ORA-07640: smsget: SGA not yet valid. Initialization in progress
Cause: An attempt was made to map to the SGA while it was being initialized.
Action: Wait until initialization is complete, and try again.
ORA-07641: smscre: Unable to use the system pagefile for the SGA
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.
ORA-07642: smprtset: $CMKRNL failure
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.
ORA-07643: smsalo: SMSVAR is invalid
Cause: an internal error
Action: Report this error to Oracle Support Services, provide your INIT.ORA file.
ORA-07645: sszfsl: $CHANGE_CLASS failure
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.
ORA-07646: sszfck: $CREATE failure
Cause: While attempting to create a file, VMS system service $CREATE failed.
Action: Examine the system message and refer to VMS system documentation.
ORA-07647: sszfck: $OPEN failure
Cause: While attempting to reopen a file, VMS system service $OPEN failed.
Action: Examine the system message and refer to VMS system documentation.
ORA-07650: sigunc: $GETJPIW failure
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.
ORA-07655: slsprom:$TRNLOG failure
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.
ORA-07656: slsprom:$GETDVI failure
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.
ORA-07657: slsprom:$ASSIGN failure
Cause: While prompting for a password, VMS system service $ASSIGN failed.
Action: Examine the system error message and refer to VMS documentation.
ORA-07658: slsprom:$QIOW read failure
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 your customer support representative.
ORA-07670: $IDTOASC failed translating a secrecy category
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.
ORA-07671: $IDTOASC failed translating an integrity category
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.
ORA-07672: $PARSE_CLASS failed translating the string into a binary label
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.
ORA-07680: sou2os: another call to Oracle currently executing
Cause: A call to the Oracle shared image entry point occurred from within the shared image. This is an internal error.
Action: Contact your customer support representative.
ORA-07681: sou2os: An error occurred while initializing Oracle
Cause: While attempting to set up the dispatch vectors for the shared image, an error occurred. This is an internal error.
Action: Contact your customer support representative.
ORA-07682: sou2os: set kernel dispatch fail err
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 your customer support representative.
ORA-07683: sou2os: $SETPRV reset error
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 your customer support representative.
ORA-07684: sou2os: supervisor stack reset error
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 your customer support representative.
ORA-07685: sou2os: supervisor stack set error
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 your customer support representative.
ORA-07700: sksarch: interrupt received
Cause: An interrupt was received while archiving the logs
Action: Retry operation
ORA-07701: sksatln: internal exception: output buffer too small
Cause: Overflow of buffer for parsing archive control text string
Action: This is an internal error, please report to Oracle
ORA-07702: unrecognized device type in archive text
Cause: Unrecognized device type in archive text
Action: This is an internal error, please report to Oracle
ORA-07703: error in archive text: need "/" after device type
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 SQLDBA Guide for the proper syntax of the text.
ORA-07704: error in archive text: need ":" after device name
Cause: The archive control text in the ARCHIVE command is invalid; the device name must be followed by a ":".
Action: Refer to the SQLDBA Guide for the proper syntax of the text.
ORA-07705: sksaprs: device name buffer too small
Cause: The buffer supplied for the device name is too small. This is an internal error.
Action: Contact your customer support representative.
ORA-07706: error in archive text: need disk file name
Cause: The archive control text in the ARCHIVE command is invalid; the disk file name is missing.
Action: Refer to the SQLDBA Guide for the proper syntax of the text.
ORA-07707: error in archive text: need tape label name
Cause: The archive control text in the ARCHIVE command is invalid; the tape label name is missing.
Action: Refer to the SQLDBA Guide for the proper syntax of the text.
ORA-07708: sksaprs: tape label name buffer too small
Cause: The buffer supplied for the tape label is too small. This is an internal error.
Action: Contact your customer support representative.
ORA-07709: sksaprs: archiving to a remote host is not allowed
Cause: The user specified a remote disk for archiving via DECnet.
Action: Archive to a disk on the local host.
ORA-07710: sksaprs: file name buffer too small
Cause: The buffer supplied for the file name is too small. This is an internal error.
Action: Contact your customer support representative.
ORA-07713: sksamtd: could not mount archival device (SYS$MOUNT failure)
Cause: VMS system service SYS$MOUNT failed
Action: Examine system error message and refer to VMS documentation
ORA-07715: sksadtd: could not dismount archival device (SYS$DISMNT failure)
Cause: VMS system service SYS$DISMNT failed
Action: Examine system error message and refer to VMS documentation
ORA-07716: sksachk: invalid device specification for ARCHIVE
Cause: VMS system service SYS$GETDVI failed"
Action: Specify a valid device in ARCHIVE control string
ORA-07717: sksaalo: error allocating memory
Cause: VMS system service LIB$GET_VM failed"
Action: Examine system error message and refer to VMS documentation
ORA-07718: sksafre: error freeing memory
Cause: VMS system service LIB$FREE_VM failed
Action: Examine system error message and refer to VMS documentation
ORA-07721: scgcm: not enough OS resource to obtain system enqueue
Cause: d 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: The sequence was created with unsafe values for some of the parameters. The calculation of NEXTVAL cannot be made because it exceeds the legal represention size.
Action: Alter or recreate the sequence number with legal limits.
ORA-08004: sequence string.NEXTVAL stringstringVALUE and cannot be instantiated
Cause: instantiating NEXTVAL would violate one of MAX/MINVALUE
Action: alter the sequence so that a new value can be requested
ORA-08005: specified row does not exist
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
ORA-08006: specified row no longer exists
Cause: the row has been deleted by another user since the operation began
Action: re-try the operation
ORA-08007: Further changes to this block by this transaction not allowed
Cause: Max locks have been reached for this transaction in this block
Action: Commit changes
ORA-08008: another instance is mounted with USE_ROW_ENQUEUES = string
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"
ORA-08100: index is not valid - see trace file for diagnostics
Cause: Validate Index detected an inconsistency in its argument index
Action: Send trace file to your customer support representative
ORA-08101: index key does not exist file string: (root string, node string) blocks (string)
Cause: Internal error: possible inconsistency in index
Action: Send trace file to your customer support representative, along with information on reproducing the error
ORA-08102: index key not found, obj# string, file string, block string (string)
Cause: Internal error: possible inconsistency in index
Action: Send trace file to your customer support representative, along with information on reproducing the error
ORA-08103: object no longer exists
Cause: The object has been deleted by another user since the operation began, or a prior incomplete recovery restored the database to a point in time during the deletion of the object.
Action: Delete the object if this is the result of an incomplete recovery.
ORA-08104: this index object string is being online built or rebuilt
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
ORA-08105: Oracle event to turn off smon cleanup for online index build
Cause: set this event only under the supervision of Oracle development
Cause: An attempt was made to perform an action that is not currently supported in a discrete transaction.
Action: Rollback the transaction, and retry it as a normal transaction.
ORA-08176: consistent read failure; rollback data not available
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.
ORA-08177: can"t serialize access for this transaction
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.
ORA-08178: illegal SERIALIZABLE clause specified for user INTERNAL
Cause: Serializable mode is not supported for user INTERNAL.
Action: Reconnect as another user and retry the SET TRANSACTION command.
ORA-08179: concurrency check failed
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 datablock is stale. This is used for internal use for now.
Action: refresh the cached copy of the datablock and retry operation.
ORA-08180: no snapshot found based on specified time
Cause: Could not match the time to an SCN from the mapping table.
Action: try using a larger time.
ORA-08181: specified number is not a valid system change number
Cause: supplied scn was beyond the bounds of a valid scn.
Action: use a valid scn.
ORA-08182: operation not supported while in Flashback mode
Cause: user tried to do dml or ddl while in Flashback mode
Action: disable Flashback and re-attempt the operation
ORA-08183: Flashback cannot be enabled in the middle of a transaction
Cause: user tried to do Flashback in the middle of a transaction
Action: do a commit
ORA-08184: attempting to re-enable Flashback while in Flashback mode
Cause: as stated above
Action: disable first before re-enabling
ORA-08185: Flashback not supported for user SYS
Cause: user logged on as SYS
Action: logon as a different (non SYS) user.
ORA-08186: invalid timestamp specified
Cause: as stated above
Action: enter a valid timestamp
ORA-08187: snapshot expression not allowed here
Cause: A snapshot expression using AS OF was specified when not allowed.
Action: Do not use the AS OF clause
ORA-08189: cannot flashback the table because row movement is not enabled
Cause: An attempt was made to perform Flashback Table operation on a table for which row movement has not been enabled. Because the Flashback Table does not preserve the rowids, it is necessary that row movement be enabled on the table.
Action: Enable row movement on the table
ORA-08190: restore point string is from a different incarnation of the database
Cause: An attempt was made to perform Flashback Table operation using a restore point from a different incarnation of the database
Action: Provide a restore point from the current database incarnation
ORA-08191: Flashback Table operation is not supported on remote tables
Cause: An attempt was made to perform Flashback Table operation on a remote table. This is not permitted.
Action: Do not perform a Flashback Table operation on remote tables.
ORA-08192: Flashback Table operation is not allowed on fixed tables
Cause: An attempt was made to perform Flashback Table operation on a fixed table. This is not permitted.
Action: Do not perform a Flashback Table operation on fixed tables.
ORA-08193: Flashback Table operation is not allowed on temporary tables
Cause: An attempt was made to perform Flashback Table operation on a temporary table. This is not permitted.
Action: Do not perform a Flashback Table operation on temporary tables.
ORA-08194: Flashback Table operation is not allowed on materialized views
Cause: An attempt was made to perform Flashback Table operation on a materialized view. This is not permitted.
Action: Do not perform a Flashback Table operation on materialized views or snapshot logs.
ORA-08195: Flashback Table operation is not supported on partitions
Cause: An attempt was made to perform Flashback Table operation on a partition. This is not permitted.
Action: Do not perform a Flashback Table operation on partitions.
ORA-08196: Flashback Table operation is not allowed on AQ tables
Cause: An attempt was made to perform Flashback Table operation on AQ tables. This is not permitted.
Action: Do not perform a Flashback Table operation on AQ tables.
ORA-08197: Flashback Table operation is not supported on clustered tables
Cause: An attempt was made to perform Flashback Table operation on a clustered table. This is not permitted.
Action: Do not perform a Flashback Table operation on clustered tables.
ORA-08198: Flashback Table is not supported on object tables, nested tables
Cause: An attempt was made to perform Flashback Table operation on a object table or a nested table or a table with nested table column. This is not permitted.
Action: Do not perform a Flashback Table operation on such tables.
ORA-08199: Flashback Table operation is not supported on this object
Cause: An attempt was made to perform Flashback Table operation on an object on which the operation is not supported.
Action: Do not perform a Flashback Table operation on such objects.
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
Action: Ensure that ORACLE_HOME and ORACLE_SID are properly set.
ORA-08207: ora_addr: cannot open address file
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.
ORA-08208: ora_addr: cannot read from address file
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.
ORA-08209: scngrs: SCN not yet initialized
Cause: The System Commit Number has not yet been initialized.
Action: Contact your customer support representative.
ORA-08210: Requested I/O error
Cause: Oracle requested that an I/O error be returned for this operation.
Action: This should not occur in normal Oracle operation. Contact support.
ORA-08230: smscre: failed to allocate SGA
Cause: The n_core system call failed, maybe due to insufficient memory.
Action: Specify a smaller number of buffers. Check INIT.ORA parameters.
ORA-08231: smscre: unable to attach to SGA
Cause: The process cannot attach to the SGA. This can happen if either the listener can"t attach, or the process cannot communicate with the listener.
Action: Verify that the instance is up and running. Contact your customer support representative.
ORA-08232: smsdes: cannot detach from SGA
Cause: Probably, the listener process has died.
Action: Contact your customer support representative.
ORA-08233: smsdes: cannot unmap SGA
Cause: The n_core system call failed while detaching from the SGA.
Action: Note nCX error returned; contact your customer support representative.
ORA-08234: smsget: cannot get instance listener address
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.
ORA-08235: smsget: listener not on this node
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 your customer support representative.
ORA-08236: smsget: cannot share subcube with listener
Cause: The n_share call failed, probably because the listener has died.
Action: Check if the listener is running, and contact your customer support representative.
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 your customer support representative.
ORA-08238: smsfre: cannot detach from SGA
Cause: The n_core system call failed while detaching from the SGA.
Action: Check nCX error, and contact your customer support representative.
ORA-08260: ora_addr: cannot open nameserver
Cause: A process could not connect to the nameserver.
Action: Make sure 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 could not be found.
Action: Make sure the nameserver is up and running. Additional information gives nameserver"s returned status.
ORA-08263: ora_addr: cannot free listener address
Cause: The listener nameserver entry could not be freed
Action: Additional information gives nameserver"s returned status. Contact your customer support representative.
ORA-08264: ora_addr: cannot close nameserver
Cause: The connection to the nameserver could not be closed.
Action: Additional information gives nameserver"s returned status. Contact your customer support representative.
ORA-08265: create_ora_addr: cannot open nameserver
Cause: A process could not connect to the nameserver.
Action: Make sure 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 could not be registered.
Action: Make sure 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 could not be closed.
Action: Additional information gives nameserver"s returned status. Contact your customer support representative.
ORA-08268: create_ora_addr: cannot close nameserver
Cause: The connection to the nameserver could not be closed.
Action: Additional information gives nameserver"s returned status. Contact your customer support representative.
ORA-08269: destroy_ora_addr: cannot destroy name
Cause: The listener"s addressing information could not be removed.
Action: Additional information gives nameserver"s returned status. Contact your customer support representative.
ORA-08270: sksachk: Illegal archival control string
Cause: Archive files cannot be created with the given archival control string.
Action: Check 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: Could not retrieve CPU times because n_stat failed.
Action: Contact customer support.
ORA-08308: sllfop: Cannot open file
Cause: Oracle could not open a file.
Action: Check the Unix errno returned as additional information.
ORA-08309: sllfop: Cannot fstat file
Cause: Oracle could not obtain information about an open file.
Action: Check the Unix errno returned as 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: Check the Oracle for nCUBE 2 User"s Guide for valid options.
ORA-08313: sllfop: could not allocate buffers
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.
ORA-08314: sllfcf: Error closing file
Cause: An error occurred trying to close a file.
Action: Check the Unix errno returned as additional information.
ORA-08315: sllfrb: Error reading file
Cause: An error occurred trying to read from a file.
Action: Check the Unix errno returned as additional information.
ORA-08316: sllfsk: Error seeking in file.
Cause: The lseek system call returned an error.
Action: Check the Unix errno returned as additional information.
ORA-08317: sllfsk: Error seeking in file.
Cause: The lseek system call returned an error.
Action: Check the Unix errno returned as additional information.
ORA-08318: sllfsk: Error reading file
Cause: An error occurred trying to read from a file.
Action: Check the Unix errno returned as additional information.
ORA-08319: sllfsk: Error reading file
Cause: An error occurred trying to read from a file.
Action: Check the Unix errno returned as additional information.
ORA-08320: scnget: Call to scnget before scnset or scnfnd.
Cause: An internal error
Action: Contact your customer support representative.
ORA-08321: scnmin: NOT IMPLEMENTED YET
Cause: An internal error
Action: Contact your customer support representative.
ORA-08322: scnmin: open/convert of bias lock failed
Cause: A call to the lkmgr failed to open and convert the bias lock
Action: Check to make sure 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: Check to make sure 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: Oracle timed out waiting for an event
Action: Contact your Oracle support representative
ORA-08332: rollback segment #string specified not available
Cause: (same as 1545)
Action: (same as 1545). Also, make sure you have created enough rollback segments 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-08401: invalid compiler name: string
Cause: An invalid compiler name <compname> was passed to a UTL_PG conversion routine.
Action: Correct the compiler name parameter in the PL/SQL code that called the conversion routine.
ORA-08412: error encountered in WMSGBSIZ, size for WMSGBLK is not big enough for warning message
Cause: The WMSGBSIZ is the maximun size for warning message block, it is recommanded to be 1024 bytes to 8 kbytes.
Action: Defined WMSGBLK of size between 1k to 8k bytes and update the WMSGBSIZ to the sizeof(WMSGBLK).
ORA-08413: invalid compiler type in FORMAT parameter at string
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.
ORA-08414: error encountered in string
Cause: The function <routine> returned an error. Where <routine> may be: RAW_TO_NUMER NUMBER_TO_RAW RAW_TO_NUMBER_FORMAT NUMBER_TO_RAW_FORMAT MAKE_NUMBER_TO_RAW_FORMAT MAKE_RAW_TO_NUMBER_FORMAT
Action: to take.
ORA-08429: raw data has invalid digit in display type data
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.
ORA-08430: raw data missing leading sign
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.
ORA-08431: raw data missing zero as defined in picture
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.
ORA-08432: raw data has invalid floating point data
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.
ORA-08433: invalid picture type in convert raw to number
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.
ORA-08434: raw data has invalid trailing sign
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.
ORA-08435: PICTURE MASK missing the leading sign when SIGN IS LEADING specified
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.
ORA-08436: raw data has invalid sign digit
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.
ORA-08437: invalid picture type in picture mask
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.
ORA-08440: raw buffer is too short to hold converted data
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.
ORA-08441: closed parenthesis missing in picture mask
Cause: A closed parenthesis was missing from the picture mask passed to a UTL_PG conversion routine.
Action: Correct the picture mask.
ORA-08443: syntax error in BLANK WHEN ZERO clause in mask options
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: BLANK ZERO BLANK ZEROS BLANK ZEROES BLANK WHEN ZERO BLANK WHEN ZEROS BLANK WHEN ZEROES
Action: Correct the mask options parameter.
ORA-08444: syntax error in JUSTIFIED clause in mask options
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: JUST JUST RIGHT JUSTIFIED JUSTIFIED RIGHT
Action: Correct the mask options parameter.
ORA-08445: syntax error in SIGN clause in mask options
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: SIGN LEADING SIGN LEADING SEPARATE SIGN LEADING SEPARATE CHARACTER SIGN TRAILING SIGN TRAILING SEPARATE SIGN TRAILING SEPARATE CHARACTER SIGN IS LEADING SIGN IS LEADING SEPARATE SIGN IS LEADING SEPARATE CHARACTER SIGN IS TRAILING SIGN IS TRAILING SEPARATE SIGN IS TRAILING SEPARATE CHARACTER
Action: Correct the mask options parameter.
ORA-08446: syntax error in SYNCHRONIZED clause in mask options
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: SYNC SYNC LEFT SYNC RIGHT SYNCHRONIZED SYNCHRONIZED LEFT SYNCHRONIZED RIGHT
Action: Correct the mask options parameter.
ORA-08447: syntax error in USAGE clause in mask options
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: USAGE DISPLAY USAGE COMP USAGE COMP-3 USAGE COMP-4 USAGE COMPUTATIONAL USAGE COMPUTATIONAL-3 USAGE COMPUTATIONAL-4 USAGE IS DISPLAY USAGE IS COMP USAGE IS COMP-3 USAGE IS COMP-4 USAGE IS COMPUTATIONAL USAGE IS COMPUTATIONAL-3 USAGE IS COMPUTATIONAL-4
Action: Correct the mask options parameter.
ORA-08448: syntax error in DECIMAL-POINT environment clause
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.
ORA-08449: invalid numeric symbol found in picture mask
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.
ORA-08450: invalid specification of CR in picture mask
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.
ORA-08451: invalid specification of DB in picture mask
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.
ORA-08452: specification of E in picture mask is unsupported
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.
ORA-08453: more than one V symbol specified in picture mask
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.
ORA-08454: more than one S symbol specified in picture mask
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.
ORA-08455: syntax error in CURRENCY SIGN environment clause
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.
ORA-08456: no sign in picture mask but SIGN clause in mask options
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.
ORA-08457: syntax error in SEPARATE CHARACTER option of SIGN clause
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.
ORA-08458: invalid format 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.
ORA-08459: invalid format parameter length
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.
ORA-08460: invalid environment clause in environment parameter
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.
ORA-08462: raw buffer contains invalid decimal data
Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contains invalid decimal data.
Action: Correct the input data.
ORA-08463: overflow converting decimal number to Oracle number
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 besure that the output variable is large enough to hold the Oracle number value.
ORA-08464: input raw decimal data contains more than 42 digits
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.
ORA-08465: input mask contains more than 32 characters
Cause: The input mask passed to UTL_PG numeric conversion routine contained more the 32 characters.
Action: Correct the mask input buffer.
ORA-08466: raw buffer length string is too short for string
Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine was less than %s bytes long, but the picture mask parameter specified that %s 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.
ORA-08467: error converting Oracle number to string
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. mat.
Action: Correct the call to the conversion routine. The input must be a valid Oracle number variable.
ORA-08468: mask option string is not supported
Cause: The mask option <clause> was passed to a UTL_PG conversion routine, but is not supported by UTL_PG. The <clause> can be: USAGE IS POINTER USAGE IS INDEX USAGE IS COMP-1 USAGE IS COMP-2 POINTER
Action: Remove the <clause> from the mask options parameter in the PL/SQL call to UTL_PG.
ORA-08498: Warning: picture mask "string" overrides picture mask option "USAGE IS string" to "USAGE IS DISPLAY"
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.
ORA-08499: Warning: picture mask options "string" ignored by UTL_PG
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.
ORA-09200: sfccf: error creating file
Cause: Could be out of disk space
Action: See OSD error accompanying this message
ORA-09201: sfcopy: error copying file
Cause: Block sizes may not match
Action: See OSD error accompanying this message
ORA-09202: sfifi: error identifying file
Cause: db_block_size specified in init.ora could be incorrect
Action: See OSD error accompanying this message
ORA-09203: sfofi: error opening file
Cause: File attributes may have changed
Action: See OSD error accompanying this message
ORA-09204: sfotf: error opening temporary file
Cause: Incorrect path may have been specified for the file
Action: See OSD error accompanying this message
ORA-09205: sfqio: error reading or writing to disk
Cause: File may have been truncated or corrupted
Action: See OSD error accompanying this message
ORA-09206: sfrfb: error reading from file
Cause: File may have been truncated or corrupted
Action: See OSD error accompanying this message
ORA-09207: sfsrd: error reading from file
Cause: File may have been truncated or corrupted
Action: See OSD error accompanying this message
ORA-09208: sftcls: error closing file
Cause: File may have been corrupted
Action: See OSD error accompanying this message
ORA-09209: sftget: error reading from file
Cause: File may have been truncated or corrupted
Action: See OSD error accompanying this message
ORA-09210: sftopn: error opening file
Cause: Incorrect path may have been specified for the file
Action: See OSD error accompanying this message
ORA-09211: sfwfb: error writing to file
Cause: File may have been truncated or corrupted
Action: See OSD error accompanying this message
ORA-09212: sfwfbmt: error writing to file
Cause: File may have been truncated or corrupted
Action: See OSD error accompanying this message
ORA-09213: slgfn: error fabricating file name
Cause: Filename may be too long
Action: See OSD error accompanying this message
ORA-09214: sfdone: I/O error detected
Cause: File may have been truncated or corrupted
Action: See OSD error accompanying this message
ORA-09215: sfqio: error detected in IOCompletionRoutine
Cause: File may have been truncated or corrupted
Action: See OSD error accompanying this message
ORA-09216: sdnfy: bad value "string" for parameter string
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.
ORA-09217: sfsfs: failed to resize file
Cause: Could be out of disk space
Action: See OSD error accompanying this message
ORA-09218: sfrfs: failed to refresh file size
Cause: File may be corrupted or truncated
Action: See OSD error accompanying this message
ORA-09240: smpalo: error allocating PGA memory
Cause: Could be out of memory
Action: See OSD error accompanying this message
ORA-09241: smsalo: error allocating SGA memory
Cause: Could be out of memory
Action: See OSD error accompanying this message
ORA-09243: smsget: error attaching to SGA
Cause: SGA may not have been created (database not started)
Action: See OSD error accompanying this message
ORA-09260: sigpidu: error obtaining process id
Cause: May be out of resources
Action: See OSD error accompanying this message
ORA-09261: spdcr: error creating detached (background) process
Cause: Could be out of resources
Action: See OSD error accompanying this message
ORA-09262: spdde: error terminating detached (background) process
Cause: Could be out of resources
Action: See OSD error accompanying this message
ORA-09263: spini: error initializing process
Cause: Could be out of memory
Action: See OSD error accompanying this message
ORA-09264: sptpa: error flagging process
Cause: Could be out of resources
Action: See OSD error accompanying this message
ORA-09265: spwat: error temporarily suspending process
Cause: Could be out of resources
Action: See OSD error accompanying this message
ORA-09266: spawn: error starting an Oracle process
Cause: Could be out memory
Action: See OSD error accompanying this message
ORA-09270: szalloc: error allocating memory for security
Cause: Could be out of memory
Action: See OSD error accompanying this message
ORA-09271: szlon: error verifying user name
Cause: Username may be too long
Action: See OSD error accompanying this message
ORA-09272: remote os logon is not allowed
Cause: Remote os login attempted when not allowed.
Action: See OSD error accompanying this message
ORA-09273: szrfc: error verifying role name
Cause: An OS error was returned when verifying the role name.
Action: See OSD error accompanying this message
ORA-09274: szrfc: insufficient role name buffer space
Cause: An OS role name was too long.
Action: See OSD error accompanying this message
ORA-09275: CONNECT INTERNAL is not a valid DBA connection
Cause: CONNECT INTERNAL is no longer supported for DBA connections.
Action: Please try to connect AS SYSDBA or AS SYSOPER.
ORA-09276: All bequeath database links must be loopback database links
Cause: A non-loopback bequeath connect string was supplied for a database link.
Action: Please use a connect string with a different transport protocol, or specify a loopback connect string (one that points to the instance for the current session) using "(PROGRAM=<this instance"s ORACLE_HOME>/bin/oracle)" and, optionally, "(ENVS=""ORACLE_SID=<this instance"s ORACLE_SID>"")".
ORA-09280: sllfcf: error closing file
Cause: File may be corrupted
Action: See OSD error accompanying this message
ORA-09281: sllfop: error opening file
Cause: Possibly incorrect path specified to the file
Action: See OSD error accompanying this message
ORA-09282: sllfrb: error reading records
Cause: File could be corrupted
Action: See OSD error accompanying this message
ORA-09283: sllfsk: error skipping records
Cause: File could be corrupted
Action: See OSD error accompanying this message
ORA-09284: sllfop: cannot allocate read buffer
Cause: malloc() system call returned an error. The system might have run out of heap space
Action: Check additional information for the OS error.
ORA-09285: sllfop: unrecognizable processing option, incorrect format
Cause: Processing option passed is of incorrect format
Action: Consult your IUG for permissible formats
ORA-09290: sksaalo: error allocating memory for archival
Cause: Could be out of memory
Action: See OSD error accompanying this message
ORA-09291: sksachk: invalid device specified for archive destination
Cause: Unable to access directory
Action: Specify a valid device in ARCHIVE control string
ORA-09292: sksabln: unable to build archive file name
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 init.ora
ORA-09293: sksasmo: unable to send message to console
Cause: An error was returned while attempting to send a message to the console operator
Action: See OSD error accompanying this message
ORA-09300: osncon: unable to connect, DPMI not available
Cause: Unable to detect the presence of DPMI
Action: Restart Windows and retry
ORA-09301: osncon: local kernel only supported in standard mode
Cause: An attempt was made to connect to S: while in enhanced mode
Action: Restart Windows in standard mode
ORA-09310: sclgt: error freeing latch
Cause: Internal error
Action: See OSD error accompanying this message
ORA-09311: slsleep: error temporarily suspending process
Cause: May be out of resources
Action: See OSD error accompanying this message
ORA-09312: slspool: error spooling file to printer
Cause: The vm_allocate system call attached the SGA at an incorrect location.
Action: Verify that the SGA attach address is valid.
ORA-09747: pw_detachPorts: server call pws_detach failed.
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.
ORA-09748: pws_look_up: fork failed
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.
ORA-09749: pws_look_up: port lookup failure
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.
ORA-09750: pw_attachPorts: port_rename failed.
Cause: The port_rename system call failed; possible internal error.
Action: Check return code in sercerrno, report to Oracle customer support.
ORA-09751: pw_attachPorts: server call pws_attach failed.
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.
ORA-09752: pw_attachPorts: port_allocate failed.
Cause: The port_allocate system call failed; possible resource exhaustion.
Action: Check return code in sercerrno, report to Oracle customer support.
ORA-09753: spwat: invalid process number.
Cause: Function was passed an invalid oracle process id.
Action: Internal error. Additional information indicates the invalid process id.
ORA-09754: sppst: invalid process number passed to sppst.
Cause: Function was passed an invalid oracle process id.
Action: Internal error. Contact Oracle support.
ORA-09755: osngpn: port allocation failure.
Cause: The port_allocate system call failed.
Action: Possible system resource shortage; check the error code in sercerrno.
ORA-09756: osnpns: no port in the name server.
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.
ORA-09757: osnipn: port allocation failure.
Cause: The port_allocate system call failed.
Action: Possible system resource shortage; check the error code in sercerrno.
ORA-09758: osnipn: could not check port in name server.
Cause: The netname_check_in call failed.
Action: Check the error code in sercerrno. Make sure the network name server is running.
ORA-09759: osnsbt: bad message received.
Cause: The msg_receive system call failed, or received a bad message.
Action: Internal error. Report the error code returned in sercerrno.
ORA-09760: osnpui: cannot send break message
Cause: The Pipe driver could not send a break message to the ORACLE shadow process break thread.
Action: Contact your customer support representative.
ORA-09761: pw_destroyPorts: server call pws_stop_instance failed.
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.
ORA-09762: sNeXT_instanceName: translation error.
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.
ORA-09764: osnmop: access error on oracle executable
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.
ORA-09765: osnmop: fork failed
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.
ORA-09766: osnmop: buffer allocation failure.
Cause: The Mach driver failed to allocate enough vm space for its I/O buffers.
Action: Decrease the value of buffer_size parameter in the Two-Task driver hoststring.
ORA-09767: osnmfs: bad return code from msg_send.
Cause: The msg_send system call failed while flushing the Mach driver"s send buffer.
Action: Internal error. Contact your customer support representative.
ORA-09768: osnmgetmsg: could not read a message
Cause: The msg_receive system call returned a failure code while waiting for a message in the Mach driver.
Action: Internal error. Contact your customer support representative.
ORA-09769: osnmbr: cannot send break message
Cause: The Mach driver could not send a break message to the ORACLE shadow process break thread.
Action: Internal error. Contact your customer support representative.
ORA-09770: pws_look_up: translation failure.
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.
ORA-09771: osnmwrtbrkmsg: bad return code from msg_send.
Cause: The msg_send sytem call failed while sending a Mach driver break.
Action: Internal error. Contact your customer support representative.
ORA-09772: osnpmetbrkmsg: message from host had incorrect message type
Cause: The Mach driver received a message having an unrecognizable message type.
Action: Internal error. Contact your customer support representative.
ORA-09773: osnmgetdatmsg: message from host had incorrect message type
Cause: The Mach driver received a message having an unrecognizable message type.
Action: Internal error. Contact your customer support representative.
ORA-09774: osnmui: cannot send break message
Cause: The Mach driver could not send a break message to the ORACLE shadow process break thread.
Action: Internal error. Contact your customer support representative.
ORA-09775: osnmrs: reset protocol error
Cause: The Mach two-task driver could not reset the connection.
Action: Internal error. Contact your customer support representative.
ORA-09776: pws_look_up: access error on (Oracle helper) executable
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.
ORA-09777: osnpbr: cannot send break message
Cause: The pipe driver could not send a break message to the ORACLE shadow process break thread.
Action: Internal error. Contact your customer support representative.
ORA-09778: snynfyport: failure allocating the notify port.
Cause: The routine failed to allocate or set the task"s notify port.
Action: Possible operating system error. Contact Oracle support.
ORA-09779: snyGetPort: failure to allocate a port.
Cause: The port_allocate system call failed; system resources might be exhausted.
Action: Possible operating system error. Contact Oracle support.
ORA-09786: sllfop: open error, unable to open file.
Cause: Processing option passed is of incorrect format.
Action: Consult your IUG for permissible formats.
ORA-09788: sllfrb: unable to read file.
Cause: Read system call returned an error.
Action: Check errno. Verify file exists.
ORA-09789: sllfsk: unable to read file.
Cause: Read system call returned an error.
Action: Check errno. Verify file exists.
ORA-09790: sllfcf: unable to close file.
Cause: Close system call returned an error.
Action: Check errno.
ORA-09791: slembdf: translation error, unable to translate error file name.
Cause: Additional information indicates error returned from sltln.
Action: Check additional information.
ORA-09792: sllfop: cannot allocate read buffer.
Cause: Malloc system call returned an error. The system might have run out of heap space.
Action: Check additional information for the OS error.
ORA-09793: szguns: length of user name is greater than buffer.
Cause: The length of the name of the user being looked up is longer than size of the buffer provided by the calling routine.
Action: This is an internal error. Contact Oracle Support Services.
ORA-09794: szrbuild: length of role name is greater than buffer.
Cause: The length of the name of the role being looked up is longer than size of the buffer provided by the calling routine.
Action: This is an internal error. Contact Oracle Support Services.
ORA-09795: szrbuild: malloc of role structure failed.
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.
ORA-09796: szrbuild: malloc of role name failed.
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.
ORA-09797: Failed to get O/S MAC privileges.
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.
ORA-09798: Label comparison failed.
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.
ORA-09799: File label retrieval failed.
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.
ORA-09800: Process sensitivity label retrieval failed.
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.
ORA-09801: Unable to get user ID from connection
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.
ORA-09802: Conversion of binary label to string failed.
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.
ORA-09803: Allocation of string buffer failed.
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.
ORA-09804: Class conversion from binary to ORACLE failed.
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.
ORA-09805: conversion of category number to string failed.
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.
ORA-09806: Allocation of label string buffer failed.
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.
ORA-09807: Conversion of label from string to binary failed.
Cause: ORACLE was unable to convert the string representation of a label to binary format.
Action: Re-enter a valid label.
ORA-09808: Could not obtain user clearance.
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.
ORA-09809: Unable to get user"s group ID from connection
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.
ORA-09810: Unable to get process ID from connection
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.
ORA-09811: Unable to initialize package.
Cause: ORACLE was unable to initialize the library used to obtain security information.
Action: This is an internal error. Contact Oracle Support Services.
ORA-09812: Unable to get user clearance from connection
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.
ORA-09813: Unable to get directory status
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.
ORA-09814: Unable to expand file name
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.
ORA-09815: File name buffer overflow
Cause: The buffer that ORACLE uses to hold the expanded name of a too small.
Action: This is an internal error. Contact Oracle Support Services.
ORA-09817: Write to audit file failed.
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.
ORA-09818: Number is too large
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.
ORA-09819: Number exceeds maximum legal value
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.
ORA-09820: Conversion of class string to numeric representation failed.
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.
ORA-09821: Numeric label is not valid
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.
ORA-09822: Translation of audit file name failed.
Cause: Oracle was unable to translate the value of the AUDIT_FILE_DEST initialization parameter.
Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services.
ORA-09823: device name is too long
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.
Action: This is an internal error. Contact Oracle Support Services.
ORA-09824: Unable to enable allowmacaccess privilege.
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.
ORA-09825: Unable to disable allowmacaccess privilege.
Cause: ORACLE was not able to turn off the allowmacaccess privilege after doing a label comparison.
Action: This is an internal error. Contact Oracle Support Services.
ORA-09826: SCLIN: cannot initialize atomic latch.
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.
ORA-09828: SCLFR: atomic latch return error.
Cause: System call atomic_op() return unexpected error.
Action: Check additional information in the trace file.
ORA-09829: pw_createPorts: server call pws_start_instance failed.
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.
ORA-09830: snyAddPort: failed to perform a remote procedure call.
Cause: The msg_rpc system call returned an error.
Action: Internal error. Contact Oracle support.
ORA-09831: snyStartThread: failed to build the server port set.
Cause: The routine failed to build a port set on which to listen for requests.
Action: Possible operating system failure. Contact Oracle support.
ORA-09832: infoCallback: bad message format.
Cause: The routine received an incorrectly formatted request.
Action: Internal error. Contact Oracle support.
ORA-09833: addCallback: bad message format.
Cause: The routine received an incorrectly formatted request.
Action: Internal error. Contact Oracle support.
ORA-09834: snyGetPortSet: failed to collect info on a port.
Cause: The port_status system called failed.
Action: Possible operating system error. Contact Oracle support.
ORA-09835: addCallback: callback port is already in a set.
Cause: The port to be added to the callback list is already in a port set.
Action: Internal error. Contact Oracle support.
ORA-09836: addCallback: could not add a port to the callback set.
Cause: The port_set_add system called failed.
Action: Possible operating system error. Contact Oracle support.
ORA-09837: addCallback: could not add allocate a callback link.
Cause: The malloc library call failed to allocate space for a callback link.
Action: Possible operating system error. Contact Oracle support.
ORA-09838: removeCallback: failure removing the callback port.
Cause: The port port_set_remove system call failed.
Action: Possible operating system error. Contact Oracle support.
ORA-09839: removeCallback: callback port is not in the callback set.
Cause: The port to be removed to the callback list is not in the callback port set.
Action: Internal error. Contact Oracle support.
ORA-09840: soacon: Name translation failure.
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.
ORA-09841: soacon: Name translation failure.
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.
ORA-09842: soacon: Archmon unable to create named pipe.
Cause: mknod() failed to create named pipe ?/dbs/mon2arch_@.
Action: Your current OS 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.
ORA-09843: soacon: Archmon unable to create named pipe.
Cause: mknod() failed to create named pipe ?/dbs/arch2mon_@.
Action: Your current OS 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.
ORA-09844: soacon: Archmon unable to open named pipe.
Cause: open() failed to open named pipe ?/dbs/mon2arch_@.
Action: Only the oracle dba can run archmon. Make sure that your current OS login has owner or group search permission for the ORACLE_HOME/dbs directory. The max number of open files may have been exceeded.
ORA-09845: soacon: Archmon unable to open named pipe.
Cause: open() failed to open named pipe ?/dbs/arch2mon_@.
Action: Only the oracle dba can run archmon. Make sure that your current OS login has owner or group search permission for the ORACLE_HOME/dbs directory. The max number of open files may have been exceeded.
ORA-09846: soacon: ARCH unable to open named pipe.
Cause: open() failed to open named pipe ?/dbs/mon2arch_@.
Action: Make sure that the OS userid of the currently running database has search permission for the ORACLE_HOME/dbs directory. The max number of open files may have been exceeded.
ORA-09847: soacon: ARCH unable to open named pipe.
Cause: open() failed to open named pipe ?/dbs/arch2mon_@.
Action: Make sure that the OS userid of the currently running database has search permission for the ORACLE_HOME/dbs directory. The max number of open files may have been exceeded.
ORA-09850: soacon: Archmon unable to lock named pipe.
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.
ORA-09851: soacon: Archmon unable to lock named pipe.
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.
ORA-09853: snyRemovePort: bad return code from request.
Cause: The request to remove a port from the callback set returned a failure code.
Action: Possible operating system error. Contact Oracle support.
ORA-09854: snyPortInfo: bad return code from request.
Cause: The request to collect info on a port in the callback set returned a failure code.
Action: Possible operating system error. Contact Oracle support.
ORA-09855: removeCallback: bad message format.
Cause: The routine received an incorrectly formatted request.
Action: Internal error. Contact Oracle support.
ORA-09856: smpalo: vm_allocate error while allocating pga.
Cause: The vm_allocate system call returned an error.
Action: Check returned error. Possibly out of system resources.
ORA-09857: smprset: vm_protect error while protecting pga.
Cause: The vm_protect system call returned an error.
Action: Internal error. Contact Oracle support.
ORA-09858: sfngat: the input file name is not in the OMF format
Cause: The function sfngat() received a filename which is not an OMF file name.
Action: Further diagnostic information should be in the error stack.
ORA-09859: sfngat: the input file name is not in the autobackup OMF format
Cause: The function sfngat() received a filename which is not an autobackup OMF file name.
Action: Further diagnostic information should be in the error stack.
