- ORA-09870: spini: failure initializing maximum number of open files.
-
Cause: ulimit system call returned an error.
-
Action: Check errno.
- 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-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-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-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-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-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-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-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-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-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-10452: Cannot do block media recovery; media recovery session may be in progress
-
Cause: A media recovery, RMAN, or flashback database session may have been in progress when an attempt was made to perform block media recovery on the standby database.
-
Action: Check for and cancel any conflicting recovery session and perform block media recovery on the standby database.
- ORA-10456: cannot open standby database; media recovery session may be in progress
-
Cause: A media recovery, RMAN, or flashback database session may have been in progress on a mounted instance of a standby database when an attempt was made to open the standby database.
-
Action: Check for and cancel any conflicting recovery session and open the standby database.
- ORA-10459: cannot start media recovery on standby database; another instance may be open
-
Cause: An attempt was made to perform media recovery on a standby database while another instance performed recovery on the standby or had the standby open.
-
Action: Close the standby on all other instances, cancel any conflicting recovery session, and perform manual recovery.
- ORA-10469: error creating control file backup, no checkpoint
-
Cause: The control file being backed up did not contain a valid control file checkpoint. Therefore the control file could not be backed up, as such a backup would not be usable later for recovery. A common cause for this situation is that you executed CREATE CONTROLFILE, which mounts the database, but not ALTER DATABASE OPEN, to open the database. The latter operation generates a valid control file checkpoint.
-
Action: Open the database with ALTER DATABASE OPEN ..., which results in a valid control file checkpoint. Run the backup operation again.
- ORA-10546: Cannot perform block media recovery; standby database does not have requisite redo.
-
Cause: An attempt was made to perform block media recovery on the standby database when the necessary redo was not available.
-
Action: Wait until the necessary redo is available and reattempt block media recovery.
- ORA-10547: Cannot perform block media recovery; standby database is not caught up with primary.
-
Cause: An attempt was made to perform block media recovery on the standby database up to scn %s, which is greater than the highest scn of %s yet applied at the standby.
-
Action: Recover the standby up to scn %s and reattempt block media recovery.
- ORA-10549: Cannot perform block media recovery using a read-only plugged-in backup datafile.
-
Cause: An attempt was made to perform block media recovery using a backup of a read-only plugged-in datafile.
-
Action: Reattempt block media recovery using a backup taken after the plugged-in datafile has been converted to read/write.
- ORA-10562: Error occurred while applying redo to data block (file# string, block# string)
-
Cause: See other errors on error stack.
-
Action: Investigate why the error occurred and how important is the data block. Media and standby database recovery usually can continue if user allows recovery to corrupt this data block.
- ORA-10566: Test recovery has used all the memory it can use
-
Cause: Test recovery tests redo in memory. It can no longer proceed because it has consumed all the memory it can use.
-
Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary result of the test recovery.
- ORA-10567: Redo is inconsistent with data block (file# string, block# string)
-
Cause: There are two possible causes of this error: (1) A write issued by Oracle was lost by the underlying OS or storage system. (2) an Oracle internal error.
-
Action: Investigate why the error occurred and how important is the data block. Media and standby database recovery usually can continue if user allows recovery to corrupt this data block.
- ORA-10575: Give up restoring recovered datafiles to consistent state: out of memory
-
Cause: There were not enough memory to restore recovered datafiles to consistent state
-
Action: This error is just a warning: You may not be able to open the database with resetlogs immediately after this error. However, you may continue media/standby recovery, and that may make the datafiles recovered consistent again.
- ORA-10576: Give up restoring recovered datafiles to consistent state: some error occurred
-
Cause: See alert file or other errors on the stack for a cause of the problem.
-
Action: This error is just a warning: You may not be able to open the database with resetlogs immediately after this error. However, you may continue media/standby recovery, and that may make the datafiles recovered consistent again.
- ORA-10579: Can not modify control file during test recovery
-
Cause: To proceed with recovery, test recovery needs to modify the control file. But test recovery is not allowed to modify control file.
-
Action: No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream.
- ORA-10580: Can not modify datafile header during test recovery
-
Cause: To proceed with recovery, test recovery needs to modify a datafile header. But test recovery is not allowed to modify datafile headers.
-
Action: No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream.
- ORA-10581: Can not modify redo log header during test recovery
-
Cause: To proceed with recovery, test recovery needs to modify a redo log header. But test recovery is not allowed to modify redo log headers.
-
Action: No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream.
- ORA-10589: Test recovery had to corrupt string data blocks in order to proceed
-
Cause: This message summarizes test recovery result: Oracle may have to corrupt a number of data blocks as specified in the message in order to apply the range of redo tested.
-
Action: See alert log for details of the problems.
- ORA-10641: Cannot find a rollback segment to bind to
-
Cause: SYSTEM tablespace migration requires rollback segment in locally managed tablespace.
-
Action: Drop rollback segments in dictionary managed tablespaces other than SYSTEM and create rollback segments in locally managed tablespace and retry migration.
- ORA-10656: Table is in unusable state due to incomplete operation
-
Cause: ALTER TABLE SHRINK operation was tried on the table which is in unusable state because of previously failed/incomplete operation.
-
Action: If the previous operation was - DROP COLUMN, resubmit DROP COLUMN CONTINUE
- DROP TABLE, resubmit DROP TABLEPURGE
- ORA-10668: Inject Evil Identifiers
-
Cause: event 10668 is set to some number > 0, causing 1/(value-1) of all identifiers to be replaced by a maximum amount of x's. It is common for an identifier to be parsed once with a max of 30 bytes, then reparsed later with a max of 4000, so it may not be possible to inject such an identifier without the aid of this event. A value of 1 causes no identifiers to be corrupted.
-
Action: never set this event
- ORA-10704: Print out information about what enqueues are being obtained
-
Cause: When enabled, prints out arguments to calls to ksqcmi and ksqlrl and the return values.
-
Action: Level indicates details: Level: 1-4: print out basic info for ksqlrl, ksqcmi 5-9: also print out stuff in callbacks: ksqlac, ksqlop 10+: also print out time for each line
- ORA-10862: resolve default queue owner to current user in enqueue/dequeue
-
Cause: resolve default queue owner to current user in enqueue/dequeue.
-
Action: turn on if client wish to resolve the default queue owner to the current user. If not turned on, the default queue owner will be resolved to the login user.
- ORA-10873: file string needs to be either taken out of backup mode or media recovered
-
Cause: An attempt was made to open a database after an instance failure or SHUTDOWN ABORT interrupted an online backup.
-
Action: If the indicated file is not a restored backup, then issue the ALTER DATABASE END BACKUP command and open the database. If the file is a restored online backup, then apply media recovery to it and open the database.
- ORA-10919: Default temporary tablespace group must have at least one tablespace
-
Cause: An attempt was made to move the only tablespace in the default database temporary tablespace group to another tablespace group.
-
Action: Either change the database default temporary tablespace or add another tablespace to the group that this tablespace belongs to.
- ORA-10920: Cannot offline tablespace belonging to default temporary tablespace group
-
Cause: An attempt was made to offline a tablespace in the default database temporary tablespace group.
-
Action: Either change the database default temporary tablespace or change the tablespace group of this tablespace.
- ORA-10931: trace name context forever
-
Cause: When enabled, allows normal packages to be compiled with standard extensions like "
" -
Action: Set this event only for a short amount of time. Once the packages are compiled, this event should be turned off. Level 1 - Turn the event on Level > 1 - Turn the event off
- ORA-10945: trace name context forever
-
Cause: When enabled, disables the behaviour change introduced by the fix for bug 822764, which traps and handles invalidations of packages whereas the previous behaviour was to use stale invalidated instantiations of the stateful package body.
-
Action: set this event ONLY if necessary - after reading the README for this release or under supervision of Oracle Support.
- ORA-10947: trace name context forever
-
Cause: When enabled, causes various PL/SQL warnings related debugging info to be written in a trace file. Useful for debugging varous Oracle processes. available only in version 10.x.
-
Action: set this event ONLY if necessary - after reading the README for this release or under supervision of Oracle Support.
- ORA-10970: backout event for bug 2133357
-
Cause: 2133357 dynamically sets the varying width flag and character width. Lob data which is not migrated during migration from single byte to multibyte charater set will be displayed as special characters.
-
Action: To help migrate lob data which was not migrated during migration by backing out 2133357, so lob data can be selected and moved to multibyte character set.
- ORA-10979: trace flags for join index implementation
-
Cause: This is an informational message.
-
Action: Values are as follows: LEVEL ACTION --------------------------------------------------------------------------- > 1 Dump refresh expressions (SQL) to trace file. > 999 If a complete refresh is invoked, it will not be performed but the system will assume that a complete refresh was done, causing the view to be VALID and updating timestamps. This should be used only under Oracle Support supervision.
- ORA-10997: another startup/shutdown operation of this instance inprogress
-
Cause: An Oracle Instance startup or shutdown operation failed to procure the serialization primitive. Another foreground process may have attempted startup or shutdown operation in parallel.
-
Action: Check additional error messages in the alert log and the process trace file.
- 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-12008: error in materialized view refresh path
-
Cause: Table SNAP$_
reads rows from the view MVIEW$_ , 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 .MLOG$_ is also referenced. -
Action: Examine the other messages on the stack to find the problem. See if the objects SNAP$_
, MVIEW$_ , . @ , .MLOG$_ @ still exist.
- 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-12013: updatable materialized views must be simple enough to do fast refresh
-
Cause: The updatable materialized view query contained a join, subquery, union, connect by, order by, or group by caluse.
-
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.
- 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-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-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-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-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-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-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-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-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 "string"."string" is INVALID and must complete refresh
-
Cause: The status of the materialized view was INVALID and an attempt was made to fast refresh the materialized view.
-
Action: Perform a complete refresh of the materialized view. Check the value of the STATUS column in dba_mviews, all_mviews, or user_mviews to verify that the materialized view is VALID after the complete refresh.
- 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-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-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-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-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-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-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-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-12150: TNS:unable to send data
-
Cause: Unable to send data. Connection probably disconnected.
-
Action: Reestablish connection. If the error is persistent, turn on tracing and reexecute the operation.
- ORA-12154: TNS:could not resolve the connect identifier specified
-
Cause: A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured. For example, if the type of connect identifier used was a net service name then the net service name could not be found in a naming method repository, or the repository could not be located or reached.
-
Action: - If you are using local naming (TNSNAMES.ORA file):
- Make sure that "TNSNAMES" is listed as one of the values of the NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA)
- Verify that a TNSNAMES.ORA file exists and is in the proper directory and is accessible.
- Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file.
- Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may make it unusable.
- If you are using directory naming:
- Verify that "LDAP" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).
- Verify that the LDAP directory server is up and that it is accessible.
- Verify that the net service name or database name used as the connect identifier is configured in the directory.
- Verify that the default context being used is correct by specifying a fully qualified net service name or a full LDAP DN as the connect identifier
- If you are using easy connect naming:
- Verify that "EZCONNECT" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).
- Make sure the host, port and service name specified are correct.
- Try enclosing the connect identifier in quote marks. See the Oracle Net Services Administrators Guide or the Oracle operating system specific guide for more information on naming.
- ORA-12159: TNS:trace file not writeable
-
Cause: The trace file to be generated is not writeable by this user.
-
Action: If the user does not have write permissions in the directory to which the trace file will be written, contact an administrator to get the proper permissions or set the TRACE_DIRECTORY_CLIENT parameter in the net profile (SQLNET.ORA file) to a directory the user can write to.
- ORA-12162: TNS:net service name is incorrectly specified
-
Cause: The connect descriptor corresponding to the net service name in TNSNAMES.ORA or in the directory server (Oracle Internet Directory) is incorrectly specified.
-
Action: If using local naming make sure there are no syntax errors in the corresponding connect descriptor in the TNSNAMES.ORA file. If using directory naming check the information provided through the administration used for directory naming.
- ORA-12163: TNS:connect descriptor is too long
-
Cause: The connect descriptor corresponding to the net service name specified as the connect identifier is too long. The maximum length for a connect descriptor is 512 bytes and this limit has been exceeded.
-
Action: Check the net service name's connect descriptor in the local naming file (TNSNAMES.ORA) or in the directory server (Oracle Internet Directory). Use a smaller connect descriptor. If this is not possible, contact Worldwide Customer Support.
- ORA-12165: TNS:Trying to write trace file into swap space.
-
Cause: Oracle Trace doesn't allow writing trace information into your swap space.
-
Action: Oracle Trace cannot write trace information into swap space so either disable tracing or redirect trace files to be written to another area of your disk.
- ORA-12168: TNS:Unable to contact LDAP Directory Server
-
Cause: Cannot contact LDAP directory server to get Oracle Net configuration.
-
Action: Verify that the directory server is up and accessible from the network. Verify that directory access configuration is correct. For more information see the Oracle Internet Directory Administrators Guide or the Oracle Net Administrators Guide.
- ORA-12169: TNS:Net service name given as connect identifier is too long
-
Cause: The net service name you are attempting to resolve is too long.
-
Action: The maximum length of a net service name is 255 bytes; this limit has been exceeded. Use a smaller net service name. If this is not possible, contact Worldwide Customer Support.
- ORA-12170: TNS:Connect timeout occurred
-
Cause: The server shut down because connection establishment or communication with a client failed to complete within the allotted time interval. This may be a result of network or system delays; or this may indicate that a malicious client is trying to cause a Denial of Service attack on the server.
-
Action: If the error occurred because of a slow network or system, reconfigure one or all of the parameters SQLNET.INBOUND_CONNECT_TIMEOUT, SQLNET.SEND_TIMEOUT, SQLNET.RECV_TIMEOUT in sqlnet.ora to larger values. If a malicious client is suspected, use the address in sqlnet.log to identify the source and restrict access. Note that logged addresses may not be reliable as they can be forged (e.g. in TCP/IP).
- ORA-12171: TNS:could not resolve connect identifier: string
-
Cause: A connection to a database or other service was requested using a connect identifier, and the connect identifier specified could not be resolved into a connect descriptor using one of the naming methods configured. For example, if the type of connect identifier used was a net service name then the net service name could not be found in a naming method repository, or the repository could not be located or reached.
-
Action: - If you are using local naming (TNSNAMES.ORA file):
- Make sure that "TNSNAMES" is listed as one of the values of the NAMES.DIRECTORY_PATH parameter in the Oracle Net profile (SQLNET.ORA)
- Verify that a TNSNAMES.ORA file exists and is in the proper directory and is accessible.
- Check that the net service name used as the connect identifier exists in the TNSNAMES.ORA file.
- Make sure there are no syntax errors anywhere in the TNSNAMES.ORA file. Look for unmatched parentheses or stray characters. Errors in a TNSNAMES.ORA file may make it unusable.
- If you are using directory naming:
- Verify that "LDAP" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).
- Verify that the LDAP directory server is up and that it is accessible.
- Verify that the net service name or database name used as the connect identifier is configured in the directory.
- Verify that the default context being used is correct by specifying a fully qualified net service name or a full LDAP DN as the connect identifier
- If you are using easy connect naming:
- Verify that "EZCONNECT" is listed as one of the values of the NAMES.DIRETORY_PATH parameter in the Oracle Net profile (SQLNET.ORA).
- Make sure the host, port and service name specified are correct.
- Try enclosing the connect identifier in quote marks. See the Oracle Net Services Administrators Guide or the Oracle operating system specific guide for more information on naming.
- ORA-12198: TNS:could not find path to destination
-
Cause: Could not navigate a path through Interchanges to the destination. This error occurs if an invalid community is in the address string, or the address includes a protocol that is not available or the TNSNAV.ORA file does not have a correct CMANAGER address specified or the Interchange is down.
-
Action: Assure that Interchanges necessary to get to the desired destination are up and have available capacity for an additional connection. Also check that the correct community and protocol have been specified in the CMANAGER address used.
- ORA-12203: TNS:unable to connect to destination
-
Cause: Invalid address specified or destination is not listening. This error can also occur because of underlying network or network transport problems.
-
Action: Verify that the net service name you entered was correct. Verify that the ADDRESS portion of the connect descriptor which corresponds to the net service name is correct. Ensure that the destination process (for example the listener) is running at the remote node.
- ORA-12204: TNS:received data refused from an application
-
Cause: The application using Connection Manager refused the connection at the listener.
-
Action: Make sure that the application listener at the destination is functioning correctly. If it is and the problem persists, contact Worldwide Customer Support.
- ORA-12209: TNS:encountered uninitialized global
-
Cause: Application calling navigation routine has not properly configured the global variables. There are no TNSNAV.ORA files available, or they are defective.
-
Action: Not normally visible to the user. For further details, turn on tracing and reexecute the operation. If error persists, contact Worldwide Customer Support.
- ORA-12212: TNS:incomplete PREFERRED_CMANAGERS binding in TNSNAV.ORA
-
Cause: The PREFERRED_CMANAGERS binding in the client's TNSNAV.ORA file does not have a CMANAGER_NAME specified.
-
Action: Define the CMANAGER_NAME as part of the PREFERRED_CMANAGERS binding. Use of the Oracle Network Manager should eliminate this error.
- ORA-12217: TNS:could not contact PREFERRED_CMANAGERS in TNSNAV.ORA
-
Cause: There is a syntax error in the PREFERRED_CMANAGERS entry, or addresses specified are wrong, or the intended Connection Managers are unavailable.
-
Action: Check the PREFERRED_CMANAGERS entries in the client's TNSNAV.ORA file and correct them or talk with your network administrator to determine if the specified Connection Managers are available. Verify that the Interchanges are active by using the INTCTL STATUS command.
- ORA-12218: TNS:unacceptable network configuration data
-
Cause: Poorly formed network configuration data. For example, a PREFERRED_CMANAGERS entry may have an incorrect CMANAGER_NAME in the client's TNSNAV.ORA file. Or an Interchange downtime parameter (TIMEOUT_INTERVAL) on the Navigator may be set to zero in INTCHG.ORA.
-
Action: Check the entries in TNSNAV.ORA and the Interchange configuration files and correct them. If necessary, talk with your network administrator to determine if the specified Interchanges (Connection Managers) are available and properly configured. Use the Oracle Network Manager to generate the configuration files if necessary.
- ORA-12219: TNS:missing community name from address in ADDRESS_LIST
-
Cause: This error occurs when an ADDRESS_LIST has some ADDRESSes in it that have no COMMUNITY component and others that do have a COMMUNITY component.
-
Action: Check that in the connect descriptors you are using either all the ADDRESSes have a COMMUNITY component or all do not.
- ORA-12221: TNS:illegal ADDRESS parameters
-
Cause: An illegal set of protocol adapter parameters was specified. In some cases, this error is returned when a connection cannot be made to the protocol transport.
-
Action: Verify that the destination can be reached using the specified protocol. Check the parameters within the ADDRESS section of TNSNAMES.ORA or in the directory. Legal ADDRESS parameter formats may be found in the Oracle operating system specific documentation or the Oracle Net Administrator's Guide. Protocols that resolve names at the transport layer are vulnerable to this error if not properly configured or names are misspelled.
- ORA-12222: TNS:no support is available for the protocol indicated
-
Cause: The protocol requested in the ADDRESS portion of the connect descriptor identified through the net service name is not available. If the supplied ADDRESS is typographically correct then support for that protocol is not installed.
-
Action: Install support for the protocol or correct typographical error, as appropriate. Note: if the supplied address was derived from resolving the net service name, check the address in the appropriate file (TNSNAMES.ORA, LISTENER.ORA) or in the directory server.
- ORA-12224: TNS:no listener
-
Cause: The connection request could not be completed because the listener is not running.
-
Action: Ensure that the supplied destination address matches one of the addresses used by the listener - compare the TNSNAMES.ORA entry with the appropriate LISTENER.ORA file (or TNSNAV.ORA if the connection is to go by way of an Interchange). Start the listener on the remote machine.
- ORA-12228: TNS:protocol adapter not loadable
-
Cause: On some platforms (such as Windows) protocol support is loaded at run-time. If the shared library (or DLL) for the protocol adapter is missing or one of its supporting libraries is missing then this error is returned.
-
Action: For further details, turn on tracing and reexecute the operation. The trace file will include the name of the shared library (or DLL) that could not be loaded.
- ORA-12229: TNS:Interchange has no more free connections
-
Cause: One or more Interchanges along the path to the destination desired has no more free connections available to be used for this call.
-
Action: Try again later when the Interchanges are less busy, or contact your network administrator to have him determine which interchange it is, and increase the number of connections available on that interchange.
- ORA-12230: TNS:Severe Network error occurred in making this connection
-
Cause: This error is reported by an interchange which fails to make contact with the destination due to a physical network error while calling a destination.
-
Action: Try again later when the network service may have been fixed or report the problem to your Network Administrator so that he may fix the problem.
- ORA-12236: TNS:protocol support not loaded
-
Cause: On some platforms (such as Windows) protocol support is loaded at run-time. If the shared library (or DLL) for the protocol adapter has not been loaded, then this error is returned.
-
Action: For further details, turn on tracing and reexecute the operation. The trace file will have the name of the shared library (or DLL) that has not been loaded.
- ORA-12315: database link type is invalid for the ALTER DATABASE statement
-
Cause: The database link name you specified on the ALTER DATABASE statement is not an ROM: link. You must specify an ROM: link when using the ALTER DATABASE statement to mount or open a secondary database.
-
Action: Re-issue the ALTER DATABASE statement using a valid ROM: link to the database you want to mount or open. If a valid ROM: link does not exist, create one using the CREATE DATABASE LINK command. See the Trusted ORACLE RDBMS Guide to Security Features for more information about creating database links using the ROM: link type.
- ORA-12316: syntax error in database link's connect string
-
Cause: The connect string in the CREATE DATABASE LINK statement has a syntactical error.
-
Action: Drop the database link and recreate it using valid syntax. See the SQL Language Reference Manual for more information about the connect string portion of the CREATE DATABASE LINK statement.
- ORA-12317: logon to database (link name string) denied
-
Cause: There are several possible causes for this error. First, you can get this error if your username (and password, if you are using database instead of operating system authentication) in the secondary database are not identical to your username (and password) in the primary database. Second, you can get this error if your username in the secondary database is invalid (has not been created). Third, you can get this error if the username/password combination specified in the connect string of the database link definition is invalid (either not created or has an invalid password).
-
Action: In the first case, ensure that the secondary database contains a username (and password, if you are using database authentication) identical to the one you are using in the primary database. In general, you should always use operating system authentication in Trusted ORACLE (see the Trusted ORACLE RDBMS Guide to Security Features for more information about the advantages of OS authentication). In the second case, ensure that your username in the secondary database has been created. In the third case, ensure that the username specified in the connect string has been created in the secondary database.
- ORA-12321: database (link name string) is not open and AUTO_MOUNTING=FALSE
-
Cause: The secondary database that your instance is attempting to mount is not open and automatic mounting has not been enabled.
-
Action: Manually mount and open the secondary database using ALTER DATABASE
with the OPEN and MOUNT options. Alternately, to allow your instance to automatically mount and open secondary databases, set the AUTO_MOUNTING parameter in the parameter file to TRUE.
- ORA-12324: cannot use the ROM: link type on a private database link
-
Cause: You can only specify the ROM: link type on a public, not a private, database link.
-
Action: Determine if there is an existing public database link to the secondary database. If not, and if you wish to establish public access to the secondary database, create a public database link to the secondary database using the CREATE DATABASE LINK command.
- ORA-12341: maximum number of open mounts exceeded
-
Cause: The number specified on the OPEN_MOUNTS parameter in the parameter file exceeds the maximum allowed (255).
-
Action: Change the value of this parameter so that it reflects the actual number of possible open mounts to secondary databases. This must be less than 255.
- ORA-12342: open mounts exceeds limit set on the OPEN_MOUNTS parameter
-
Cause: The number of currently open mounts exceeds the value you specified on the OPEN_MOUNTS parameter.
-
Action: Increase the value of the OPEN_MOUNTS parameter so that it accommodates the maximum possible number of open mounts to secondary databases.
- ORA-12345: user string lacks CREATE SESSION privilege in database link (linkname string)
-
Cause: There are several possible causes for this message: First, you will get this message if your username in the second database specified was not granted the CREATE SESSION system privilege. Second, you will get this message if the username specified in the connect string of the database link definition was not granted the CREATE SESSION system privilege.
-
Action: The action you take depends upon the cause of the message: In the first case, ensure that your username in the secondary database was granted the CREATE SESSION system privilege. In the second case, ensure the username specified in the connect string of the database link definition was granted the CREATE SESSION system privilege in the secondary database.
- ORA-12351: cannot create view using a remote object which has a remote object reference
-
Cause: You tried to create a view which references a remote object which, in turn, references an object on another database. Since the view that you tried to create references a remote object, that object cannot reference an object on another database.
-
Action: Choose a different object to reference in your view or change the remote object so that it does not reference another database.
- ORA-12352: object string.string@string is invalid
-
Cause: An attempt was made to reference (compile against) an object of a secondary database but the object is invalid and the system cannot validate or recompile it because it is in a secondary database.
-
Action: Manually recompile the invalid object in the secondary database.
- ORA-12353: secondary stored object cannot reference remote object
-
Cause: You tried to either select from a remote view or execute a remote procedure which references an object on another database. Since the remote view or procedure is on a secondary database, an additional reference to another database cannot be done.
-
Action: Choose a different object to reference or change the remote view or procedure so that it does not reference another database.
- ORA-12354: secondary object being dropped
-
Cause: You tried to access a object (for example, a table or view) on a secondary database that was in the process of being dropped.
-
Action: Repeat the operation. If you receive this message again, try to access the object from the secondary database. If you receive an internal error or a trace file, contact Oracle WorldWide Technical Support.
