77 ORA-09870 to ORA-12101
- ORA-09870: spini: failure initializing maximum number of open files.
-
Cause: ulimit system call returned an error.
- ORA-09871: TASDEF_NAME: translation error while expanding ?/dbs/tasdef@.dbf.
-
Cause: Failure of sltln(?/tasdef@.dbf) while creating test and set pages.
- ORA-09872: TASDEF_CREATE: create failure in creating ?/dbs/tasdef@.dbf.
-
Cause: Create() failed when trying to create the tasdef file.
- ORA-09873: TASDEF_OPEN: open error when opening tasdef@.dbf file.
-
Cause: Unable to open tasdef@.dbf file.
- ORA-09874: TASDEF_READ: read error, unable to read tasdef@.dbf file.
-
Cause: Read system call returned an error when attempting to read ?/dbs/tasdef@.dbf.
- ORA-09875: TASDEF_WRITE: write error when writing ?/dbs/tasdef@.dbf file.
-
Cause: Write call failed.
- ORA-09876: TASDEF_CLOSE: unable to close ?/dbs/tasdef@.dbf file.
-
Cause: Close system call returned an error.
- ORA-09877: sstascre: shmget error, unable to get a shared memory segment.
-
Cause: Error in shmget.
- ORA-09878: sstascre/sstasat: shmat error, unable to attach tas write page
-
Cause: Error in shmat.
- ORA-09879: sstascre/sstasat: shmat error, unable to attach tas read page
-
Cause: Error in shmat.
- ORA-09880: sstasfre/sstasdel: shmdt error, unable to detach tas write page
-
Cause: Error in shmdt.
- ORA-09881: sstasfre/sstasdel: shmdt error, unable to detach tas read page
-
Cause: Error in shmdt.
- ORA-09882: sstasfre/sstasdel: shmctl error, unable to remove tas shm page
-
Cause: Error in shmctl.
- ORA-09883: Two Task interface: oratab file does not exist
-
Cause: The oratab file does not exist.
- ORA-09884: Two Task interface: SID doens't match current PU
-
Cause: You are trying to start oracle on another PU than you configured oracle on or there is no entry for this SID in oratab file.
- ORA-09885: osnTXtt: cannot create TXIPC channel
-
Cause: The TXIPC driver failed to create pipes for two-task communications with the oracle shadow process.
- ORA-09886: osnTXtt: translation error while expanding txipc@.trc.
-
Cause: Failure of sltln(txipc@.trc) while creating debug channel.
- ORA-09887: osnTXtt: Failed to create/open debug channel.
-
- ORA-09888: osnTXtt: txipc channel creation failed
-
Cause: The txipc driver failed to create channels for two-task communications with the oracle shadow process.
- ORA-09889: osnTXtt: access error on oracle executable
-
Cause: The txipc driver could not access the oracle executable.
- ORA-09890: osnTXtt: malloc failed
-
Cause: The txipx driver failed to allocate enough heap space for its context area buffers.
- ORA-09908: slkmnm: gethostname returned error code.
-
Cause: The system call gethostname returned an error.
- ORA-09909: Malloc of scratch buffer failed.
-
Cause: Memory needed for a temporary buffer could not be allocated. The additional information field contains the number of bytes that ORACLE attempted to allocate.
- ORA-09910: Unable to find ORACLE password file entry for user.
-
Cause: No entry exists for the user in the ORACLE password file.
- ORA-09911: Incorrect user password.
-
Cause: The password entered by the user was incorrect.
- ORA-09912: Malloc of name buffer(s) failed.
-
Cause: ORACLE was unable to allocate memory for one or both of the buffers that are used to hold the name of DBA and the operator users.
- ORA-09913: Malloc of dummy name failed.
-
Cause: ORACLE was unable to allocate memory for the user name that is to to be used in the encryption of the user's password.
- ORA-09914: Unable to open the ORACLE password file.
-
Cause: ORACLE could not open the password file for reading.
- ORA-09915: Password encryption failed.
-
Cause: ORACLE was unable to encrypt a password.
- ORA-09916: Required password was not specified.
-
Cause: A user attempted to connect as "internal," but did not specify a password.
- ORA-09918: Unable to get user privileges from SQL*Net
-
Cause: ORACLE was unable to retrieve the user's privilege set from the SQL*Net connection.
- ORA-09919: Unable to set label of dedicated server
-
Cause: ORACLE was unable to set the label of the dedicated to server to the required value.
- ORA-09920: Unable to get sensitivity label from connection
-
Cause: ORACLE was unable to retrieve the user's sensitivity label from the SQL*Net connection.
- ORA-09921: Unable to get information label from connection
-
Cause: ORACLE was unable to retrieve the user's information label from the SQL*Net connection.
- ORA-09922: Can't spawn process - background log directory not created properly
-
Cause: ORACLE was unable to spawn a background process because the directory that will hold trace files of the background processes was not created properly.
- ORA-09923: Can't spawn process - user log directory not created properly
-
Cause: ORACLE was unable to spawn a background process because the directory that holds the trace files of the dedicated server processes was not created properly.
- ORA-09924: Can't spawn process - core dump directory not created properly
-
Cause: ORACLE was unable to spawn a background process because the directory that holds the core dumps produced by ORACLE processes in the event of exceptions was not created properly.
- ORA-09925: Unable to create audit trail file
-
Cause: ORACLE was not able to create the file being used to hold audit trail records.
- ORA-09926: Unable to set effective privilege set of the server
-
Cause: A dedicated server was unable to set it's own privilege set.
- ORA-09927: Unable to set label of server
-
Cause: ORACLE was not able to set the label of a server to a new value.
- ORA-09928: Unable to restore the label of server
-
Cause: ORACLE was unable to restore the label of the server to the value that it had before raising it to database high.
- ORA-09929: GLB of two labels is invalid
-
Cause: The result of a greatest lower bound operation on two labels was not valid.
- ORA-09930: LUB of two labels is invalid
-
Cause: The result of a least upper bound operation on two labels was not valid.
- ORA-09931: Unable to open ORACLE password file for reading
-
Cause: An attempt to open a password file for reading failed.
- ORA-09932: Close of ORACLE password file failed.
-
Cause: An attempt to close a password file failed.
- ORA-09933: Deletion of old password file failed.
-
Cause: The removal of the old password file failed.
- ORA-09934: Link of current password file to old failed.
-
Cause: ORACLE was unable to create a link so that the old password file could be saved.
- ORA-09935: Unlink of current password file failed.
-
Cause: ORACLE was unable to complete the saving of the current password file.
- ORA-09936: Open of ORACLE password file for write failed.
-
Cause: ORACLE was unable to create a password file.
- ORA-09937: Chmod of ORACLE password file failed.
-
Cause: ORACLE was unable to change a password file to be readonly.
- ORA-09938: Save of signal handlers failed.
-
Cause: ORACLE was unable to save the previous values of selected signal handlers.
- ORA-09939: Restoration of signal handlers failed.
-
Cause: ORACLE was unable to restore the previous values of selected signal handlers.
- ORA-09940: ORACLE password file header is corrupt
-
Cause: The header of one of the password files was not in the format that ORACLE expected.
- ORA-09941: Version of orapasswd or installer is older than file.
-
Cause: The version of orapasswd or installer that is being run is older than that of the ORACLE password file. Since the file version is only changed when the format is changed, this error means that the executable is using a different format than that with which the file was created.
- ORA-09942: Write of ORACLE password file header failed.
-
Cause: The attempt to write out the header of the ORACLE password file failed.
- ORA-09943: Allocation of memory for password list component failed.
-
Cause: When it is building a list of password file entries, ORACLE allocates memory for various components. One of the allocations failed.
- ORA-09944: Password entry is corrupt.
-
Cause: An entry in an ORACLE password file was not in the format that ORACLE expected.
- ORA-09945: Unable to initialize the audit trail file
-
Cause: ORACLE unable to write header information to the file being used as the audit trail.
- ORA-09946: File name too long for buffer
-
Cause: The buffer that was to be used to hold a file name was determined to be too short for the generated name. This will happen if the translated name for either a trace file or an audit file is longer than the maximum allowed, which on many ports is 256 characters.
- ORA-09947: Unable to allocate connection attributes structure
-
Cause: ORACLE was not able to allocate the memory needed to hold the attributes of the SQL*Net connection. The "Additional Information" field holds the number of bytes that ORACLE attempted to allocate.
- ORA-09948: Process information label retrieval failed.
-
Cause: ORACLE was unable to get the information label for a process.
- ORA-09949: Unable to get client operating system privileges
-
Cause: ORACLE was unable to get the operating system privileges for the client process.
- ORA-09950: Unable to get server operating system privileges
-
Cause: ORACLE was unable to get its privileges from the operating system.
- ORA-09951: Unable to create file
-
Cause: ORACLE was unable to create a file.
- ORA-09952: scgcmn: lk_open_convert unexpected return: open failed
-
Cause: The distributed lock manager returned an unexpected value
- ORA-09953: scggc: unexpected return of a lock convert
-
Cause: The distributed lock manager returned an unexpected value
- ORA-09954: scgcc: unexpected return status to callback of lock close
-
Cause: The distributed lock manager returned an unexpected value
- ORA-09955: scgcan: unexpected return status when canceling a lock
-
Cause: DLM system service x returned an unexpected value
- ORA-09956: scgcm: unexpected lock status condition
-
Cause: A global locking system service returned an unexpected value.
- ORA-09957: Unable to send termination request to IMON
-
Cause: The attempt to send a termination signal to IMON failed.
- ORA-09958: IMON: two processes with the same ORACLE pid are active
-
Cause: The IMON process was unable to add an entry for a server process because another active process occupies the slot.
- ORA-09959: IMON: deletion of a process failed.
-
Cause: The IMON process was unable to delete a server process from its process ID array because no entry for the process could be found.
- ORA-09960: Unable to establish signal handler for termination signal
-
Cause: ORACLE was unable to set up a handler for the signal used to notify it that the instance was shutting down.
- ORA-09961: Unable to restore termination signal handler
-
Cause: ORACLE failed to set the handler for the termination signal to its previous value.
- ORA-09962: lk_group_create error in scggrc
-
- ORA-09963: lk_group_attach error in scggra
-
- ORA-09964: lk_group_detach error in scggrd
-
- ORA-09966: falure in translation while expanding ?/dbs/lk for lock file
-
Cause: Oracle failed to translate ?/dbs/lk, when creating a file name for the database mount lock or the instance startup/shutdown lock.
- ORA-09967: unable to create or open lock file
-
Cause: Oracle failed, when making an open system call, inorder to acquire a file lock used by the database mount lock or the instance startup/shutdown lock.
- ORA-09968: unable to lock file
-
Cause: The system call for locking a file returned an error when trying to acquire a database mount lock or the instance startup/shutdown lock.
- ORA-09969: unable to close or remove lock file
-
Cause: The close system call or unlink system call returned an error.
- ORA-09974: skxfidini: Error Initializing SDI Channel
-
Cause: The process was unable to initialize the SDI channel properly.
- ORA-09975: kxfspini: Error Initializing SDI Process
-
Cause: The process was unable to attach to the SDI channel.
- ORA-09976: skxfqdini: Error Creating Port
-
Cause: The process was unable to create a communications endpoint.
- ORA-09977: skxfqhini: Error Connecting
-
Cause: The process was unable to connect to another endpoint.
- ORA-09978: skxfqhdel: Error Disconnecting from another endpoint.
-
Cause: The process was unable to disconnect cleanly from another endpoint.
- ORA-09979: skxfqhsnd: Error Sending a message to another endpoint
-
Cause: The process was unable to send a message to an existing endpoint.
- ORA-09980: skxfqdrcv: Error Receiving a message from another endpoint
-
Cause: The process encountered an error while trying to receive a message.
- ORA-09981: skxfqdreg: Error Adding a page to the SDI buffer pool
-
Cause: The process was unable to add a page to the SDI buffer pool.
- ORA-09982: skxfqddrg: Error Removing a page from the SDI buffer pool
-
Cause: The process was unable to remove a page to the SDI buffer pool.
- ORA-09983: skxfidsht: Error shutting down SDI channel
-
Cause: The process was unable shut down the SDI channel
- ORA-09984: SGA file $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf does not exist
-
Cause: file does not exist or is not accessible
- ORA-09985: SGA definition file could not be read
-
Cause: UNIX read() operation failed
- ORA-09986: wrong number of bytes read from SGA definition file
-
Cause: Struct skgmsdef size differs from no. of bytes read from SGA file
- ORA-09987: unable to attach to SGA in READ-ONLY mode
-
Cause: The instance is not up, or SGA segments are not read-accessible
- ORA-09988: error while detaching SGA
-
Cause: skgmsdef struct is corrupted and/or segment addresses are modified
- ORA-09989: attempt to use invalid skgmsdef struct pointer
-
Cause: Pointer to skgmsdef struct used without validating it
- ORA-10702: Application continuity debugging was not enabled
-
Cause: Enable application continuity debugging
- ORA-10887: An Oracle Active Data Guard license is required to open a pluggable database while standby recovery is applying changes.
-
Cause: An attempt was made to open a pluggable database without the Oracle Active Data Guard license.
- ORA-10889: minimum number of instances needed for redo apply unavailable
-
Cause: An attempt was made to start multi-instance redo apply with less than two instances in either a mounted or open state.
- ORA-10892: multi-instance redo apply encountered nonlogged operation
-
Cause: Multi-instance Redo Apply did not support applying invalidation redo. Invalidation redo is created as part of performing a nonlogged operation. Details of the first data block affected by the nonlogged operation can be found in the alert log.
- ORA-10979: trace flags for join index implementation
-
Cause: This is an informational message.
- ORA-12000: a materialized view log already exists on table 'string'
-
Cause: An attempt was made to create a materialized view log on a table that already had a materialized view log. Each master table had only one materialized view log.
- ORA-12001: cannot create log: table 'string' already has a trigger
-
Cause: Materialized view logs are filled by a trigger on the master table. That trigger cannot be created.
- ORA-12002: there is no materialized view log on table "string"."string"
-
Cause: There was no materialized view log on the master table.
- ORA-12003: materialized view or zonemap "string"."string" does not exist
-
Cause: The database object with the given owner and name was not found.
- ORA-12004: REFRESH FAST cannot be used for materialized view "string"."string"
-
Cause: The materialized view log does not exist or cannot be used. PCT refresh is also not enabled on the materialized view
- ORA-12005: may not schedule automatic refresh for times in the past
-
Cause: An attempt was made to schedule an automated materialized view refresh for a time in the past.
- ORA-12007: materialized view reuse parameters are inconsistent
-
Cause: The CREATE MATERIALIZED VIEW .. or CREATE MATERIALIZED VIEW LOG .. REUSE command was given inconsistent parameters immediately after the REUSE.
- ORA-12008: error in materialized view or zonemap refresh path
-
Cause: Table SNAP$_<mview_name> reads rows from the view MVIEW$_<mview_name>, which is a view on the master table (the master may be at a remote site). Any error in this path will cause this error at refresh time. For fast refreshes, the table <master_owner>.MLOG$_master is also referenced.
- ORA-12009: materialized views may not contain long columns
-
Cause: An attempt was made to create a materialized view with a long column.
- ORA-12010: cannot create materialized view log on table owned by SYS
-
Cause: An attempt was made to create a materialized view log on the table owned by SYS. CREATE MATERIALIZED VIEW LOG attempts to create a trigger on the table, but triggers can not be created on SYS tables.
- ORA-12011: execution of string jobs failed
-
Cause: An error was caught in dbms_ijob.run from one or more jobs which were due to be run.
- ORA-12012: error on auto execute of job string
-
Cause: An error was caught while doing an automatic execution of a job.
- ORA-12013: updatable materialized view must be simple enough and have a materialized view log on its master table to do fast refresh
-
Cause: The updatable materialized view query contained a JOIN, SUBQUERY, UNION, CONNECT BY, ORDER BY, or GROUP BY clause, or the master table did not have a materialized view log.
- ORA-12014: table 'string' does not contain a primary key constraint
-
Cause: The CREATE MATERIALIZED VIEW LOG command was issued with the WITH PRIMARY KEY option and the master table did not contain a primary key constraint or the constraint was disabled.
- ORA-12015: cannot create a fast refresh materialized view from a complex query
-
Cause: Neither ROWIDs and nor primary key constraints are supported for complex queries.
- ORA-12016: materialized view does not include all primary key columns
-
Cause: The query that instantiates the materialized view did not include all of the columns in the master's primary key constraint.
- ORA-12017: cannot alter primary key mview 'string' to a rowid mview
-
Cause: An attempt was made to convert the primary key of a materialized view to a ROWID materialized view.
- ORA-12018: following error encountered during code generation for "string"."string"
-
Cause: The refresh operations for the indicated materialized view could not be regenerated due to errors.
- ORA-12019: master table is a synonym to a remote object
-
Cause: An attempt was made to create a materialized view or a materialized view log on a remote synonym which is unsupported.
- ORA-12020: materialized view string is not registered
-
Cause: An attempt was made to unregister a materialized view that is not registered.
- ORA-12021: materialized view "string"."string" is corrupt
-
Cause: The materialized view indicated is no longer valid.
- ORA-12022: materialized view log on "string"."string" already has rowid
-
Cause: Materialized view log on the indicated table already has ROWID information.
- ORA-12023: missing index on materialized view "string"."string"
-
Cause: The specified ROWID materialized view did not have the required index on the ROWID column of its underlying table.
- ORA-12024: materialized view log on "string"."string" does not have primary key columns
-
Cause: Materialized view log on the indicated table does not have primary key information.
- ORA-12025: materialized view log on "string"."string" already has primary keys
-
Cause: Materialized view log on the indicated table already has primary key columns.
- ORA-12026: invalid filter column detected
-
Cause: One or more of the specified filter columns did not exist or was a primary key column or a primary key based object identifier.
- ORA-12027: duplicate filter column
-
Cause: One or more of the specified filter columns were already being recorded in the materialized view log.
- ORA-12028: materialized view type is not supported by master site string
-
Cause: Pre-Oracle8 master sites are not able to support primary key or subquery materialized views that are able to perform a fast refresh.
- ORA-12029: LOB columns may not be used as filter columns
-
Cause: An attempt was made to use LOB columns as filter columns.
- ORA-12030: cannot create a fast refresh materialized view
-
Cause: The materialized view log did not exist or did not log the information needed by the materialized view to perform a fast refresh.
- ORA-12031: cannot use primary key columns from materialized view log on "string"."string"
-
Cause: The materialized view log either did not have primary key columns logged, or the timestamp associated with the primary key columns was more recent than the last refresh time.
- ORA-12032: cannot use rowid column from materialized view log on "string"."string"
-
Cause: The materialized view log either does not have ROWID columns logged, or the timestamp associated with the ROWID columns is more recent than the last refresh time.
- ORA-12033: cannot use filter columns from materialized view log on "string"."string"
-
Cause: The materialized view log either did not have filter columns logged, or the timestamp associated with the filter columns was more recent than the last refresh time.
- ORA-12034: materialized view log on "string"."string" younger than last refresh
-
Cause: The materialized view log was younger than the last refresh.
- ORA-12035: could not use materialized view log on "string"."string"
-
Cause: The materialized view log did not exist or could not be used.
- ORA-12036: updatable materialized view log is not empty, refresh materialized view
-
Cause: The updatable materialized view log was not empty. The updatable materialized view log must be empty before an updatable rowid materialized view can be altered to a primary key materialized view.
- ORA-12037: unknown export format
-
Cause: An attempt was made to import a materialized view exported by an unknown export version (e.g., from a newer release than the importing site)
- ORA-12038: string literal has unexpected length
-
- ORA-12039: unable to use local rollback segment "string"
-
Cause: A local rollback segment was specified in the CREATE MATERIALIZED VIEW command, but automatic refresh parameters were not specified. Therefore a refresh group was not created to automatically refresh the materialized view and the local rollback segment can't be registered for future use.
- ORA-12040: master rollback segment option not support by master site string
-
Cause: An attempt was made to specify master rollback segment in the current operation. The master site of the current materialized view does not allow users to specify a rollback segment to be used for materialized view operations. This feature is only supported by Oracle8 or later master sites.
- ORA-12041: cannot record ROWIDs for index-organized table "string"."string"
-
Cause: Index-organized tables do not have ROWIDs. Therefore a materialized view log that records the ROWIDs of an index-organized table could not be created.
- ORA-12042: cannot alter job_queue_processes in single process mode
-
Cause: An attempt was made to alter job_queue_processes in single process mode.
- ORA-12043: invalid CREATE MATERIALIZED VIEW option
-
Cause: An invalid option was used in a CREATE MATERIALIZED VIEW statement.
- ORA-12044: invalid CREATE MATERIALIZED VIEW LOG option
-
Cause: An invalid option was used in a CREATE MATERIALIZED VIEW LOG statement.
- ORA-12045: invalid ALTER MATERIALIZED VIEW LOG option
-
Cause: An invalid option was used in an ALTER MATERIALIZED VIEW LOG statement.
- ORA-12046: cannot use trusted constraints for refreshing remote MV
-
Cause: REFRESH USING TRUSTED CONSTRAINTS specified in ALTER MATERIALIZED VIEW or CREATE MATERIALIZED VIEW of a remote materialized view
- ORA-12047: PCT FAST REFRESH cannot be used for materialized view "string"."string"
-
Cause: PCT refresh is either not enabled on this materialized view or not possible after set of the base table changes since last refresh.
- ORA-12048: error encountered while refreshing materialized view "string"."string"
-
Cause: Some problem occurs during refresh of multiple materialized views in atomic mode. The materialized view whose refresh failed has raised this error.
- ORA-12051: ON COMMIT attribute is incompatible with other options
-
Cause: ON COMMIT refresh attribute, incompatible with other refresh options such as automatic periodic refresh, was specified.
- ORA-12052: cannot fast refresh materialized view string.string
-
Cause: Either ROWIDs of certain tables were missing in the definition or the inner table of an outer join did not have UNIQUE constraints on join columns.
- ORA-12053: this is not a valid nested materialized view
-
Cause: The list of objects in the FROM clause of the definition of this materialized view had some dependencies upon each other.
- ORA-12054: cannot set the ON COMMIT refresh attribute for the materialized view
-
Cause: The materialized view did not satisfy conditions for refresh at commit time.
- ORA-12055: materialized view definition contains cyclic dependencies with existing materialized views
-
Cause: The materialized view query definition introduced a cyclic dependency with existing materialized view.
- ORA-12056: invalid REFRESH method
-
Cause: The NEVER REFRESH option may not be used under the following conditions: * The materialized view is updatable * The materialized view refreshes ON COMMIT * Automatic refresh options are specified
- ORA-12057: materialized view or zonemap "string"."string" is invalid and must use complete refresh
-
Cause: The status of the materialized view or zonemap was invalid and an attempt was made to fast refresh it.
- ORA-12058: materialized view cannot use prebuilt table
-
Cause: An attempt was made to use the prebuilt tables.
- ORA-12059: prebuilt table "string"."string" does not exist
-
Cause: The specified prebuilt table did not exist.
- ORA-12060: shape of prebuilt table does not match definition query
-
Cause: The number of columns or the type or the length semantics of a column in the prebuilt table did not match the materialized view definition query.
- ORA-12061: invalid ALTER MATERIALIZED VIEW option
-
Cause: An invalid option was used in an ALTER MATERIALIZED VIEW statement.
- ORA-12062: transaction string received out of sequence from site string
-
Cause: A transaction from the client site was received out of sequence. This implies that one or more transactions were missing.
- ORA-12063: unable to apply transaction from site string
-
Cause: The current transaction from the client site could not be applied to the master site.
- ORA-12064: invalid refresh sequence number: string
-
Cause: The client site was attempting to perform a refresh with an invalid refresh sequence.
- ORA-12065: unknown refresh group identifier string
-
Cause: The specified refresh group did not exist at the master site.
- ORA-12066: invalid CREATE MATERIALIZED VIEW command
-
Cause: The Replication API does not support the following options and types of materialized view: o ROWID materialized views o REFRESH ON COMMIT o ON PREBUILT TABLE o BUILD DEFERRED o NEVER REFRESH o ENABLE QUERY REWRITE
- ORA-12067: empty refresh groups are not allowed
-
Cause: The refresh group being instantiated did not contain any materialized views.
- ORA-12068: updatable mview log for mview "string"."string" does not exist
-
Cause: The updatable materialized view was missing the updatable materialized view log required to track updates made to the materialized view.
- ORA-12069: invalid object for offline instantiation
-
Cause: Only materialized views can be offline instantiated. The object being offline instantiated was not a valid materialized view.
- ORA-12070: cannot offline instantiate materialized view "string"."string"
-
Cause: Offline instantiation does not support materialized views using the following options: o ON PREBUILT TABLE o BUILD DEFERRED
- ORA-12071: definition query of "string"."string" is invalid for offline instantiation
-
Cause: Offline instantiation requires materialized view definition queries to observe the following constraints: o The database link that will be used by the materialized view site to connect to the master site must be included with each master table referenced in the query. o All master tables referenced must be located at the local site. References to other sites are not allowed.
- ORA-12072: updatable materialized view log data for "string"."string" cannot be created
-
Cause: The updatable materialized view was missing the updatable materialized view log required to track updates made to the materialized view.
- ORA-12073: request cannot be processed
-
Cause: An out-of-sequence request was made and it cannot be processed.
- ORA-12074: invalid memory address
-
Cause: An attempt was made to access an invalid memory region.
- ORA-12075: invalid object or field
-
Cause: An attempt was made to access an invalid field or object in the Java Virtual Memory.
- ORA-12076: invalid threshold value
-
Cause: The result set threshold or LOB threshold value is not supported.
- ORA-12077: temporary updatable materialized view log does not exist
-
Cause: Temporary updatable materialized view log was not created or was dropped.
- ORA-12078: fast refresh of refresh group ID string failed
-
Cause: Refresh result set sent through client method REFRESH_REQ_RESULT returned an unknown value.
- ORA-12079: do not invalidate result cache created during materialized view refresh
-
Cause: Result cache created during materialized view refresh was not invalidated at end.
- ORA-12080: Buffer cache miss for IOQ batching
-
- ORA-12081: update operation not allowed on table "string"."string"
-
Cause: An attempt was made to update a read-only materialized view.
- ORA-12082: "string"."string" cannot be index organized
-
Cause: An attempt was made to create an index-organized materialized aggregate view or an index-organized updatable ROWID materialized view. This is not supported.
- ORA-12083: must use DROP MATERIALIZED VIEW to drop "string"."string"
-
Cause: An attempt was made to drop a materialized view using a command other than DROP MATERIALIZED VIEW.
- ORA-12084: must use ALTER MATERIALIZED VIEW to alter "string"."string"
-
Cause: An attempt was made to alter a materialized view using a command other than ALTER MATERIALIZED VIEW.
- ORA-12085: materialized view log on "string"."string" already has object id
-
Cause: Materialized view log on the indicated table already has object id information.
- ORA-12086: table "string"."string" is not an object table
-
Cause: The CREATE MATERIALIZED VIEW LOG command was issued with the WITH OBJECT ID option and the master table is not an object table.
- ORA-12087: online redefinition not allowed on tables owned by "string"
-
Cause: An attempt was made to online redefine a table owned by SYS or SYSTEM.
- ORA-12088: cannot online redefine table "string"."string" with unsupported datatype
-
Cause: An attempt was made to online redefine a table containing a LONG column, an ADT column, or a FILE column.
- ORA-12089: cannot online redefine table "string"."string" with no primary key
-
Cause: An attempt was made to online redefine a table that does not have a primary key defined on it.
- ORA-12090: cannot online redefine table "string"."string"
-
Cause: An attempt was made to online redefine a table that is either a temporary table, an IOT overflow table, a table with fine-grained access control or row-level security enabled, a CDC change table, or a table with a CDC change table defined on it.
- ORA-12091: cannot online redefine table "string"."string" with materialized views
-
Cause: An attempt was made to online redefine a table that had materialized views defined on it or had a materialized view log defined on it or is a master.
- ORA-12092: cannot online redefine replicated table "string"."string"
-
Cause: An attempt was made to online redefine a table that is either a materialized view or a replicated table.
- ORA-12093: invalid interim table "string"."string"
-
Cause: The table is not the interim table of the corresponding table to be online redefined.
- ORA-12094: error during online redefinition
-
Cause: There was an error during the online redefinition process.
- ORA-12096: error in materialized view log on "string"."string"
-
Cause: There was an error originating from this materialized view log. One possible cause is that schema redefinition has occurred on the master table and one or more columns in the log is now a different type than corresponding master column(s). Another possible cause is that there is a problem accessing the underlying materialized view log table.
- ORA-12097: changes in the master tables during refresh, try refresh again
-
Cause: There are some changes (i.e., conventional DML, direct load, partition maintenance operation) in the master tables during materialized view refresh.
- ORA-12098: cannot comment on the materialized view
-
Cause: An attempt was made to issue a COMMENT ON TABLE statement on a materialized view.
- ORA-12099: Don't go into fast table scan (kdst) mode
-
- ORA-12100: materialized view log on "string"."string" already has sequence
-
Cause: Materialized view log on the indicated table already has sequence information.
- ORA-12101: shape of materialized view does not match the base table
-
Cause: The number of columns or the type or the length semantics of a column in the materialized view did not match the materialized view base table.