ORA-09858 to ORA-12101

77 ORA-09858 to ORA-12101

ORA-09858: sfngat: the input file name is not in the OMF format: Cause: The function sfngat() received a filename which is not an OMF file name.; Action: Further diagnostic information should be in the error stack.
ORA-09859: sfngat: the input file name is not in the autobackup OMF format: Cause: The function sfngat() received a filename which is not an autobackup OMF file name.; Action: Further diagnostic information should be in the error stack.
ORA-09870: spini: failure initializing maximum number of open files.: Cause: ulimit system call returned an error.; Action: Check errno.
ORA-09871: TASDEF_NAME: translation error while expanding ?/dbs/tasdef@.dbf.: Cause: Failure of sltln(?/tasdef@.dbf) while creating test and set pages.; Action: Check additional return error for more information.
ORA-09872: TASDEF_CREATE: create failure in creating ?/dbs/tasdef@.dbf.: Cause: Create() failed when trying to create the tasdef file.; Action: Verify permissions on $(ORACLE_HOME)/dbs directory.
ORA-09873: TASDEF_OPEN: open error when opening tasdef@.dbf file.: Cause: Unable to open tasdef@.dbf file.; Action: Check errno. Possible permission problem. Verify that tasdef@.dbf file exists.
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.; Action: Check errno returned. Sgadef file may be corrupted or incompatible with oracle version.
ORA-09875: TASDEF_WRITE: write error when writing ?/dbs/tasdef@.dbf file.: Cause: Write call failed.; Action: Check errno returned. Possibly out of space on device.
ORA-09876: TASDEF_CLOSE: unable to close ?/dbs/tasdef@.dbf file.: Cause: Close system call returned an error.; Action: Check errno returned. Possible operating system failure.
ORA-09877: sstascre: shmget error, unable to get a shared memory segment.: Cause: Error in shmget.; Action: Check errno returned. Verify that enough shared memory is available on the system.
ORA-09878: sstascre/sstasat: shmat error, unable to attach tas write page: Cause: Error in shmat.; Action: Check errno returned.Verify that enough shared memory is available on the system.
ORA-09879: sstascre/sstasat: shmat error, unable to attach tas read page: Cause: Error in shmat.; Action: Check errno returned.Verify that enough shared memory is available on the system.
ORA-09880: sstasfre/sstasdel: shmdt error, unable to detach tas write page: Cause: Error in shmdt.; Action: Check errno returned.
ORA-09881: sstasfre/sstasdel: shmdt error, unable to detach tas read page: Cause: Error in shmdt.; Action: Check errno returned.
ORA-09882: sstasfre/sstasdel: shmctl error, unable to remove tas shm page: Cause: Error in shmctl.; Action: Check errno returned.
ORA-09883: Two Task interface: oratab file does not exist: Cause: The oratab file does not exist.; Action: Install oracle before you use it or recreate the oratab file.
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.; Action: Start oracle with this SID on its designated PU (see oratab file). Or install the new database with SID.
ORA-09885: osnTXtt: cannot create TXIPC channel: Cause: The TXIPC driver failed to create pipes for two-task communications with the oracle shadow process.; Action: You have probably exceeded the maximum number of open file descriptors per user or the system file table is full. Note the operating system error code and contact your system administrator.
ORA-09886: osnTXtt: translation error while expanding txipc@.trc.: Cause: Failure of sltln(txipc@.trc) while creating debug channel.; Action: Check additional return error for more information.
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.; Action: You have probably exceeded the maximum number of open file descriptors per user or the system file table operating system error code and contact your system administrator.
ORA-09889: osnTXtt: access error on oracle executable: Cause: The txipc driver could not access the oracle executable.; Action: Check the permissions on the ORACLE executable and each component of the ORACLE_HOME/bin path.
ORA-09890: osnTXtt: malloc failed: Cause: The txipx driver failed to allocate enough heap space for its context area buffers.; Action: Contact your customer support representative.
ORA-09908: slkmnm: gethostname returned error code.: Cause: The system call gethostname returned an error.; Action: This is most likely an internal error. Make sure gethostname is successful in other contexts, and if so contact Oracle support.
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.; Action: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact ORACLE support.
ORA-09910: Unable to find ORACLE password file entry for user.: Cause: No entry exists for the user in the ORACLE password file.; Action: Have the database administrator install a password entry by running orapasswd.
ORA-09911: Incorrect user password.: Cause: The password entered by the user was incorrect.; Action: Enter the correct password.
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.; Action: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact ORACLE support.
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.; Action: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact ORACLE support.
ORA-09914: Unable to open the ORACLE password file.: Cause: ORACLE could not open the password file for reading.; Action: Check the UNIX error number. If the error number indicates that the file does not exist, have the database administrator create the file by running orapasswd. If the error number indicates insufficient permissions, ask the database administrator to change the permissions. Otherwise, contact ORACLE customer support.
ORA-09915: Password encryption failed.: Cause: ORACLE was unable to encrypt a password.; Action: This is an internal error - contact ORACLE customer support.
ORA-09916: Required password was not specified.: Cause: A user attempted to connect as "internal," but did not specify a password.; Action: Connect as internal again and 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.; Action: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact ORACLE support.
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.; Action: Check the UNIX error number for a possible operating system error. Also, check the privileges on the oracle executable. It should have at least "allowmacaccess" privilege.
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.; Action: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact ORACLE support.
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.; Action: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact ORACLE support.
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.; Action: Examine the directory pointed to by the initialization parameter "background_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.
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.; Action: Examine the directory pointed to by the initialization parameter "user_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.
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.; Action: Examine the directory pointed to by the initialization parameter "core_dump_dest". Make sure that all of the following is true: 1. The directory exists. 2. The name indeed points to a directory, and is not a file. 3. The directory is accessible and writable to the ORACLE user.
ORA-09925: Unable to create audit trail file: Cause: ORACLE was not able to create the file being used to hold audit trail records.; Action: Check the UNIX error number for a possible operating system error. If there is no error, contact ORACLE customer support.
ORA-09926: Unable to set effective privilege set of the server: Cause: A dedicated server was unable to set it's own privilege set.; Action: Check the privileges granted to the ORACLE executable. It must have at least "allowmacacess" privilege.
ORA-09927: Unable to set label of server: Cause: ORACLE was not able to set the label of a server to a new value.; Action: Check the privileges on $ORACLE_HOME/bin/oracle. Make sure that it has "allowmacaccess" privilege.
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.; Action: This is an internal error - contact ORACLE support.
ORA-09929: GLB of two labels is invalid: Cause: The result of a greatest lower bound operation on two labels was not valid.; Action: Repeat the operation with two different labels. Consult the system encoding file for the values of valid labels.
ORA-09930: LUB of two labels is invalid: Cause: The result of a least upper bound operation on two labels was not valid.; Action: Repeat the operation with two different labels. Consult the system encoding file for the values of valid labels.
ORA-09931: Unable to open ORACLE password file for reading: Cause: An attempt to open a password file for reading failed.; Action: Make sure that the permissions on the file have not been changed so that the ORACLE user cannot open it.
ORA-09932: Close of ORACLE password file failed.: Cause: An attempt to close a password file failed.; Action: Check the UNIX error number for the specific reason.
ORA-09933: Deletion of old password file failed.: Cause: The removal of the old password file failed.; Action: Check the UNIX error number for the specific reason.
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.; Action: Check the UNIX error number for the specific reason.
ORA-09935: Unlink of current password file failed.: Cause: ORACLE was unable to complete the saving of the current password file.; Action: Check the UNIX error number for the specific reason.
ORA-09936: Open of ORACLE password file for write failed.: Cause: ORACLE was unable to create a password file.; Action: Check the UNIX error number for the specific reason.
ORA-09937: Chmod of ORACLE password file failed.: Cause: ORACLE was unable to change a password file to be readonly.; Action: Check the UNIX error number for the specific reason.
ORA-09938: Save of signal handlers failed.: Cause: ORACLE was unable to save the previous values of selected signal handlers.; Action: This is an internal error. Contact ORACLE support.
ORA-09939: Restoration of signal handlers failed.: Cause: ORACLE was unable to restore the previous values of selected signal handlers.; Action: This is an internal error. Contact ORACLE support.
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.; Action: Check the headers of both files. The header should be in the format "FILE VERSION: N.N.N.N.N EXECUTABLE VERSION: N.N.N.N.N" where N is a number. Remove the corrupt file(s) and re-run "orapasswd".
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.; Action: Run a version of the installer or orapasswd whose version is the same or later than that of the file.
ORA-09942: Write of ORACLE password file header failed.: Cause: The attempt to write out the header of the ORACLE password file failed.; Action: Check the operating system error number. It is possible that the file system became full.
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.; Action: Check the operating system error number. The system has probably run out of memory.
ORA-09944: Password entry is corrupt.: Cause: An entry in an ORACLE password file was not in the format that ORACLE expected.; Action: Removed the corrupt file(s) and re-run "orapasswd."
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.; Action: Check the UNIX error number for a possible operating system error. If there is no error, contact ORACLE customer support.
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.; Action: Use a shorter file name.
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.; Action: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact ORACLE customer support.
ORA-09948: Process information label retrieval failed.: Cause: ORACLE was unable to get the information label for a process.; Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact ORACLE support.
ORA-09949: Unable to get client operating system privileges: Cause: ORACLE was unable to get the operating system privileges for the client process.; Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact ORACLE support.
ORA-09950: Unable to get server operating system privileges: Cause: ORACLE was unable to get its privileges from the operating system.; Action: This is an error that should never happen. Contact ORACLE customer support.
ORA-09951: Unable to create file: Cause: ORACLE was unable to create a file.; Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact ORACLE support.
ORA-09952: scgcmn: lk_open_convert unexpected return: open failed: Cause: The distributed lock manager returned an unexpected value; Action: Check for system error message and refer to the distributed lock manager documentation or contact your customer support representative.
ORA-09953: scggc: unexpected return of a lock convert: Cause: The distributed lock manager returned an unexpected value; Action: Check for lock manager error message and refer to DLM documentation refer to the distributed lock manager documentation or contact your customer support representative.
ORA-09954: scgcc: unexpected return status to callback of lock close: Cause: The distributed lock manager returned an unexpected value; Action: Check for lock manager error message and refer to DLM documentation refer to the distributed lock manager documentation or contact your customer support representative.
ORA-09955: scgcan: unexpected return status when canceling a lock: Cause: DLM system service x returned an unexpected value; Action: Check for system error message and refer to DLM documentation refer to the distributed lock manager documentation or contact your customer support representative.
ORA-09956: scgcm: unexpected lock status condition: Cause: A global locking system service returned an unexpected value.; Action: Check for system error message (if any) and refer to refer to the distributed lock manager documentation or contact your customer support representative.
ORA-09957: Unable to send termination request to IMON: Cause: The attempt to send a termination signal to IMON failed.; Action: This is an internal error, contact ORACLE support.
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.; Action: This is an internal error, contact ORACLE support.
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.; Action: This is an internal error, contact ORACLE support.
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.; Action: This is an internal error, contact ORACLE support.
ORA-09961: Unable to restore termination signal handler: Cause: ORACLE failed to set the handler for the termination signal to its previous value.; Action: This is an internal error, contact ORACLE support.
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.; Action: Check additional return errors for more information.
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.; Action: Check errno for more information.
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.; Action: Check errno for more information.
ORA-09969: unable to close or remove lock file: Cause: The close system call or unlink system call returned an error.; Action: Check errno for more information.
ORA-09974: skxfidini: Error Initializing SDI Channel: Cause: The process was unable to initialize the SDI channel properly.; Action: Correct the operating system error and retry the operation.
ORA-09975: kxfspini: Error Initializing SDI Process: Cause: The process was unable to attach to the SDI channel.; Action: Verify that the SDI process specific limits correctly configured. Correct the operating system error and retry the operation.
ORA-09976: skxfqdini: Error Creating Port: Cause: The process was unable to create a communications endpoint.; Action: Verify that the SDI port specific limits correctly configured. Correct the operating system error and retry the operation.
ORA-09977: skxfqhini: Error Connecting: Cause: The process was unable to connect to another endpoint.; Action: Verify that the SDI port specific limits correctly configured. Check that the other node(s) is part of the cluster and operating properly. Correct the operating system error and retry the operation.
ORA-09978: skxfqhdel: Error Disconnecting from another endpoint.: Cause: The process was unable to disconnect cleanly from another endpoint.; Action: Check that the other node(s) are part of the cluster and operating properly. Check the instance and processes on the other node(s). Correct the operating system error and retry the operation.
ORA-09979: skxfqhsnd: Error Sending a message to another endpoint: Cause: The process was unable to send a message to an existing endpoint.; Action: Check that the other node(s) are part of the cluster and operating properly. Check the instance and processes on the other node(s). Correct the operating system error and retry the operation.
ORA-09980: skxfqdrcv: Error Receiving a message from another endpoint: Cause: The process encountered an error while trying to receive a message.; Action: Check that the other node(s) are part of the cluster and operating properly. Check the instance and processes on the other node(s). Correct the operating system error and retry the operation.
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.; Action: Correct the operating system error and retry the operation.
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.; Action: Correct the operating system error and retry the operation.
ORA-09983: skxfidsht: Error shutting down SDI channel: Cause: The process was unable shut down the SDI channel; Action: Check the SDI persistent resources using SDI tools. Verify that all processes exited cleanly and the instance is safely shut down. Delete any remaining SDI channel IDs associated with the current instance.
ORA-09984: SGA file $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf does not exist: Cause: file does not exist or is not accessible; Action: Restart the instance to create the SGA definition file.
ORA-09985: SGA definition file could not be read: Cause: UNIX read() operation failed; Action: check errno and take appropriate action.
ORA-09986: wrong number of bytes read from SGA definition file: Cause: Struct skgmsdef size differs from no. of bytes read from SGA file; Action: Compare the two struct definitions and ensure that they are identical in size and structure.
ORA-09987: unable to attach to SGA in READ-ONLY mode: Cause: The instance is not up, or SGA segments are not read-accessible; Action: Verify that the instance is up and read permissions for the SGA segments are set.
ORA-09988: error while detaching SGA: Cause: skgmsdef struct is corrupted and/or segment addresses are modified; Action: Safely shut down instance and mount SGA segments again.
ORA-09989: attempt to use invalid skgmsdef struct pointer: Cause: Pointer to skgmsdef struct used without validating it; Action: Assign a valid address to the skgmsdef struct pointer before using it.
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.; Action: Do not open a pluggable database or acquire 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.; Action: Mount or open at least two instances.
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.; Action: Restart recovery using single instance Redo Apply. Do not specify the INSTANCE keyword in the command to start recovery.
ORA-11400: Control file has changed between fetches: Cause: The pseudo control file used by a per-Pluggable Database Data Guard (DGPDB) changed while a SQL query was fetching rows from it and those rows needed to correctly reflect the state of the data files.; Action: Execute the query again.
ORA-11401: Cached Control file data is not available: Cause: The instance wide cache for the pseudo control file used by a per-Pluggable Database Data Guard (DGPDB) was found to be invalid when an attempt was made to read from it.; Action: Retry the operation.
ORA-11402: Data Guard site entry not found: Cause: The SYS.DATA_GUARD_SITE$ table in ROOT did not contain the requested site details.; Action: If it is not obvious from the context of the error then the site name or database ID used to lookup up the site can be found in the trace file of the process originally reporting the error. Data Guard Broker is the preferred method to maintain the site configuration data. Try removing and adding the site again.
ORA-11403: Data Guard site data invalid or incomplete: Cause: The SYS.DATA_GUARD_SITE$ row contained incorrect or incomplete details used to form a connection to the site. The previous error on the error stack should give more insight into what is incorrect or incomplete. For example, an ORA-27476 indicates the defined or defaulted credential could not be accessed.; Action: If it is not obvious from the context of the error which site site entry is causing the problem or which piece of data from the entry is incorrect or incomplete then more details can be found in the trace file of the process that originally reported the error. Data Guard Broker is the preferred method to maintain the site configuration data. Try removing and adding the site again.
ORA-11404: User has no privilege to create a standby from the source: Cause: The Oracle user used to connect to the source CDB was not granted SYSDG privilege in the source PDB.; Action: Either grant the user the privilege, use a different user by modifying the Data Guard site configuration data, or modify the command being used to create the standby.
ORA-11405: Remote Data Guard site is not ready: Cause: Contact was made with the remote Data Guard site, but the following error was raised when an attempt was made to use the site.; Action: Examine the error following this one and attempt to rectify the issue. For example, ORA-03150 likely means the remote site is mounted but not open, and therefore attempt the operation again once the site open.
ORA-11406: The standby pluggable database "string" cannot be a source.: Cause: The SQL statement named a source pluggable database that was a per-Pluggable Database Data Guard (DGPDB). A DGPDB cannot be used in this context.; Action: Do not use a DGPDB as the source for this statement.
ORA-11407: Other Oracle RAC instances are not ready for the role change.: Cause: An attempt to change Oracle RAC instances to a primary role of the per-Pluggable Database Data Guard (DGPDB) failed.; Action: See the following error for more details, resolve the issue, and try again.
ORA-11408: Other Oracle RAC instances are not ready for the drop operation.: Cause: An attempt to change Oracle RAC instances to drop the per-Pluggable Database Data Guard (DGPDB) failed.; Action: See the following error for more details, resolve the issue, and try again.
ORA-11409: Instance string failed to respond within string centiseconds.: Cause: One or more Oracle RAC instances failed to respond to the per-Pluggable Database Data Guard (DGPDB) request as indicated in the previous error.; Action: The GEN2 process, on the specified Oracle RAC instance, is busy with a long running task. Try again later.
ORA-11410: Instance string returned error status string.: Cause: The per-Pluggable Database Data Guard (DGPDB) request failed on the specified Oracle RAC instance.; Action: The Oracle RAC instance was either shutting down or starting up or the GEN2 process was not ready. Try again later.
ORA-11411: This operation is not allowed in a standby container database.: Cause: The use of a per-Pluggable Database Data Guard (DGPDB) was not allowed in a standby container database.; Action: Do not use or change a DGPDB in a standby container database.
ORA-11412: Operation not allowed while the root container is open for upgrade or downgrade.: Cause: The attempted operation could not start because it needed to use dictionary tables in the root container, but the root container was being upgraded or downgraded.; Action: Try the operation again after the upgrade or downgrade task is complete.
ORA-11414: An active per PDB Data Guard is running on another instance.: Cause: The PDB could not be opened because another instance in the Oracle RAC has the same PDB open with recovery running. Only one Oracle RAC instance may have a standby PDB open with managed recovery running.; Action: If managed recovery needs to be running and the PDB needs to be open on this instance then cancel managed recovery, close the PDB on the other instance and then open it on this instance and start managed recovery. If the PDB needs to be open on more than one instance then cancel managed recovery and open it.
ORA-11415: A per PDB Data Guard standby is open on more than one instance.: Cause: Media recovery could not be started because another instance in the Oracle RAC has the same PDB open. Only one Oracle RAC instance may have a standby PDB open when managed recovery is running.; Action: Close the PDB on all other instances.
ORA-11416: System too busy. Try again later: Cause: The request to open, close, start recovery or cancel recovery for the standby PDB failed because the background process DBW0 was too busy. This is never expected to happen and an incident report has been created to capture why the DBW0 process failed to process the request in time.; Action: Try the action again later or use a different instance in the Oracle RAC.
ORA-11417: cannot run more than string active per PDB Data Guard: Cause: The operation could not start because it exceeded the resources available for per PDB Data Guard.; Action: Either cancel recovery for a running active per PDB Data Guard, start recovery for the active per PDB Data Guard from a different instance, or close the per PDB Data Guard before starting recovery.
ORA-11500: A domain constraint cannot be modified or dropped.: Cause: An attempt was made to modify or drop a constraint on a table that is inherited from a SQL domain.; Action: Do not attempt to modify or drop a constraint inherited from a domain. Alter the table and drop the domain from the columns as an alternative.
ORA-11501: The column default does not match the domain default of the column.: Cause: A default was specified for a column that was different than the default of the domain with which the column was associated.; Action: Correct the default to match the domain default of the column or disassociate the column from the domain.
ORA-11502: The domain to be dropped has dependent objects.: Cause: An attempt was made to drop a domain with dependent objects.; Action: Drop the domain using the FORCE mode.
ORA-11503: The column collation does not match the domain collation of the column.: Cause: The specified or default column collation was different than the domain collation with which the column was associated.; Action: The column collation associated with the domain cannot be modified. Set the domain collation on a column associated with the domain only.
ORA-11504: The domain specified does not exist or the user does not have privileges on the domain for the operation.: Cause: A domain was specified that did not exist or for which the user had no required privileges.; Action: Specify a valid domain or grant the required privileges on the domain.
ORA-11505: The domain already has an expression.: Cause: The specified ALTER DOMAIN statement attempted to add an expression that the domain already had.; Action: Use the ALTER DOMAIN MODIFY statement instead.
ORA-11506: The domain expression does not exist.: Cause: The ALTER DOMAIN statement tried to drop or modify an expression that the domain did not have.; Action: Use the ALTER DOMAIN ADD statement instead.
ORA-11507: The argument to DOMAIN_DISPLAY or DOMAIN_ORDER is not associated with a domain.: Cause: DOMAIN_DISPLAY or DOMAIN_ORDER was called with an argument that was not associated with a domain.; Action: Associate the argument with a domain or do not use DOMAIN operators.
ORA-11508: Casting to a domain using the MULTISET keyword is not allowed.: Cause: An attemp was made to cast to a domain using the MULTISET keyword.; Action: The DOMAIN and MULTISET keywords are mutually exclusive. User either the DOMAIN or the MULTISET keyword but not both.
ORA-11509: Casting to a multi-column domain is not allowed.: Cause: A multi-column domain was specified with a CAST operator.; Action: Use a single column domain with the CAST operator.
ORA-11510: Casting to a polymorphic or multi-column domain as specified is not allowed.: Cause: Either a polymorphic or a multi-cast domain was specified with the CAST operator; or the data type or collation for the CAST operator did not match the domain attributes.; Action: Use a non-polymorphic single column domain and match the data type and collation with those of the domain.
ORA-11511: Alter table modify drop domain cannot be combined with other options.: Cause: An attempt was made to modify column properties in addition to disassociating the column from the domain.; Action: Use separate ALTER TABLE statements; one to modify the column properties and one to disassociate the column from the domain.
ORA-11512: The column already has an associated domain.: Cause: An attempt was made to associate a domain to a column that was already associated with a domain, which is not allowed.; Action: Disassociate the column from the current domain and try the operation again.
ORA-11513: CAST AS DOMAIN has failed due to domain constraints.: Cause: The expression to be casted as domain did not satisfy one of the constraints of the domain.; Action: Ensure that the expression satisfies all of the enabled domain constraints.
ORA-11514: Creating a domain with the same name as an Oracle supplied type, or user defined data type, package or function is not allowed.: Cause: An attempt was made to create a domain with the same name as an Oracle supplied data type, or user defined data type, package, or function in the same schema.; Action: Ensure that the domain name does not coincide with that an Oracle supplied data type or a user defined type, package or function in the same schema.
ORA-11515: incorrect number of columns in domain association list: Cause: The number of columns associated with a domain did not match the domain column count.; Action: Associate a column with each domain column.
ORA-11517: the column data type does not match the domain column: Cause: The column data type did not match the domain column with which it was associated.; Action: Do not associate the column with the domain if the data types do not match.
ORA-11518: cannot drop domain from only a subset of the columns: Cause: The number of columns disassociated from a domain did not match the domain column count.; Action: Specify the full list of columns associated with the domain, one for each domain column.
ORA-11519: column is associated with a multi-column domain: Cause: An attempt was made to drop a column associated with a multi-column domain, without dropping all other columns.; Action: Drop all columns associated with a multi-column domain or drop domain from all such columns.
ORA-11520: sub-domain string not found: Cause: The specified sub-domain was missing.; Action: Ensure that the sub-domain exists and is accessible.
ORA-11521: sub-domain string is a flexible domain: Cause: The specified sub-domain was a flexible domain.; Action: Ensure that the sub-domain is a regular domain.
ORA-11522: domain column string data type is not the same in all sub-domains: Cause: The data type of the sub-domains was inconsistent.; Action: Ensure that the sub-domain column data types are the same.
ORA-11523: domain column string not referenced: Cause: Some domain column was not passed to a sub-domain.; Action: Ensure that all domain columns are referenced.
ORA-11524: sub-domain or its argument is an expression: Cause: The sub-domain or its argument was an expression.; Action: Ensure that all sub-domain arguments are domain columns.
ORA-11525: column string used in selector-expression is not a discriminant column: Cause: Some column was not in the discriminant column list.; Action: Ensure that only discriminant columns are used in the selector-expression.
ORA-11526: number of columns in sub-domain string do not match: Cause: The number of columns passed to the sub-domain do not match definition.; Action: Ensure that actual columns match the defined columns.
ORA-11527: duplicate domain or discriminant column: Cause: The specified column names were not unique.; Action: Ensure that there are no duplicate column names.
ORA-11528: missing discriminant column: Cause: A discriminant column was not specified.; Action: Specify discriminant columns when associating columns to a flexible domain.
ORA-11529: cannot modify the display or order of a domain used by a flexible domain: Cause: An attempt was made to add, drop or modify the display or order expression of a domain with flexible domain dependents.; Action: Drop all flexible domains depending on a domain before adding, dropping or modifying the domain display or order expression.
ORA-11530: cannot alter the display or order of a flexible domain: Cause: At attempt was made to alter a domain affecting its display or order expression.; Action: Drop the flexible domain, alter the domains it depended on and recreate the flexible domain.
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.; Action: All materialized views on a table can use the same materialized view log for that table. To make changes to the existing log, use the ALTER MATERIALIZED VIEW LOG command or drop the materialized view log and create it again.
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.; Action: To create a materialized view log, drop the current trigger on the master.
ORA-12002: there is no materialized view log on table "string"."string": Cause: There was no materialized view log on the master table.; Action: Create a 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.; Action: Verify input and retry.
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; Action: Use just REFRESH, which will reinstantiate the entire table. If a materialized view log exists and the form of the materialized view allows the use of a materialized view log or PCT refresh is possible after a given set of changes, REFRESH FAST will be available starting the next time the materialized view is refreshed.
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.; Action: Choose a time in the future instead.
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.; Action: Examine the other messages on the stack to find the problem.
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.; Action: Examine the other messages on the stack to find the problem. See if the objects SNAP$_<mview_name>, MVIEW$_<mview_name>, mowner.master@dblink, mowner.MLOG$_master@dblink still exist.
ORA-12009: materialized views may not contain long columns: Cause: An attempt was made to create a materialized view with a long column.; Action: Do not attempt to create materialized view logs with long columns.
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.; Action: Do not create a materialized view log 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.; Action: Look at the alert log for details on which jobs failed and why.
ORA-12012: error on auto execute of job string: Cause: An error was caught while doing an automatic execution of a job.; Action: Look at the accompanying errors for details on why the execute failed.
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.; Action: Make the materialized view simpler. If a join is really needed, make multiple simple materialized views then put a view on top of them. Make sure a materialized view log is created for the master table.
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.; Action: Reissue the command using only the WITH ROWID option, create a primary key constraint on the master table, or enable an existing primary key constraint.
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.; Action: Reissue the command with the REFRESH FORCE or REFRESH COMPLETE option or create a simple materialized view.
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.; Action: Include all of the master's primary key columns in the materialized view query or create a ROWID materialized view.
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.; Action: Conversion of a primary key materialized view to a ROWID materialized view is not supported. Create a new materialized view with ROWIDs or drop and recreate the materialized view with ROWIDs.
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.; Action: Correct the problem indicated in the following error messages and repeat the operation.
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.; Action: Do not create a materialized view or materialized view log on a remote synonym.
ORA-12020: materialized view string is not registered: Cause: An attempt was made to unregister a materialized view that is not registered.; Action: No action required.
ORA-12021: materialized view "string"."string" is corrupt: Cause: The materialized view indicated is no longer valid.; Action: Contact Oracle Customer Support.
ORA-12022: materialized view log on "string"."string" already has rowid: Cause: Materialized view log on the indicated table already has ROWID information.; Action: No action required.
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.; Action: Drop and recreate the materialized view.
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.; Action: Add primary keys to the materialized view log using the ALTER MATERIALIZED VIEW command.
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.; Action: No action required.
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.; Action: Ensure that all specified filter columns exist in the master table and ensure that primary key columns or primary key based object identifiers are not included in the list of filter columns.
ORA-12027: duplicate filter column: Cause: One or more of the specified filter columns were already being recorded in the materialized view log.; Action: Describe the materialized view log table and reissue the SQL command with the filter columns that are 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.; Action: Create a ROWID materialized view or use a master table from an Oracle8 site.
ORA-12029: LOB columns may not be used as filter columns: Cause: An attempt was made to use LOB columns as filter columns.; Action: Remove LOB columns from the filter columns list and retry command.
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.; Action: Ensure that the materialized view log exists and logs the necessary information. - For ROWID materialized views, the master table's ROWID must be logged. - For primary key materialized views, the master table's primary key columns must be logged. - For subquery materialized views, the filter columns, primary key, and ROWID values must be logged. - For object materialized views, object id must be logged.
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.; Action: A complete refresh is required before the next fast refresh. Add primary key columns to the materialized view log, if required.
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.; Action: A complete refresh is required before the next fast refresh. Add ROWID columns to the materialized view log, if required.
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.; Action: A complete refresh is required before the next fast refresh. Add filter columns to the materialized view log, if required.
ORA-12034: materialized view log on "string"."string" younger than last refresh: Cause: The materialized view log was younger than the last refresh.; Action: A complete refresh is required before the next fast 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.; Action: Use just REFRESH, which will reinstantiate the entire table. If a materialized view log exists and the form of the materialized view allows the use of a materialized view log, REFRESH FAST will be available starting the next time the materialized view is refreshed.
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.; Action: Ensure that updatable materialized view log is empty by refreshing the materialized view before converting the updatable ROWID materialized view 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); Action: Re-export the file using a version of export known by 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.; Action: Either supply the automatic refresh parameters so that a refresh group will be created or do not specify a local rollback segment.
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.; Action: Do not specify a master rollback segment in the current operation or choose a new master site.
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.; Action: Do not include the WITH ROWID option when using the CREATE MATERIALIZED VIEW command and do not include the ADD ROWID option when using the ALTER MATERIALIZED VIEW command if the master table is index-organized.
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.; Action: Do not attempt to set 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.; Action: Specify only valid options.
ORA-12044: invalid CREATE MATERIALIZED VIEW LOG option: Cause: An invalid option was used in a CREATE MATERIALIZED VIEW LOG statement.; Action: Specify only valid options.
ORA-12045: invalid ALTER MATERIALIZED VIEW LOG option: Cause: An invalid option was used in an ALTER MATERIALIZED VIEW LOG statement.; Action: Specify only valid options.
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; Action: remove this attribute from ALTER/ CREATE MATERIALIZED VIEW DDL
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.; Action: Use just REFRESH FORCE, which will reinstantiate the entire table and try to pick the best refresh method on the materialized view Do explain_mview to look at the cause why PCT refresh is not possible on this materialized view
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.; Action: Examine the other messages on the stack to find the refresh problem.
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.; Action: Specify only valid options.
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.; Action: Specify the FORCE or COMPLETE option. If this error is got during creation, the materialized view definition may have be changed. Refer to the documentation on materialized views.
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.; Action: Refer to the documentation to see which types of nesting are valid.
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.; Action: Specify only valid options.
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.; Action: Modify the materialized view query definition.
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; Action: For updatable materialized views, reissue the SQL command using REFRESH FORCE, REFRESH FAST, or REFRESH COMPLETE. For read-only materialized views, reissue the SQL command using ON DEMAND.
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.; Action: Perform a complete refresh of the materialized view or zonemap.
ORA-12058: materialized view cannot use prebuilt table: Cause: An attempt was made to use the prebuilt tables.; Action: Reissue the SQL command using BUILD IMMEDIATE or BUILD DEFERRED.
ORA-12059: prebuilt table "string"."string" does not exist: Cause: The specified prebuilt table did not exist.; Action: Reissue the SQL command using BUILD IMMEDIATE, BUILD DEFERRED, or ensure that the prebuilt table exists.
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.; Action: Reissue the SQL command using BUILD IMMEDIATE, BUILD DEFERRED, or ensure that the prebuilt table matches the materialized view definition query.
ORA-12061: invalid ALTER MATERIALIZED VIEW option: Cause: An invalid option was used in an ALTER MATERIALIZED VIEW statement.; Action: Specify only valid options.
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.; Action: Ensure that the transaction queue at the client site is valid and has not been corrupted.
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.; Action: Ensure that the client site is still valid and that it has not been dropped from 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.; Action: Perform a complete refresh to synchronize the refresh sequence number.
ORA-12065: unknown refresh group identifier string: Cause: The specified refresh group did not exist at the master site.; Action: Ensure that the client site is still valid and that it has not been dropped from 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; Action: Create a PRIMARY KEY materialized view using REFRESH WITH PRIMARY KEY and/or remove the invalid options.
ORA-12067: empty refresh groups are not allowed: Cause: The refresh group being instantiated did not contain any materialized views.; Action: Modify the template to include at least one materialized view.
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.; Action: Create the updatable materialized view log.
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.; Action: Remove the object from the template or replace the object with 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; Action: Remove the invalid options.
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.; Action: Modify the materialized view definition query.
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.; Action: Create an updatable materialized view log.
ORA-12073: request cannot be processed: Cause: An out-of-sequence request was made and it cannot be processed.; Action: Try again with a valid request.
ORA-12074: invalid memory address: Cause: An attempt was made to access an invalid memory region.; Action: Reconnect and try the command again.
ORA-12075: invalid object or field: Cause: An attempt was made to access an invalid field or object in the Java Virtual Memory.; Action: Retry the request.
ORA-12076: invalid threshold value: Cause: The result set threshold or LOB threshold value is not supported.; Action: Specify a threshold value below 64K.
ORA-12077: temporary updatable materialized view log does not exist: Cause: Temporary updatable materialized view log was not created or was dropped.; Action: Re-create the temporary updatable materialized view log. Warning: This will cause a complete refresh of the materialized view.
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.; Action: Re-issue the refresh request.
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.; Action: Do not set this as an event.
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.; Action: No action required. Only Oracle is allowed 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.; Action: Try to create the materialized view without the index organization clause.
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.; Action: Use the DROP MATERIALIZED VIEW command.
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.; Action: Use the ALTER MATERIALIZED VIEW command.
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.; Action: No action required.
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.; Action: Either specify the name of an object table, or remove the WITH OBJECT ID clause.
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.; Action: Do not attempt 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.; Action: Do not attempt 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.; Action: Do not attempt 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.; Action: Do not attempt to online redefine a table that is not supported by online redefinition.
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.; Action: Drop all materialized views and materialized view logs before attempting to online redefine the table.
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.; Action: Do not attempt 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.; Action: Pass in the valid interim table.
ORA-12094: error during online redefinition: Cause: There was an error during the online redefinition process.; Action: Abort 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.; Action: Check further error messages in stack for more detail about the cause. If there has been schema redefinition, drop the materialized view log and recreate it.
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.; Action: Refresh the affected materialized views again.
ORA-12098: cannot comment on the materialized view: Cause: An attempt was made to issue a COMMENT ON TABLE statement on a materialized view.; Action: Issue a COMMENT ON MATERIALIZED VIEW statement instead.
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.; Action: No action required.
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.; Action: Ensure that the materialized view column list matches with the base table.