75 ORA-07500 to ORA-09857
- ORA-07500: scglaa: $cantim unexpected return
-
Cause: VMS system service $CANTIM returned an unexpected value
- ORA-07501: scgtoa: $deq unexpected return
-
Cause: VMS system service $DEQ returned an unexpected value
- ORA-07502: scgcmn: $enq unexpected return
-
Cause: VMS system service $ENQ returned an unexpected value
- ORA-07503: scgcmn: $setimr unexpected return
-
Cause: VMS system service $SETIMR returned an unexpected value
- ORA-07504: scgcmn: $hiber unexpected return
-
Cause: VMS system service $HIBER returned an unexpected value
- ORA-07505: scggt: $enq parent lock unexpected return
-
Cause: VMS system service $ENQ returned an unexpected value
- ORA-07506: scgrl: $deq unexpected return on lockid string
-
Cause: VMS system service $DEQ returned an unexpected value
- ORA-07507: scgcm: unexpected lock status condition
-
Cause: A global locking system service returned an unexpected value.
- ORA-07508: scgfal: $deq all unexpected return
-
Cause: VMS system service $DEQ returned an unexpected value
- ORA-07509: scgfal: $deq parent lock unexpected return
-
Cause: VMS system service $DEQ returned an unexpected value
- ORA-07510: scgbrm: $getlki unexpected return on lockid string
-
Cause: VMS system service $GETLKI returned an unexpected value
- ORA-07511: sscggtl: $enq unexpected return for master termination lock
-
Cause: VMS system service $ENQ returned an unexpected value
- ORA-07512: sscggtl: $enq unexpected return for client termination lock
-
Cause: VMS system service $ENQ returned an unexpected value
- ORA-07513: sscgctl: $deq unexpected return on cancel of term. lock
-
Cause: VMS system service $DEQ returned an unexpected value
- ORA-07514: scgcan: $deq unexpected return while canceling lock
-
Cause: VMS system service $DEQ returned an unexpected value
- ORA-07534: scginq: $getlki unexpected return on lockid string
-
Cause: VMS system service $GETLKI returned an unexpected value
- ORA-07548: sftopn: Maximum number of files already open
-
Cause: Too many test files open
- ORA-07549: sftopn: $OPEN failure
-
Cause: VMS system service $OPEN failed
- ORA-07550: sftopn: $CONNECT failure
-
Cause: VMS system service $OPEN failed
- ORA-07551: sftcls: $CLOSE failure
-
Cause: VMS system service $CLOSE failed
- ORA-07552: sftget: $GET failure
-
Cause: VMS system service $GET failed
- ORA-07561: szprv: $IDTOASC failure
-
Cause: VMS system service $IDTOASC failed
- ORA-07562: sldext: extension must be 3 characters
-
Cause: An extension was found but it is of improper length
- ORA-07563: sldext: $PARSE failure
-
Cause: VMS system service $PARSE failed
- ORA-07564: sldext: wildcard in filename or extension
-
Cause: A wildcard was used in the file name
- ORA-07565: sldext: $SEARCH failure
-
Cause: VMS system service $SEARCH failed
- ORA-07568: slspool: $OPEN failure
-
Cause: VMS system service $OPEN failed
- ORA-07569: slspool: $CLOSE failure
-
Cause: VMS system service $CLOSE failed
- ORA-07570: szrfc: $IDTOASC failure
-
Cause: VMS system service $IDTOASC failed
- ORA-07571: szrfc: $FIND_HELD failure
-
Cause: VMS system service $FIND_HELD failed
- ORA-07572: szrfc: insufficient rolename buffer space
-
Cause: An OS role name was too long.
- ORA-07573: slkhst: could not perform host operation
-
Cause: VMS system service LIB$SPAWN failed
- ORA-07574: szrfc: $GETUAI failure
-
Cause: VMS system service $GETUAI failed
- ORA-07576: sspexst: $GETJPIW failure on process ID string
-
Cause: VMS system service $GETJPIW failed
- 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.
- ORA-07578: szprv: $FIND_HELD failure
-
Cause: VMS system service $FIND_HELD failed
- ORA-07579: spini: $DCLEXH failure
-
Cause: VMS system service $PARSE failed
- ORA-07580: spstp: $GETJPIW failure
-
Cause: VMS system service $GETJPIW failed
- ORA-07581: spstp: cannot derive SID from unexpected process name
-
Cause: A background process did not have name of correct form
- ORA-07582: spstp: ORA_SID has illegal value
-
Cause: The ORA_SID must exist and be less than 6 characters
- 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).
- ORA-07585: spdcr: $PARSE failure
-
Cause: VMS system service $PARSE failed
- ORA-07586: spdcr: $SEARCH failure
-
Cause: VMS system service $SEARCH failed
- ORA-07587: spdcr: $CREPRC failure
-
Cause: VMS system service $CREPRC failed
- ORA-07588: spdcr: $GETJPIW get image name failure
-
Cause: VMS system service $GETJPIW failed
- ORA-07589: spdde: system ID not set
-
Cause: The logical name ORA_SID doesn't translate to a valid value.
- ORA-07590: spdde: $DELPRC failure
-
Cause: VMS system service $DELPRC failed
- ORA-07591: spdde: $GETJPIW failure
-
Cause: VMS system service $GETJPIW failed
- ORA-07592: sspgprv: Error obtaining required privileges
-
Cause: While obtaining needed privileges, an error was returned from SYS$SETPRV.
- ORA-07593: ssprprv: Error release privileges
-
Cause: While releasing privileges, an error was returned from SYS$SETPRV.
- ORA-07594: spiip: $GETJPIW failure
-
Cause: VMS system service $GETJPIW failed
- ORA-07595: sppid: $GETJPIW failure
-
Cause: VMS system service $GETJPIW failed
- ORA-07596: sptpa: $GETJPIW failure
-
Cause: VMS system service $GETJPIW failed
- ORA-07597: spguns: $GETJPIW failure
-
Cause: VMS system service $GETJPIW failed
- ORA-07598: spwat: $SETIMR failure
-
Cause: VMS system service $GETJPIW failed
- ORA-07599: spwat: $SCHDWK failure
-
Cause: VMS system service $SCHDWK failed
- ORA-07600: slkmnm: $GETSYIW failure
-
Cause: VMS system service $GETSYIW failed
- ORA-07601: spguno: $GETJPIW failure
-
Cause: VMS system service $GETJPIW failed
- ORA-07602: spgto: $GETJPIW failure
-
Cause: VMS system service $GETJPIW failed
- ORA-07605: szprv: $ASCTOID failure
-
Cause: VMS system service $ASCTOID failed
- ORA-07606: szprv: $CHKPRO failure
-
Cause: VMS system service $CHKPRO failed
- ORA-07607: szaud: $SNDOPR failure
-
Cause: VMS system service $SNDOPR failed
- ORA-07608: szprv: $GETUAI failure
-
Cause: VMS system service $GETUAI failed
- ORA-07609: szprv: $HASH_PASSWORD failure
-
Cause: VMS system service $HASH_PASSWORD failed
- ORA-07610: $GETJPIW failed in retrieving the user's MAC priviledges
-
Cause: VMS system service $GETJPIW failed
- ORA-07612: $GETUAI failed in retrieving the user's clearance level
-
Cause: VMS system service $GETUAI failed
- ORA-07613: $GETJPIW failed in retrieving the user's process label
-
Cause: VMS system service $GETJPIW failed
- ORA-07614: $CHANGE_CLASS failed in retrieving the user's process label
-
Cause: VMS system service $CHANGE_CLASS failed
- ORA-07615: $CHANGE_CLASS failed in retrieving the specified file label
-
Cause: VMS system service $CHANGE_CLASSS failed
- ORA-07616: $CHANGE_CLASS failed in retrieving the specified device label
-
Cause: VMS system service $CHANGE_CLASS failed
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-07622: smscre: $CREATE failure
-
Cause: While creating the system global area (SGA) backing file, VMS system service $CREATE failed.
- ORA-07623: smscre: $CRMPSC failure
-
Cause: While creating the system global area (SGA), VMS system service $CRMPSC failed.
- ORA-07624: smsdes: $DGBLSC failure
-
Cause: While deleting the system global area (SGA), VMS system service $DGBLSC failed.
- 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.
- 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.
- ORA-07627: smsfre: $CRETVA failure
-
Cause: While unmapping the system global area (SGA) during logoff, VMS system service $CRETVA failed.
- 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.
- 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.
- ORA-07630: smpdal: $DELTVA failure
-
Cause: While deleting the program global area (PGA) during logoff, VMS system service $DELTVA failed.
- 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.
- ORA-07632: smsrcx: $DELTVA failure
-
Cause: While deleting a context area, VMS system service $DELTVA failed.
- ORA-07633: smsdbp: illegal protection value
-
Cause: The buffer debug function was called with an illegal value. This is an internal error.
- ORA-07634: smsdbp: $CRETVA failure
-
Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $CRETVA failed.
- ORA-07635: smsdbp: $SETPRT failure
-
Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $SETPRT failed.
- ORA-07636: smsdbp: $MGBLSC failure
-
Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $MGBLSC failed.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-07643: smsalo: SMSVAR is invalid
-
Cause: an internal error
- ORA-07645: sszfsl: $CHANGE_CLASS failure
-
Cause: While attempting to set the label on a file, SEVMS service $CHANGE_CLASS failed.
- ORA-07646: sszfck: $CREATE failure
-
Cause: While attempting to create a file, VMS system service $CREATE failed.
- ORA-07647: sszfck: $OPEN failure
-
Cause: While attempting to reopen a file, VMS system service $OPEN failed.
- 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.
- ORA-07655: slsprom:$TRNLOG failure
-
Cause: While attempting to translate SYS$INPUT during a prompt for a password, VMS system service $TRNLOG failed.
- ORA-07656: slsprom:$GETDVI failure
-
Cause: While attempting to get device characteristics during a prompt for a password, VMS system service $GETDVI failed.
- ORA-07657: slsprom:$ASSIGN failure
-
Cause: While prompting for a password, VMS system service $ASSIGN failed.
- ORA-07658: slsprom:$QIOW read failure
-
Cause: While prompting for a password, VMS system service $QIOW failed.
- ORA-07665: ssrexhd: recursive exception encountered string string string string string string
-
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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-07682: sou2os: set kernel dispatch fail err
-
Cause: During Oracle shared image entry, a dispatch to kernel mode failed.
- 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.
- 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.
- 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.
- ORA-07700: sksarch: interrupt received
-
Cause: An interrupt was received while archiving the logs
- ORA-07701: sksatln: internal exception: output buffer too small
-
Cause: Overflow of buffer for parsing archive control text string
- ORA-07702: unrecognized device type in archive text
-
Cause: Unrecognized device type in archive text
- 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 '/'.
- 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 ':'.
- ORA-07705: sksaprs: device name buffer too small
-
Cause: The buffer supplied for the device name is too small. This is an internal error.
- 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.
- 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.
- 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.
- ORA-07709: sksaprs: archiving to a remote host is not allowed
-
Cause: The user specified a remote disk for archiving via DECnet.
- ORA-07710: sksaprs: file name buffer too small
-
Cause: The buffer supplied for the file name is too small. This is an internal error.
- ORA-07713: sksamtd: could not mount archival device (SYS$MOUNT failure)
-
Cause: VMS system service SYS$MOUNT failed
- ORA-07715: sksadtd: could not dismount archival device (SYS$DISMNT failure)
-
Cause: VMS system service SYS$DISMNT failed
- ORA-07716: sksachk: invalid device specification for ARCHIVE
-
Cause: VMS system service SYS$GETDVI failed"
- ORA-07717: sksaalo: error allocating memory
-
Cause: VMS system service LIB$GET_VM failed"
- ORA-07718: sksafre: error freeing memory
-
Cause: VMS system service LIB$FREE_VM failed
- ORA-07721: scgcm: not enough OS resource to obtain system enqueue
-
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.
- ORA-07740: slemop: incorrect handle size (programming error)
-
Cause: structures used for reading error message files do not match
- ORA-07741: slemop: $OPEN failure
-
Cause: VMS system service $OPEN failed
- ORA-07742: slemop: $CONNECT failure
-
Cause: VMS system service $CONNECT failed
- ORA-07743: slemop: incorrect error file attributes
-
Cause: An error message file is of incorrect format
- ORA-07744: slemcl: invalid error message file handle
-
Cause: seal in passed in handle does not match correct value
- ORA-07745: slemcl: $CLOSE failure
-
Cause: VMS system service $CLOSE failed
- ORA-07746: slemrd: invalid error message file handle
-
Cause: seal in passed in handle does not match correct value
- ORA-07747: slemrd: $READ failure
-
Cause: VMS system service $READ failed
- ORA-07750: slemcr: fopen failure
-
Cause: An attempt to create a message file failed. This is an internal error.
- ORA-07751: slemcr: malloc failure
-
Cause: An attempt to allocate a cache for a newly-created message file failed. This is an internal error.
- ORA-07753: slemcf: fseek before write failure
-
Cause: An attempt to seek before writing a message file cache element failed. This is an internal error.
- ORA-07754: slemcf: fwrite failure
-
Cause: An attempt to write a message file cache element failed. This is an internal error.
- ORA-07755: slemcf: fseek before read failure
-
Cause: An attempt to seek before reading a message file cache element failed. This is an internal error.
- ORA-07756: slemcf: fread failure
-
Cause: An attempt to read a message file cache element failed. This is an internal error.
- ORA-07757: slemcc: invalid handle
-
Cause: The seal in a passed-in handle does not match correct value. This is an internal error.
- ORA-07758: slemcw: invalid handle
-
Cause: The seal in a passed-in handle does not match correct value. This is an internal error.
- ORA-07759: slemtr: invalid destination
-
Cause: The destination string provided to the function is too short This is an internal error.
- ORA-07760: slemtr: $open failure
-
Cause: the $open service failed. This is an internal error
- ORA-07800: slbtpd: invalid number
-
Cause: An impossible request for binary to decimal conversion was made
- ORA-07801: slbtpd: invalid exponent
-
Cause: An impossible request for binary to decimal conversion was made
- ORA-07802: slbtpd: overflow while converting to packed decimal
-
Cause: An impossible request for binary to decimal conversion was made
- ORA-07803: slpdtb: invalid packed decimal nibble
-
Cause: An impossible request for decimal to binary conversion was made
- ORA-07804: slpdtb: number too large for supplied buffer
-
Cause: An impossible request for decimal to binary conversion was made
- ORA-07820: sspscn: SYS$CRELNM failure
-
Cause: An error was returned from the SYS$CRELNM function
- ORA-07821: sspsdn: SYS$DELLNM failure
-
Cause: An error was returned from the SYS$DELLNM function
- ORA-07822: sspscm: SYS$CREMBX failure
-
Cause: An error was returned from the SYS$CREMBX function while trying to create the process dump mailbox.
- ORA-07823: sspsqr: $QIO failure
-
Cause: An error was returned from $QIO while trying to queue a read to the process dump mailbox.
- ORA-07824: sspain: $SETIMR failure
-
Cause: An error was returned from SYS$SETIMR while trying to queue a process spin-watch timer.
- ORA-07825: sspsck: $QIO failure at AST level
-
Cause: An error was returned from SYS$QIO while trying to read the process dump mailbox.
- ORA-07826: sspscm: SYS$GETDVIW failure
-
Cause: An error was returned from SYS$GETDVIW while trying to get information about the process dump mailbox.
- ORA-07840: sllfop: LIB$GET_VM failure
-
Cause: An error was returned from LIB$GET_VM while attempting to allocate memory for an i/o vector.
- ORA-07841: sllfop: SYS$OPEN failure
-
Cause: An error was returned from SYS$OPEN while attempting to open the data file for reading
- ORA-07842: sllfcl: SYS$CLOSE failure
-
Cause: An error was returned from SYS$CLOSE while attempting to close the input data file
- ORA-07843: sllfcl: LIB$FREE_VM failure
-
Cause: An error was returned from LIB$FREE_VM while attempting to free the memory for the i/o vector
- ORA-07844: sllfop: LIB$GET_VM failure
-
Cause: An error was returned from LIB$GET_VM while attempting to allocate memory for data and index buffers
- ORA-07845: sllfcl: LIB$FREE_VM failue
-
Cause: An error was returned from LIB$FREE_VM while attempting to free memory used by data and index buffers
- ORA-07846: sllfop: string byte record too big for string byte user buffer
-
Cause: The longest record in the file will not fit into the largest data buffer that can be allocated
- ORA-07847: sllfop: $CONNECT failure
-
Cause: An error was returned by SYS$CONNECT while attempting to open the data file
- ORA-07848: sllfrb: $GET failure
-
Cause: An error was returned by SYS$GET while attempting to read the data file
- ORA-07849: sllfsk: $GET failure
-
Cause: An error was returned by SYS$GET while attempting to skip records in the input file
- ORA-07850: sllfop: bad option
-
Cause: You are using a bad option to loader Fixed= is one legal option. Check documentation for others.
- ORA-07860: osnsoi: error setting up interrupt handler
-
Cause: An error occurred while setting up the control interrupt handler
- ORA-07880: sdopnf: internal error
-
Cause: A list of all files open by this process could not be obtained.
- ORA-08000: maximum number of session sequence lists exceeded
-
Cause: the sequence parent state objects for this session are all used
- ORA-08002: sequence string.CURRVAL is not yet defined in this session
-
Cause: sequence CURRVAL has been selected before sequence NEXTVAL
- ORA-08003: sequence string.NEXTVAL exceeds internal limits
-
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.
- ORA-08004: sequence string.NEXTVAL string stringVALUE and cannot be instantiated
-
Cause: instantiating NEXTVAL would violate one of MAX/MINVALUE
- ORA-08005: specified row does not exist
-
Cause: A row with the given rowid does not exist in any of the tables given
- ORA-08006: specified row no longer exists
-
Cause: the row has been deleted by another user since the operation began
- ORA-08007: Further changes to this block by this transaction not allowed
-
Cause: Max locks have been reached for this transaction in this block
- 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
- ORA-08100: index is not valid - see trace file for diagnostics
-
Cause: Validate Index detected an inconsistency in its argument index
- ORA-08101: index key does not exist file string: (root string, node string) blocks (string)
-
Cause: Internal error: possible inconsistency in index
- ORA-08102: index key not found, obj# string, file string, block string (string)
-
Cause: Internal error: possible inconsistency in index
- 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.
- 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
- ORA-08105: Oracle event to turn off smon cleanup for online index build
-
Cause: set this event only under the supervision of Oracle development
- ORA-08106: cannot create journal table string.string
-
Cause: The online index builder could not create its journal table
- ORA-08108: may not build or rebuild this type of index online
-
Cause: only support normal index or IOT top-level index
- ORA-08109: nosort is not a supported option for online index build
-
Cause: may not specify nosort for online index build
- ORA-08110: Oracle event to test SMON cleanup for online index build
-
Cause: Oracle Kernel test only
- ORA-08111: a partitioned index may not be coalesced as a whole
-
Cause: User attempted to coalesce a partitioned index using ALTER INDEX COALESCE statement, which is illegal
- ORA-08112: a composite partition may not be coalesced as a whole
-
Cause: User attempted to coalesce a composite partition
- ORA-08113: composite partition index may not be compressed
-
Cause: User attempted to compress a composite partition index
- ORA-08114: can not alter a fake index
-
Cause: User attempted to alter a fake index
- ORA-08115: can not online create/rebuild this index type
-
Cause: User attempted to create index type that online doesnot support
- ORA-08116: can not acquire dml enough lock(S mode) for online index build
-
Cause: User attempted to create index online without allowing DML Share lock
- ORA-08117: Index Organized Table operation released its block pin
-
Cause: Block maintenance forced the release of a block pin
- ORA-08118: Deferred FK constraints cannot be enforced, index too big (string)
-
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.
- ORA-08119: The new initrans will make the index too big
-
Cause: Specifying the initrans need additional space to hold the index key which might make the index too big
- ORA-08120: Need to create SYS.IND_ONLINE$ table in order to (re)build index
-
Cause: Alter index Build/Rebuild online require existing of SYS.IND_ONLINE$ table.
- ORA-08121: Number of indexes need to be maintained offline exceeds limit for DML
-
Cause: Too many indexes needed to be maintained. The limit is 2^16 indexes for each DML statement
- ORA-08122: Online (re)build of index rolled back due to DML conflict
-
Cause: The online (re)build journal is inconsistent with ongoing DML and cannot be used successfully to complete the online index (re)build.
- ORA-08175: discrete transaction restriction violated (string)
-
Cause: An attempt was made to perform an action that is not currently supported in a discrete 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.
- 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.
- ORA-08178: illegal SERIALIZABLE clause specified for user INTERNAL
-
Cause: Serializable mode is not supported for user INTERNAL.
- 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.
- ORA-08180: no snapshot found based on specified time
-
Cause: Could not match the time to an SCN from the mapping table.
- ORA-08181: specified number is not a valid system change number
-
Cause: supplied scn was beyond the bounds of a valid scn.
- ORA-08182: operation not supported while in Flashback mode
-
Cause: user tried to do dml or ddl while in Flashback mode
- ORA-08183: Flashback cannot be enabled in the middle of a transaction
-
Cause: user tried to do Flashback in the middle of a transaction
- ORA-08184: attempting to re-enable Flashback while in Flashback mode
-
Cause: as stated above
- ORA-08185: Flashback not supported for user SYS
-
Cause: user logged on as SYS
- ORA-08186: invalid timestamp specified
-
Cause: as stated above
- ORA-08187: snapshot expression not allowed here
-
Cause: A snapshot expression using AS OF was specified when not allowed.
- 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.
- 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
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- ORA-08205: ora_addr: $ORACLE_SID not set in environment
-
Cause: The environment variable ORACLE_SID is not set.
- ORA-08206: ora_addr: cannot translate address file name
-
Cause: Cannot translate $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf.
- ORA-08207: ora_addr: cannot open address file
-
Cause: The address file could not be opened.
- ORA-08208: ora_addr: cannot read from address file
-
Cause: The address file could not be read.
- ORA-08209: scngrs: SCN not yet initialized
-
Cause: The System Commit Number has not yet been initialized.
- ORA-08210: Requested I/O error
-
Cause: Oracle requested that an I/O error be returned for this operation.
- ORA-08230: smscre: failed to allocate SGA
-
Cause: The n_core system call failed, maybe due to insufficient memory.
- 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.
- ORA-08232: smsdes: cannot detach from SGA
-
Cause: Probably, the listener process has died.
- ORA-08233: smsdes: cannot unmap SGA
-
Cause: The n_core system call failed while detaching from the SGA.
- ORA-08234: smsget: cannot get instance listener address
-
Cause: The instance listener address cannot be read from the sgadef file.
- 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.
- ORA-08236: smsget: cannot share subcube with listener
-
Cause: The n_share call failed, probably because the listener has died.
- ORA-08237: smsget: SGA region not yet created
-
Cause: Attempting to attach to an SGA which has not yet been created.
- ORA-08238: smsfre: cannot detach from SGA
-
Cause: The n_core system call failed while detaching from the SGA.
- ORA-08243: recursive audit operation attempted
-
Cause: A recursive operation requiring audit was attempted in the middle of an auditing operation or an audit table movement operation. The most likely reason is that space management operations needed to free up space in the audit tablespace or a SQL operation on dictionary tables directly or using database triggers which produced more audit records.
- ORA-08260: ora_addr: cannot open nameserver
-
Cause: A process could not connect to the nameserver.
- ORA-08261: ora_addr: cannot find name in nameserver
-
Cause: The listener nameserver entry for an instance could not be found.
- ORA-08263: ora_addr: cannot free listener address
-
Cause: The listener nameserver entry could not be freed
- ORA-08264: ora_addr: cannot close nameserver
-
Cause: The connection to the nameserver could not be closed.
- ORA-08265: create_ora_addr: cannot open nameserver
-
Cause: A process could not connect to the nameserver.
- ORA-08266: create_ora_addr: cannot register name in nameserver
-
Cause: The listener's addressing information could not be registered.
- ORA-08267: destroy_ora_addr: cannot close nameserver
-
Cause: The connection to the nameserver could not be closed.
- ORA-08268: create_ora_addr: cannot close nameserver
-
Cause: The connection to the nameserver could not be closed.
- ORA-08269: destroy_ora_addr: cannot destroy name
-
Cause: The listener's addressing information could not be removed.
- ORA-08270: sksachk: Illegal archival control string
-
Cause: Archive files cannot be created with the given archival control string.
- ORA-08271: sksabln: Buffer size not large enough for archive control string
-
Cause: The given archival control string expands into too many characters.
- ORA-08274: Out of memory for environment variable
-
Cause: There is insufficient memory to return the requested value
- ORA-08275: Environment variable unset
-
Cause: The requested environment variable is not set
- ORA-08276: No room in nameserver for pid
-
Cause: There is no room to record the pid for a background process
- ORA-08277: Cannot set environment variable
-
Cause: There is insufficient memory to expand the environment.
- ORA-08278: Cannot get CPU statistics
-
Cause: Could not retrieve CPU times because n_stat failed.
- ORA-08308: sllfop: Cannot open file
-
Cause: Oracle could not open a file.
- ORA-08309: sllfop: Cannot fstat file
-
Cause: Oracle could not obtain information about an open file.
- ORA-08310: sllfop: Bad value for recsize
-
Cause: An illegal value for the record size was specified.
- ORA-08311: sllfop: bad value for maxrecsize
-
Cause: An illegal value for the maximum record size was specified.
- ORA-08312: sllfop: unrecognized processing option
-
Cause: An unrecognized processing option was specified.
- ORA-08313: sllfop: could not allocate buffers
-
Cause: Memory for the load buffers could not be allocated.
- ORA-08314: sllfcf: Error closing file
-
Cause: An error occurred trying to close a file.
- ORA-08315: sllfrb: Error reading file
-
Cause: An error occurred trying to read from a file.
- ORA-08316: sllfsk: Error seeking in file.
-
Cause: The lseek system call returned an error.
- ORA-08317: sllfsk: Error seeking in file.
-
Cause: The lseek system call returned an error.
- ORA-08318: sllfsk: Error reading file
-
Cause: An error occurred trying to read from a file.
- ORA-08319: sllfsk: Error reading file
-
Cause: An error occurred trying to read from a file.
- ORA-08320: scnget: Call to scnget before scnset or scnfnd.
-
Cause: An internal error
- ORA-08321: scnmin: NOT IMPLEMENTED YET
-
Cause: An internal error
- ORA-08322: scnmin: open/convert of bias lock failed
-
Cause: A call to the lkmgr failed to open and convert the bias lock
- ORA-08323: scnmin: close of bias lock failed
-
Cause: A call to the lkmgr failed to close the bias lock
- ORA-08330: Printing not supported
-
Cause: An attempt was made to automatically spool a file to the printer
- ORA-08331: Wait operation timed out
-
Cause: Oracle timed out waiting for an event
- ORA-08332: rollback segment #string specified not available
-
Cause: (same as 1545)
- ORA-08340: This command not allowed on nCUBE, only one thread is ever used.
-
Cause: An illegal command was executed for the nCUBE platform.
- 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.
- ORA-08342: sropen: failed to open a redo server connection
-
Cause: An error occurred trying to connect to the redo server.
- ORA-08343: srclose: failed to close a redo server connection
-
Cause: An error occurred trying to close the redo server connection.
- ORA-08344: srapp: failed to send redo data to the redo server
-
Cause: An error occurred trying to send redo to the redo server.
- ORA-08401: invalid compiler name: string
-
Cause: An invalid compiler name compname was passed to a UTL_PG conversion routine.
- ORA-08402: error executing PL/SQL code coverage
-
Cause: An error occurred during execution of a PL/SQL code coverage procedure.
- 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.
- 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.
- 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
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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
- 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
- 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
- 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
- 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
- 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
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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
- 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.
- 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
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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.
- 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
- ORA-08469: must use the SIGN IS SEPARATE clause in mask options
-
Cause: A signed numeric entry with DISPLAY usage was converted using a non-defaulted character set and its PICTURE character-string contains an S. In these circumstances, a SIGN IS SEPARATE clause must be specified in the mask options.
- 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.
- 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.
- ORA-09200: sfccf: error creating file
-
Cause: Could be out of disk space
- ORA-09201: sfcopy: error copying file
-
Cause: Block sizes may not match
- ORA-09202: sfifi: error identifying file
-
Cause: db_block_size specified in init.ora could be incorrect
- ORA-09203: sfofi: error opening file
-
Cause: File attributes may have changed
- ORA-09204: sfotf: error opening temporary file
-
Cause: Incorrect path may have been specified for the file
- ORA-09205: sfqio: error reading or writing to disk
-
Cause: File may have been truncated or corrupted
- ORA-09206: sfrfb: error reading from file
-
Cause: File may have been truncated or corrupted
- ORA-09207: sfsrd: error reading from file
-
Cause: File may have been truncated or corrupted
- ORA-09208: sftcls: error closing file
-
Cause: File may have been corrupted
- ORA-09209: sftget: error reading from file
-
Cause: File may have been truncated or corrupted
- ORA-09210: sftopn: error opening file
-
Cause: Incorrect path may have been specified for the file
- ORA-09211: sfwfb: error writing to file
-
Cause: File may have been truncated or corrupted
- ORA-09212: sfwfbmt: error writing to file
-
Cause: File may have been truncated or corrupted
- ORA-09213: slgfn: error fabricating file name
-
Cause: Filename may be too long
- ORA-09214: sfdone: I/O error detected
-
Cause: File may have been truncated or corrupted
- ORA-09215: sfqio: error detected in IOCompletionRoutine
-
Cause: File may have been truncated or corrupted
- ORA-09216: sdnfy: bad value 'string' for parameter string
-
Cause: The directory specified as the value for the stated parameter could not be used.
- ORA-09217: sfsfs: failed to resize file
-
Cause: Could be out of disk space
- ORA-09218: sfrfs: failed to refresh file size
-
Cause: File may be corrupted or truncated
- ORA-09240: smpalo: error allocating PGA memory
-
Cause: Could be out of memory
- ORA-09241: smsalo: error allocating SGA memory
-
Cause: Could be out of memory
- ORA-09242: smscre: error creating SGA
-
- ORA-09243: smsget: error attaching to SGA
-
Cause: SGA may not have been created (database not started)
- ORA-09244: smprset: error setting memory protections
-
- ORA-09245: smcstk: error switching stacks
-
- ORA-09246: sfsmap: unable to map SGA
-
- ORA-09247: smsdes: error destroying the SGA
-
- ORA-09260: sigpidu: error obtaining process id
-
Cause: May be out of resources
- ORA-09261: spdcr: error creating detached (background) process
-
Cause: Could be out of resources
- ORA-09262: spdde: error terminating detached (background) process
-
Cause: Could be out of resources
- ORA-09263: spini: error initializing process
-
Cause: Could be out of memory
- ORA-09264: sptpa: error flagging process
-
Cause: Could be out of resources
- ORA-09265: spwat: error temporarily suspending process
-
Cause: Could be out of resources
- ORA-09266: spawn: error starting an Oracle process
-
Cause: Could be out memory
- ORA-09270: szalloc: error allocating memory for security
-
Cause: Could be out of memory
- ORA-09271: szlon: error verifying user name
-
Cause: Username may be too long
- ORA-09272: remote os logon is not allowed
-
Cause: Remote os login attempted when not allowed.
- ORA-09273: szrfc: error verifying role name
-
Cause: An OS error was returned when verifying the role name.
- ORA-09274: szrfc: insufficient role name buffer space
-
Cause: An OS role name was too long.
- ORA-09275: CONNECT INTERNAL is not a valid DBA connection
-
Cause: CONNECT INTERNAL is no longer supported for DBA connections.
- ORA-09276: All bequeath database links must be loopback database links
-
Cause: A non-loopback bequeath connect string was supplied for a database link.
- ORA-09280: sllfcf: error closing file
-
Cause: File may be corrupted
- ORA-09281: sllfop: error opening file
-
Cause: Possibly incorrect path specified to the file
- ORA-09282: sllfrb: error reading records
-
Cause: File could be corrupted
- ORA-09283: sllfsk: error skipping records
-
Cause: File could be corrupted
- ORA-09284: sllfop: cannot allocate read buffer
-
Cause: malloc() system call returned an error. The system might have run out of heap space
- ORA-09285: sllfop: unrecognizable processing option, incorrect format
-
Cause: Processing option passed is of incorrect format
- ORA-09290: sksaalo: error allocating memory for archival
-
Cause: Could be out of memory
- ORA-09291: sksachk: invalid device specified for archive destination
-
Cause: Unable to access directory
- ORA-09292: sksabln: unable to build archive file name
-
Cause: Bad directory or format specified
- ORA-09293: sksasmo: unable to send message to console
-
Cause: An error was returned while attempting to send a message to the console operator
- ORA-09300: osncon: unable to connect, DPMI not available
-
Cause: Unable to detect the presence of DPMI
- ORA-09301: osncon: local kernel only supported in standard mode
-
Cause: An attempt was made to connect to S: while in enhanced mode
- ORA-09310: sclgt: error freeing latch
-
Cause: Internal error
- ORA-09311: slsleep: error temporarily suspending process
-
Cause: May be out of resources
- ORA-09312: slspool: error spooling file to printer
-
Cause: Could be out of resources
- ORA-09313: slsprom: error prompting user
-
Cause: May be out of resources
- ORA-09314: sltln: error translating logical name
-
Cause: Internal buffer may have overflowed
- ORA-09315: sql2tt: two-task error translating ORACLE_EXECUTABLE
-
Cause: Internal error
- ORA-09316: szrpc: unable to verify password for role
-
Cause: OS roles may not be supported for this platform
- ORA-09317: szprv: insufficient privileges
-
Cause: The password specified is invalid
- ORA-09318: slkhst: unable to host out to operating system
-
Cause: There might not be enough memory for the command or hosting out may not be supported on this platform
- ORA-09319: slgtd: unable to obtain the current date and time
-
Cause: The system time might be set incorrectly
- ORA-09320: szrfc: unable to obtain the list of valid OS roles
-
Cause: OS roles may not be supported on this platform
- ORA-09321: slzdtb: unable to convert zoned decimal to binary
-
Cause: internal error
- ORA-09322: slpdtb: unable to convert packed decimal to binary
-
Cause: internal error
- ORA-09330: Session terminated internally by Oracle or by an Oracle DBA
-
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.
- ORA-09340: Specified ORACLE_SID is either invalid or too long
-
Cause: ORACLE_SID must be at the most 4 alphanumeric characters.
- ORA-09341: scumnt: unable to mount database
-
Cause: Another instance is currently mounting the database
- ORA-09342: Detached process terminated by Oracle during shutdown abort
-
Cause: The user performed a shutdown abort.
- ORA-09344: spsig: error signalling thread
-
Cause: This function may not be implemented.
- ORA-09350: Windows 32-bit Two-Task driver unable to allocate context area
-
Cause: See OSD error accompanying this message
- ORA-09351: Windows 32-bit Two-Task driver unable to allocate shared memory
-
Cause: See OSD error accompanying this message
- ORA-09352: Windows 32-bit Two-Task driver unable to spawn new ORACLE task
-
Cause: See OSD error accompanying this message
- ORA-09353: Windows 32-bit Two-Task driver unable to open event semaphore
-
Cause: See OSD error accompanying this message
- ORA-09354: Windows 32-bit Two-Task driver: ORACLE task unexpectedly died
-
Cause: See OSD error accompanying this message
- ORA-09360: Windows 3.1 Two-Task driver unable to allocate context area
-
Cause: See OSD error accompanying this message
- ORA-09361: Windows 3.1 Two-Task driver unable to lock context area
-
Cause: See OSD error accompanying this message
- ORA-09362: Windows 3.1 Two-Task driver unable to deallocate context area
-
Cause: See OSD error accompanying this message
- ORA-09363: Windows 3.1 Two-Task driver invalid context area
-
Cause: See OSD error accompanying this message
- ORA-09364: Windows 3.1 Two-Task driver unable to create hidden window
-
Cause: See OSD error accompanying this message
- ORA-09365: Windows 3.1 Two-Task driver unable to destroy hidden window
-
Cause: See OSD error accompanying this message
- ORA-09366: Windows 3.1 Two-Task driver unable to allocate shared memory
-
Cause: See OSD error accompanying this message
- ORA-09367: Windows 3.1 Two-Task driver unable to deallocate shared memory
-
Cause: See OSD error accompanying this message
- ORA-09368: Windows 3.1 Two-Task driver unable to spawn ORACLE
-
Cause: See OSD error accompanying this message
- ORA-09369: Windows 3.1 Two-Task driver bad instance handle
-
Cause: See OSD error accompanying this message
- ORA-09370: Windows 3.1 Two-Task driver ORACLE task timed out
-
Cause: See OSD error accompanying this message
- ORA-09700: sclin: maximum number of latches exceeded
-
Cause: ORACLE wants to use more latches then available.
- ORA-09701: scnfy: maximum number of processes exceeded
-
Cause: PROCESSES INIT.ORA parameter exceeded.
- ORA-09702: sem_acquire: cannot acquire latch semaphore
-
Cause: The semaphore used for accessing latches could not be seized
- ORA-09703: sem_release: cannot release latch semaphore
-
Cause: The semaphore used for accessing latches could not be released
- ORA-09704: sstascre: ftok error in creating test and set pages.
-
Cause: the ftok() library call failed in sstastcre().
- ORA-09705: spcre: cannot initialize latch semaphore
-
Cause: The semaphore used for accessing latches could not be initialized
- ORA-09706: slsget: get_process_stats error.
-
Cause: get_process_stats system call returned an error. Possible OS error.
- ORA-09708: soacon: failed to bind socket to port.
-
Cause: The bind system call failed on the socket.
- ORA-09709: soacon: failed to accept a connection.
-
Cause: The accept system call failed on the socket.
- ORA-09710: soarcv: buffer overflow.
-
Cause: The internal buffer is not big enough to hold the message read.
- ORA-09711: orasrv: archmon already connected.
-
Cause: An existing connection has already been made from archmon to orasrv.
- ORA-09712: orasrv: log archiver already connected.
-
Cause: An existing connection has already been made from log archiver to orasrv.
- ORA-09714: Two Task interface: cannot obtain puname
-
Cause: The TXIPC driver cannot obtain the name of the PU. (Possible OS error)
- ORA-09715: orasrv: cannot obtain puname
-
Cause: Orasrv cannot obtain the name of the PU. (Possible OS error)
- ORA-09716: kslcll: Unable to fix in-flux lamport latch.
-
Cause: One Oracle process died while still holding a lamport latch.
- ORA-09717: osnsui: maximum number of user interrupt handlers exceeded.
-
Cause: The internal limit on the number of user interrupt handlers has been exceeded.
- ORA-09718: osnsui: cannot set up user interrupt handler.
-
Cause: Malloc() failed to allocate space to hold user interrupt handler.
- ORA-09719: osncui: invalid handle.
-
Cause: The handle passed to osncui is out of the valid range.
- ORA-09740: slsget: cannot get virtual memory region statistics.
-
Cause: The vm_region system call failed to get virual memory region statistics.
- ORA-09741: spwat: error waiting for a post.
-
Cause: Msg_receive system call returned an error. Internal error.
- ORA-09742: sppst: error during a post.
-
Cause: Msg_send system call returned an error. Internal error.
- ORA-09743: smscre: could not attach shared memory.
-
Cause: The mmap or write system call returned an error. Internal error.
- ORA-09744: smsget: mmap returned an error.
-
Cause: The mmap system call returned an error. Internal error.
- ORA-09745: smscre: vm_allocate error, unable to create shared memory.
-
Cause: Error in system call vm_allocate. Failed to create SGA as a single shared memory segment.
- ORA-09746: smscre: shared memory attach address incorrect.
-
Cause: The vm_allocate system call attached the SGA at an incorrect location.
- ORA-09747: pw_detachPorts: server call pws_detach failed.
-
Cause: The call pws_detach to (Oracle helper) failed.
- ORA-09748: pws_look_up: fork failed
-
Cause: The pws_look_up call could not fork the (Oracle helper) process.
- ORA-09749: pws_look_up: port lookup failure
-
Cause: The pws_look_up could not find a port to (Oracle helper).
- ORA-09750: pw_attachPorts: port_rename failed.
-
Cause: The port_rename system call failed; possible internal error.
- ORA-09751: pw_attachPorts: server call pws_attach failed.
-
Cause: The call pws_attach to (Oracle helper) failed.
- ORA-09752: pw_attachPorts: port_allocate failed.
-
Cause: The port_allocate system call failed; possible resource exhaustion.
- ORA-09753: spwat: invalid process number.
-
Cause: Function was passed an invalid oracle process id.
- ORA-09754: sppst: invalid process number passed to sppst.
-
Cause: Function was passed an invalid oracle process id.
- ORA-09755: osngpn: port allocation failure.
-
Cause: The port_allocate system call failed.
- ORA-09756: osnpns: no port in the name server.
-
Cause: osnpns could not find the given named port in the name server.
- ORA-09757: osnipn: port allocation failure.
-
Cause: The port_allocate system call failed.
- ORA-09758: osnipn: could not check port in name server.
-
Cause: The netname_check_in call failed.
- ORA-09759: osnsbt: bad message received.
-
Cause: The msg_receive system call failed, or received a bad message.
- ORA-09760: osnpui: cannot send break message
-
Cause: The Pipe driver could not send a break message to the ORACLE shadow process break thread.
- ORA-09761: pw_destroyPorts: server call pws_stop_instance failed.
-
Cause: The call pws_stop_instance to (Oracle helper) failed.
- ORA-09762: sNeXT_instanceName: translation error.
-
Cause: A failure was detected while translating the value of ORACLE_SID.
- ORA-09763: osnmpx: send/receive error exchanging Mach ports.
-
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.
- ORA-09764: osnmop: access error on oracle executable
-
Cause: The Mach driver could not access the oracle executable.
- ORA-09765: osnmop: fork failed
-
Cause: The Mach driver could not fork the oracle shadow process.
- ORA-09766: osnmop: buffer allocation failure.
-
Cause: The Mach driver failed to allocate enough vm space for its I/O buffers.
- ORA-09767: osnmfs: bad return code from msg_send.
-
Cause: The msg_send system call failed while flushing the Mach driver's send buffer.
- 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.
- ORA-09769: osnmbr: cannot send break message
-
Cause: The Mach driver could not send a break message to the ORACLE shadow process break thread.
- ORA-09770: pws_look_up: translation failure.
-
Cause: The pws_look_up routine failed to translate the name of the (Oracle helper) executable.
- ORA-09771: osnmwrtbrkmsg: bad return code from msg_send.
-
Cause: The msg_send sytem call failed while sending a Mach driver break.
- ORA-09772: osnpmetbrkmsg: message from host had incorrect message type
-
Cause: The Mach driver received a message having an unrecognizable message type.
- ORA-09773: osnmgetdatmsg: message from host had incorrect message type
-
Cause: The Mach driver received a message having an unrecognizable message type.
- ORA-09774: osnmui: cannot send break message
-
Cause: The Mach driver could not send a break message to the ORACLE shadow process break thread.
- ORA-09775: osnmrs: reset protocol error
-
Cause: The Mach two-task driver could not reset the connection.
- ORA-09776: pws_look_up: access error on (Oracle helper) executable
-
Cause: The pws_look_up call could not access the (Oracle helper) executable.
- ORA-09777: osnpbr: cannot send break message
-
Cause: The pipe driver could not send a break message to the ORACLE shadow process break thread.
- ORA-09778: snynfyport: failure allocating the notify port.
-
Cause: The routine failed to allocate or set the task's notify port.
- ORA-09779: snyGetPort: failure to allocate a port.
-
Cause: The port_allocate system call failed; system resources might be exhausted.
- ORA-09786: sllfop: open error, unable to open file.
-
Cause: Open system call returned an error.
- ORA-09787: sllfop: unrecognizable processing option, incorrect format.
-
Cause: Processing option passed is of incorrect format.
- ORA-09788: sllfrb: unable to read file.
-
Cause: Read system call returned an error.
- ORA-09789: sllfsk: unable to read file.
-
Cause: Read system call returned an error.
- ORA-09790: sllfcf: unable to close file.
-
Cause: Close system call returned an error.
- ORA-09791: slembdf: translation error, unable to translate error file name.
-
Cause: Additional information indicates error returned from sltln.
- ORA-09792: sllfop: cannot allocate read buffer.
-
Cause: Malloc system call returned an error. The system might have run out of heap space.
- 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.
- 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.
- ORA-09795: szrbuild: malloc of role structure failed.
-
Cause: The allocation of memory for an internal structure used to hold a role descriptor failed.
- 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.
- ORA-09797: Failed to get O/S MAC privileges.
-
Cause: The operating system would not allow the retrieval of this process' privileges.
- ORA-09798: Label comparison failed.
-
Cause: The comparison of two binary labels failed.
- ORA-09799: File label retrieval failed.
-
Cause: ORACLE was unable to get a label attached to a file.
- ORA-09800: Process sensitivity label retrieval failed.
-
Cause: ORACLE was unable to get the sensitivity label for a process.
- 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.
- ORA-09802: Conversion of binary label to string failed.
-
Cause: ORACLE was unable to convert a binary label to a string.
- 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.
- ORA-09804: Class conversion from binary to ORACLE failed.
-
Cause: ORACLE was unable to convert a class component from binary format to ORACLE format.
- ORA-09805: conversion of category number to string failed.
-
Cause: ORACLE was unable to translate a category number to its corresponding string representation failed.
- ORA-09806: Allocation of label string buffer failed.
-
Cause: a temporary buffer used to hold a label could not be allocated.
- 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.
- ORA-09808: Could not obtain user clearance.
-
Cause: ORACLE was unable to get a user's clearance level.
- 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.
- 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.
- ORA-09811: Unable to initialize package.
-
Cause: ORACLE was unable to initialize the library used to obtain security information.
- 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.
- ORA-09813: Unable to get directory status
-
Cause: ORACLE was unable to determine if a directory is multilevel.
- ORA-09814: Unable to expand file name
-
Cause: ORACLE was unable to expand the name of a file that resides in multilevel directory.
- ORA-09815: File name buffer overflow
-
Cause: The buffer that ORACLE uses to hold the expanded name of a too small.
- ORA-09816: Unable to set effective privileges
-
- ORA-09817: Write to audit file failed.
-
Cause: ORACLE was unable to write an entry to the file used as the audit trail.
- 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.
- ORA-09819: Number exceeds maximum legal value
-
Cause: the number specified for a component was greater than the maximum value allowed for that component.
- 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.
- ORA-09821: Numeric label is not valid
-
Cause: A label specified in ORACLE numeric format was found not to be valid.
- ORA-09822: Translation of audit file name failed.
-
Cause: Oracle was unable to translate the value of the AUDIT_FILE_DEST initialization parameter.
- 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.
- 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.
- ORA-09825: Unable to disable allowmacaccess privilege.
-
Cause: ORACLE was not able to turn off the allowmacaccess privilege after doing a label comparison.
- ORA-09826: SCLIN: cannot initialize atomic latch.
-
Cause: System call atomic_op() return error.
- ORA-09827: SCLGT: atomic latch return unknown error.
-
Cause: System call atomic_op() return unexpected error.
- ORA-09828: SCLFR: atomic latch return error.
-
Cause: System call atomic_op() return unexpected error.
- 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.
- ORA-09830: snyAddPort: failed to perform a remote procedure call.
-
Cause: The msg_rpc system call returned an error.
- 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.
- ORA-09832: infoCallback: bad message format.
-
Cause: The routine received an incorrectly formatted request.
- ORA-09833: addCallback: bad message format.
-
Cause: The routine received an incorrectly formatted request.
- ORA-09834: snyGetPortSet: failed to collect info on a port.
-
Cause: The port_status system called failed.
- 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.
- ORA-09836: addCallback: could not add a port to the callback set.
-
Cause: The port_set_add system called failed.
- ORA-09837: addCallback: could not add allocate a callback link.
-
Cause: The malloc library call failed to allocate space for a callback link.
- ORA-09838: removeCallback: failure removing the callback port.
-
Cause: The port port_set_remove system call failed.
- 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.
- ORA-09840: soacon: Name translation failure.
-
Cause: sltln() could not translate the named pipe ?/dbs/mon2arch_@.
- ORA-09841: soacon: Name translation failure.
-
Cause: sltln() could not translate the named pipe ?/dbs/arch2mon_@.
- ORA-09842: soacon: Archmon unable to create named pipe.
-
Cause: mknod() failed to create named pipe ?/dbs/mon2arch_@.
- ORA-09843: soacon: Archmon unable to create named pipe.
-
Cause: mknod() failed to create named pipe ?/dbs/arch2mon_@.
- ORA-09844: soacon: Archmon unable to open named pipe.
-
Cause: open() failed to open named pipe ?/dbs/mon2arch_@.
- ORA-09845: soacon: Archmon unable to open named pipe.
-
Cause: open() failed to open named pipe ?/dbs/arch2mon_@.
- ORA-09846: soacon: ARCH unable to open named pipe.
-
Cause: open() failed to open named pipe ?/dbs/mon2arch_@.
- ORA-09847: soacon: ARCH unable to open named pipe.
-
Cause: open() failed to open named pipe ?/dbs/arch2mon_@.
- ORA-09848: soawrt: Unable to write to named pipe.
-
- ORA-09849: soarcv: Unable to read from named pipe.
-
- ORA-09850: soacon: Archmon unable to lock named pipe.
-
Cause: fcntl() failed to set write lock on named pipe ?/dbs/arch2mon_@.
- ORA-09851: soacon: Archmon unable to lock named pipe.
-
Cause: fcntl() failed to set read lock on named pipe ?/dbs/mon2arch_@.
- ORA-09853: snyRemovePort: bad return code from request.
-
Cause: The request to remove a port from the callback set returned a failure code.
- 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.
- ORA-09855: removeCallback: bad message format.
-
Cause: The routine received an incorrectly formatted request.
- ORA-09856: smpalo: vm_allocate error while allocating pga.
-
Cause: The vm_allocate system call returned an error.
- ORA-09857: smprset: vm_protect error while protecting pga.
-
Cause: The vm_protect system call returned an error.