ORA-02140 to ORA-04099
-
ORA-02159: installed DLM does not support releasable locking mode
-
Cause: The parameter file specified gc_* parameters that allow locks to be release by the LCK process when not in use. This mode requires additional support from the DLM that is not available.
-
Action: Specify configuration parameters that do not require the additional function.
-
ORA-02170: FREELIST GROUPS storage option not allowed
-
Cause: The user attempted to specify the FREELIST GROUPS storage option. This option may only be specified during create table and when allow_freelist_groups INIT.ORA is specified.
-
Action: Remove this option and retry the statement or set the allow_freelist_groups INIT.ORA parameter.
-
ORA-02266: unique/primary keys in table referenced by enabled foreign keys
-
Cause: An attempt was made to truncate a table with unique or primary keys referenced by foreign keys enabled in another table. Other operations not allowed are dropping/truncating a partition of a partitioned table or an ALTER TABLE EXCHANGE PARTITION.
-
Action: Before performing the above operations the table, disable the foreign key constraints in other tables. You can see what constraints are referencing a table by issuing the following command: SELECT * FROM USER_CONSTRAINTS WHERE TABLE_NAME = "tabnam";
-
ORA-02270: no matching unique or primary key for this column-list
-
Cause: A REFERENCES clause in a CREATE/ALTER TABLE statement gives a column-list for which there is no matching unique or primary key constraint in the referenced table.
-
Action: Find the correct column names using the ALL_CONS_COLUMNS catalog view
-
ORA-02303: cannot drop or replace a type with type or table dependents
-
Cause: An attempt was made to drop or replace a type that has type or table dependents.
-
Action: For DROP TYPE, drop all type(s) and table(s) depending on the type and then retry the operation, or use the FORCE option. For CREATE TYPE, drop all type(s) and table(s) depending on the type and then retry the operation, or drop all table(s) depending on the type and retry with the FORCE option.
-
ORA-02304: invalid object identifier literal
-
Cause: An attempt was made to enter an object identifier literal for CREATE TYPE that is either:
- not a string of 32 hexadecimal characters
- an object identifier that already identifies an existing object
- an object identifier different from the original object identifier already assigned to the type
-
Action: Do not specify the object identifier clause or specify a 32 hexadecimal-character object identifier literal that is unique or identical to the originally assigned object identifier. Then retry the operation.
-
ORA-02306: cannot create a type that already has valid dependent(s)
-
Cause: An attempt was made to create a type that already has some valid dependent(s) (these dependents depend on the fact that the type does not exist).
-
Action: Drop the dependents first before creating the type, or do not create the type.
-
ORA-02320: failure in creating storage table for nested table column string
-
Cause: An error occurred while creating the storage table for the specified nested table column.
-
Action: See the messages that follow for more details. If the situation they describe can be corrected, do so; otherwise contact Oracle Support.
-
ORA-02329: column of datatype string cannot be unique or a primary key
-
Cause: An attempt was made to place a UNIQUE or a PRIMARY KEY constraint on a column of datatype VARRAY, nested table, object, LOB, FILE or REF.
-
Action: Change the column datatype or remove the constraint. Then retry the operation.
-
ORA-02348: cannot create VARRAY column with embedded LOB
-
Cause: An attempt was made to create a column of a VARRAY type which has an embedded LOB attribute. The LOB could be an attribute of a subtype of the declared type of VARRAY's element.
-
Action: Remove offending attribute from type. If it is a subtype attribute then declare the VARRAY column NOT SUBSTITUTABLE.
-
ORA-02359: database version in file string is not valid
-
Cause: The specified file could not be used for this load because its database version was not compatible with the database version in the other files in the DUMPFILE clause.
-
Action: Verify all the files in the DUMPFILE clause are from the same unload operation.
-
ORA-02370: internal metadata in file string is not valid
-
Cause: The specified file could not be used for this load because the internal metadata stored in this file does not match the metadata stored in the first file piece set.
-
Action: Verify all the files in the DUMPFILE clause are from the same unload operation.
-
ORA-02374: conversion error loading table string.string
-
Cause: A row could not be loaded into the table because there was a conversion error for one or more columns in a row.
-
Action: See the message that follows for more information about the row that could not be loaded. To avoid this error, make sure the definition of the table being imported matches the definition of the table being exported.
-
ORA-02375: conversion error loading table string.string partition string
-
Cause: A row could not be loaded into the table because there was a conversion error for one or more columns in a row.
-
Action: See the message that follows for more information about the row that could not be loaded. To avoid this error, make sure the definition of the table being imported matches the definition of the table being exported.
-
ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit
-
Cause: An attempt was made to exceed the maximum number of concurrent sessions allowed by the SESSION_PER_USER clause of the user profile.
-
Action: End one or more concurrent sessions or ask the database administrator to increase the SESSION_PER_USER limit of the user profile.
-
ORA-02424: potential circular view references or unknown referenced tables
-
Cause: the create schema statement contains views that depend on other views in the containing create schema statement or they contain references to unknown tables.
-
Action: create the dependent views in a separate create schema statement and make sure all referenced tables are either defined in the create schema statement or exist outside the statement.
-
ORA-02436: date or system variable wrongly specified in CHECK constraint
-
Cause: An attempt was made to use a date constant or system variable, such as USER, in a check constraint that was not completely specified in a CREATE TABLE or ALTER TABLE statement. For example, a date was specified without the century.
-
Action: Completely specify the date constant or system variable. Setting the event 10149 allows constraints like "a1 > '10-MAY-96'", which a bug permitted to be created before version 8.
-
ORA-02449: unique/primary keys in table referenced by foreign keys
-
Cause: An attempt was made to drop a table with unique or primary keys referenced by foreign keys in another table.
-
Action: Before performing the above operations the table, drop the foreign key constraints in other tables. You can see what constraints are referencing a table by issuing the following command: SELECT * FROM USER_CONSTRAINTS WHERE TABLE_NAME = "tabnam";
-
ORA-02474: Fixed hash area extents used (string) exceeds maximum allowed (string)
-
Cause: The number of extents required for creating the fixed hash area exceeds the maximum number allowed.
-
Action: Reduce the number of extents required by increasing the extent allocation sizes within the STORAGE clause.
-
ORA-02478: merge into base segment would overflow MAXEXTENTS limit
-
Cause: Merge of temporary segment into base segment failed because MAXEXTENTS was larger than the total in the temp and base segments
-
Action: Use a larger value for MAXEXTENTS on the base segment or make the extents in the temporary segments larger
-
ORA-02703: osnpopipe: pipe creation failed
-
Cause: The pipe driver failed to create pipes for communications with the orapop 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-02708: osnrntab: connect to host failed, unknown ORACLE_SID
-
Cause: The invoked Unix two-task driver failed to find an entry in oratab for the sid you supplied.
-
Action: First, check whether you have read access to oratab, and see if the desired sid is there. Add an entry to oratab for the desired sid, if necessary.
-
ORA-02709: osnpop: pipe creation failed
-
Cause: The pipe 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-02710: osnpop: fork failed
-
Cause: The pipe driver could not fork the oracle shadow process.
-
Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient.
-
ORA-02719: osnfop: fork failed
-
Cause: The fast driver could not fork the oracle shadow process.
-
Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient.
-
ORA-02720: osnfop: shmat failed
-
Cause: When the fast driver was invoked, processes failed to attach to the shared memory buffer. You probably supplied an illegal shared memory attach address, or the system ran out of data space to accomodate the buffer.
-
Action: Try invoking the Fast driver later, or use the default attach address.
-
ORA-02730: osnrnf: cannot find user logon directory
-
Cause: The driver you have specified could not find your logon directory while searching for your local .sqlnet file.
-
Action: Set and export the HOME environment variable to identify your home directory. Check with your system administrator to make sure that your uid and home directory are correct in the /etc/passwd file.
-
ORA-02732: osnrnf: cannot find a matching database alias
-
Cause: Database alias specified was not identified in either $HOME/.sqlnet or /etc/sqlnet.
-
Action: Create the alias in a file called .sqlnet in your home directory for personal use or ask your system administrator to create the alias in /etc/sqlnet for system-wide use.
-
ORA-02786: Size needed for shared region is greater than segment size
-
Cause: The size of the shared segment that was specified for the shared buffer region is less than the number of bytes required. The first field of the "additional information" field is the size needed. The second is the size of the segment.
-
Action: Use a larger size segment or let the package allocate its own.
-
ORA-02800: Requests timed out
-
Cause: Some of the requests for asynchronous input or output were not serviced in the required amount of time.
-
Action: If the load on the system is high, it is possible that the timeout limit is too low. Reset it with sfainit(). If the server processes are dying due to unexpected signals, this is an internal error, and ORACLE support should be contacted.
-
ORA-02818: Less than the number of blocks requested was read in
-
Cause: A server could not read in the request amount of data. The first number in the "additional information" field is the block number being read in. The second is the actual number of bytes that was read in.
-
Action: This is a programming error.
-
ORA-02819: Write failed
-
Cause: A server was unable to perform a write. The number in the "additional information" field is the starting block number of the data segment being written out. The first number in the "additional information" field is the block number being written out. The second is the actual number of bytes that was written out. The disk may have filled up.
-
Action: Check the UNIX error number.
-
ORA-02842: Client unable to fork a server
-
Cause: The client could not spawn a server. A possible reason is that the operating system has reached its limit on the number of processes that it can spawn.
-
Action: Either reduce the number of servers that are to be used, or reconfigure the operating system so that it can handle more processes.
-
ORA-02855: Number of requests is less than the number of slaves
-
Cause: The value given for "db_slave_buffers" in your INIT.ORA file is less than the number specified for the number of slaves, "db_slaves."
-
Action: Specify a number that is greater than that given for "db_slaves" Alternatively, specify 0. The kernel will supply the appropriate number.
-
ORA-03113: end-of-file on communication channel
-
Cause: The connection between Client and Server process was broken.
-
Action: There was a communication error that requires further investigation. First, check for network problems and review the SQL*Net setup. Also, look in the alert.log file for any errors. Finally, test to see whether the server process is dead and whether a trace file was generated at failure time.
-
ORA-03127: no new operations allowed until the active operation ends
-
Cause: An attempt was made to execute a new operation before the active non-blocking operation completed or a new operation was attempted before all the pieces of a column were inserted or fetched.
-
Action: Execute the new operation after the non-blocking operation completes. If piecewise binds/defines were done, execute the new operation after all the pieces have been inserted or fetched.
-
ORA-03136: inbound connection timed out
-
Cause: Inbound connection was timed out by the server because user authentication was not completed within the given time specified by SQLNET.INBOUND_CONNECT_TIMEOUT or its default value
-
Action: 1) Check SQL*NET and RDBMS log for trace of suspicious connections. 2) Configure SQL*NET with a proper inbound connect timeout value if necessary.
-
ORA-03150: end-of-file on communication channel for database link
-
Cause: The connection between the client and the remote server process was broken.
-
Action: Look in the alert.log file of the remote server for any errors. Also, check to see whether the remote server process is dead and whether a trace file was generated at failure time.
-
ORA-03170: deadlocked on readable physical standby (undo segment string)
-
Cause: A new undo segment was added. A query can occasionally deadlock when issued around the time an undo segment is added and used immediately on the primary.
-
Action: Retry the query. Avoid creating new undo segments when using standby as a regular part of operation.
-
ORA-03171: Recovery was terminated during query execution
-
Cause: Recovery was terminated. A query can ocassionally deadlock when recovery is terminated because it needs a block with changes that are made after the point at which recovery was terminated.
-
Action: Retry the query. Avoid cancelling recovery on standby.
-
ORA-03173: Standby may not be synced with primary
-
Cause: ALTER SESSION SYNC WITH PRIMARY did not work because either the standby was not synchronous or in a data-loss mode with regard to the primary, or the standby recovery was terminated.
-
Action: Make the standby synchronous and no-data-loss with regard to the primary. Make the standby recovery active.
-
ORA-03212: Temporary Segment cannot be created in locally-managed tablespace
-
Cause: Attempt to create a temporary segment for sort/hash/lobs in in permanent tablespace of kind locally-managed
-
Action: Alter temporary tablespace of user to a temporary tablespace or a dictionary-managed permanent tablespace
-
ORA-03219: Tablespace 'string' is dictionary-managed, offline or temporary
-
Cause: Operation which is only applicable to permanent, online, locally-managed tablespaces is specified for a tablespace which is either dictionary-managed, offline or temporary
-
Action: Reissue operation for a different tablespace, mount the tablespace or do not issue it at all, since it does not apply for the given tablespace
-
ORA-03221: Temporary tablespaces and temporary segments must have standard block size
-
Cause: An attempt was made to do one of the following : (1) create a temporary tablespace with a non-standard block size or, (2) alter an existing permanent tablespace of non-standard block size to a temporary tablespace or, (3) issue a DDL statement that would result in the creation of a temporary segment in a tablespace of non-standard block size.
-
Action: (1) If creating a temporary tablespace, do not specify a block size different from the standard block size. (2) If altering an existing permanent tablespace to a temporary tablespace, ensure that it is of standard block size. (3) Ensure that the user's temporary tablespace is a tablespace having the standard block size.
-
ORA-03222: average row size and row count must be greater than zero
-
Cause: Either a bad value passed to dbms_space.create_table_cost() or explain plan did not pass through size information.
-
Action: Check the row size parameter in dbms_space.create_table_cost(). For explain plan, make sure statistics have been computed for all source tables in the CREATE TABLE AS SELECT statement.
-
ORA-03223: Bitmap index block addressable limitation reached
-
Cause: The limitation of addressability of BMIB (Bitmap Index Block) was reached for the current blocksize.
-
Action: If the segment size has grown greater than addressability of BMIB (Bitmap Index Block), do the following: (1) Partition the table. (2) Move the segment to a tablespace having bigger blocksize.
-
ORA-03238: unable to extend LOB segment string.string subpartition string by string in tablespace string
-
Cause: An attempt was made to allocate an extent for LOB subpartition segment in tablespace, but the extent could not be allocated because there is not enough space in the tablespace indicated.
-
Action: Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.
-
ORA-03239: maxextents (string) reached in LOB segment string.string subpartition string
-
Cause: A LOB subpartition segment tried to extend past maxextents.
-
Action: If maxextents is less than the system maximum, raise it. Otherwise, recreate the subpartition with larger INITIAL, NEXT, or PCTINCREASE parameters.
-
ORA-03244: No free space found to place the control information
-
Cause: During migration of tablespace found no place to put the control information. If during bitmaps relocation, found no space at the specified destination.
-
Action: If during migration, add more space to the tablespace and retry migration. If during bitmaps relocation, specify a destination address where there is enough free space.
-
ORA-03254: unable to execute the sql in read only database
-
Cause: Unable to create a consistent snapshot of the object in a read only database. Transaction recovery must be performed before opening the database read only.
-
Action: Open the database read write, allow dead transaction recovery to complete and then open the database read only.
-
ORA-03297: file contains used data beyond requested RESIZE value
-
Cause: Some portion of the file in the region to be trimmed is currently in use by a database object
-
Action: Drop or move segments containing extents in this region prior to resizing the file, or choose a resize value such that only free space is in the trimmed.
-
ORA-03299: cannot create dictionary table string
-
Cause: A dictionary table is created upon the first execution of the command 'alter database datafile autoextend on' for a database. This operation did not succeed. The most probable cause for this is insufficient space in the system tablespace.
-
Action: See action for next error message in error stack.
-
ORA-04031: unable to allocate string bytes of shared memory ("string","string","string","string")
-
Cause: More shared memory is needed than was allocated in the shared pool or Streams pool.
-
Action: If the shared pool is out of memory, either use the DBMS_SHARED_POOL package to pin large packages, reduce your use of shared memory, or increase the amount of available shared memory by increasing the value of the initialization parameters SHARED_POOL_RESERVED_SIZE and SHARED_POOL_SIZE. If the large pool is out of memory, increase the initialization parameter LARGE_POOL_SIZE. If the error is issued from an Oracle Streams or XStream process, increase the initialization parameter STREAMS_POOL_SIZE or increase the capture or apply parameter MAX_SGA_SIZE.
-
ORA-04032: pga_aggregate_target must be set before switching to auto mode
-
Cause: attempt to set workarea_size_policy to AUTO while pga_aggregate_target is not specified
-
Action: before setting workarea_size_policy, set pga_aggregate_target to a value representing the total private memory available to the instance. This total is generally the total physical memory available in the system minus what is needed for the SGA minus what is needed for the operating system (e.g. 500MB)
-
ORA-04043: object string does not exist
-
Cause: An object name was specified that was not recognized by the system. There are several possible causes:
- An invalid name for a table, view, sequence, procedure, function, package, or package body was entered. Since the system could not recognize the invalid name, it responded with the message that the named object does not exist.
- An attempt was made to rename an index or a cluster, or some other object that cannot be renamed.
-
Action: Check the spelling of the named object and rerun the code. (Valid names of tables, views, functions, etc. can be listed by querying the data dictionary.)
-
ORA-04045: errors during recompilation/revalidation of string.string
-
Cause: This message indicates the object to which the following errors apply. The errors occurred during implicit recompilation/revalidation of the object.
-
Action: Check the following errors for more information, and make the necessary corrections to the object.
-
ORA-04046: results of compilation are too large to support
-
Cause: Attempt to compile and store a large stored procedure that results in compilation data that is too large for the system to support or store.
-
Action: Reduce the size of the store procedure by splitting it into smaller stored procedures.
-
ORA-04051: user string cannot use database link string.string
-
Cause: During forwarding of a remote object access, an attempt was made to use a non-existent database link or one owned by a user other than the logon user or PUBLIC.
-
Action: Change your database link structure so that all indirect remote accesses are done from the same userid that originates the request.
-
ORA-04052: error occurred when looking up remote object stringstringstringstringstring
-
Cause: An error occurred when trying to look up a remote object.
-
Action: Fix the error. Make sure the remote database system has run CATRPC.SQL to create necessary views used for querying or looking up objects stored in the database.
-
ORA-04053: error occurred when validating remote object stringstringstringstringstring
-
Cause: An error occurred when trying to validate a remote object.
-
Action: Fix the error. Make sure the remote database system has run CATRPC.SQL to create necessary views used for querying or looking up objects stored in the database.
-
ORA-04055: Aborted: "string" formed a non-REF mutually-dependent cycle with "string".
-
Cause: This compilation was aborted because the library unit that was compiled would have formed a non-REF mutually-dependent cycle with some other library units. This happens when an attempt is made to compile types that have attributes of other types that may participate in a cycle with this type. Example: create type t1; create type t2 (a t1); create type t1 (a t2);
-
Action: Break the cycle (possibly by adding a REF or by using another type).
-
ORA-04061: existing state of string has been invalidated
-
Cause: Attempt to resume the execution of a stored procedure using the existing state which has become invalid or inconsistent with the stored procedure because the procedure has been altered or dropped.
-
Action: Try again; this error should have caused the existing state of all packages to be re-initialized.
-
ORA-04063: string has errors
-
Cause: Attempt to execute a stored procedure or use a view that has errors. For stored procedures, the problem could be syntax errors or references to other, non-existent procedures. For views, the problem could be a reference in the view's defining query to a non-existent table. Can also be a table which has references to non-existent or inaccessible types.
-
Action: Fix the errors and/or create referenced objects as necessary.
-
ORA-04086: trigger description too long, move comments into triggering code
-
Cause: The trigger description is limited to 2000 characters (for dictionary storage reasons). The description does not include the text of the "when" clause or the text of the pl/sql code executed for the trigger.
-
Action: If the trigger description contains a large comment, move that
-
ORA-04091: table string.string is mutating, trigger/function may not see it
-
Cause: A trigger (or a user defined plsql function that is referenced in this statement) attempted to look at (or modify) a table that was in the middle of being modified by the statement which fired it.
-
Action: Rewrite the trigger (or function) so it does not read that table.
-
ORA-04096: trigger 'string' has a WHEN clause which is too large, limit 2K
-
Cause: A trigger's 'when' clause is limited to 2K for dictionary storage reasons. The trigger being created exceeded that size.
-
Action: Use a smaller 'when' clause. Note, the trigger body could be used to perform the same limiting action as the 'when' clause.
-
ORA-04098: trigger 'string.string' is invalid and failed re-validation
-
Cause: A trigger was attempted to be retrieved for execution and was found to be invalid. This also means that compilation/authorization failed for the trigger.
-
Action: Options are to resolve the compilation/authorization errors, disable the trigger, or drop the trigger.
-
ORA-04099: trigger 'string' is valid but not stored in compiled form
-
Cause: A trigger was attempted to be retrieved for execution and was found to be valid, but not stored. This may mean the an upgrade was done improperly from a non-stored trigger release.
-
Action: Alter compile the trigger to create the trigger in stored form. Also, you may want to review that a proper upgrade was done.
扫一扫
2732
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
