- ORA-02140: invalid tablespace name
- Cause: An identifier does not follow ALTER TABLESPACE.
- Action: Specify a tablespace name following ALTER TABLESPACE.
- 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 dependents. There could be a substitutable column of a supertype of the type being dropped.
- Action: Drop all type(s) and table(s) depending on the type, then retry the operation using the VALIDATE option, or use 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-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-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-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.
- 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.
- 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.
- ORA-04930: open sequence number failed or initial state is valid
- Cause: Either Shared Sequence Number OS component was not installed properly, or an MC hardware failure may have occurred or a previous instance was not shut down properly.
- Action: Verify that there are no background or foreground Oracle processes from a previous instance on this node using the OS command ps -ef|grep
. Verify that there are no shared memory segments belonging to the user which owns the Oracle installation by isuing the ipcs -b OS command. If there are shared memory segments or processes still on the system, use svrmgrl to shutdown the instance with the abort option. If the instance is not up, verify that the cluster software and/or the hardware is installed and working. Log in as superuser and issue the cnxshow command. Are all of the nodes in the cluster listed? Are they members of the cluster? Is the communications between nodes okay? If the answer to any of these questions is false, contact Digital's customer support organization.
- ORA-04931: unable to set initial sequence number value
- Cause: A call to the SSN failed to set the sequence number to its initial value, possibly caused by an MC hardware problem.
- Action: Verify that the MC hardware is functioning properly. If it is not, contact Digital's customer support organization. If it is, contact Oracle support.
- ORA-04934: unable to obtain the current sequence number
- Cause: A call to the SSN failed to return its current value. Either there are many errors occurring on the MC hardware, or the sequence number has become invalid and cannot be validated.
- Action: Verify that the MC hardware is functioning properly. If it is, contact Oracle Support.
- ORA-04940: unsupported optimization of Oracle binary, check alert log for more info
- Cause: ORACLE binary has been optimized with unsupported options or a required option has not been used.
- Action: Check the documentation for a list of supported and required flags for the optimizing utility that you used to optimize ORACLE. Shutdown the instance, optimize ORACLE again with supported combination of options and restart the instance.
- ORA-06031: NETDNT: connect failed, unrecognized object name
- Cause: Host string contains reference to object (which doesn't exist): @d:
- => object is ORDN ; when is VMS, the object is ORDN .COM when is UNIX, the object is ORDN @d: ::"task= " => object is ; when is VMS, the object is .COM when is UNIX, the object is - Action: Retry with correct object name or create the required object on host node
- ORA-06034: NETDNT: connect failed, partner exited unexpectedly
- Cause: Connection with host node was made but partner aborted
- Action: Make sure object (see 06031, above) is working (for VMS run the command file and make sure that the ORACLE server process starts up); sometimes happens when the network/node is under stress - in this case a retry often works.
- ORA-06108: NETTCP: connect to host failed
- Cause: Connection attempt to remote host has failed. Probably means that the SQL*Net TCP/IP server on the remote host is not up, or the host itself is not up (check the latter by targeting it with Telnet).
- Action: Start the SQL*Net TCP/IP server process on the remote host.
- ORA-06121: NETTCP: access failure
- Cause: The host's SQL*Net TCP/IP server was unable to test the accessibility of the SID mapping file (specified in CONFIG.ORA) associated with this connection request. See the SQL*Net TCP/IP server log file for more details.
- Action: Contact your customer support representative.
- ORA-06124: NETTCP: timeout waiting for ORASRV
- Cause: The ORACLE server process was started but failed to respond after N secs.
- Action: For heavily loaded systems this is not an uncommon occurrence. Increase the value of N (the default is 30) by placing the following entry in the CONFIG.ORA file: SQLNET ORASRV_WAIT =
which will come into effect the next time the SQL*Net TCP/IP server is started.
- ORA-06125: NETTCP: ORASRV exited unexpectedly
- Cause: The ORACLE server process was started but exited unexpectedly. Possible causes: 1. Insufficient quotas to run ORASRV
2. ORACLE is not installed See the ORASRV output file for more details; the file will be in the ORA_SQLNET directory and will have a name of the form: ORA_SRVTnn_.OUT - Action: If appropriate action is not obvious from the ORASRV output file then contact your customer support representative.
- ORA-06129: NETTCP: unable to transfer socket ownership to ORASRV
- Cause: The host's SQL*Net TCP/IP server was unable to transfer the network communication handle to the ORACLE server process. See the SQL*Net TCP/IP server log file for more details.
- Action: Contact your customer support representative.
- ORA-06130: NETTCP: host access denied
- Cause: The host's SQL*Net TCP/IP server rejected this connection request because the client node does not have access privilege - as determined by the contents of the Valid Node Table (VNT), a component of the host's CONFIG.ORA.
- Action: To grant access, add appropriate entry to the host's VNT.
- ORA-06131: NETTCP: user access denied
- Cause: The host's SQL*Net TCP/IP server rejected this connection request because the client user(name) does not have access privilege - as determined by the contents of the Username Mapping Table (UMT), a component of the host's CONFIG.ORA.
- Action: To grant access, add appropriate entry to the host's UMT.
- ORA-06252: NETNTT: cannot open address file
- Cause: The NTT two-task driver could not open a file containing address information.
- Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. Make sure the instance you are attempting to connect to is actually up and running.
- ORA-06253: NETNTT: cannot read arguments from address file
- Cause: The NTT two-task driver could not read addressing information from its addressing file.
- Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. Make sure the instance you are attempting to connect to is actually up and running.
- ORA-06254: NETNTT: cannot share connection to cube
- Cause: The NTT two-task driver could not share a connection to the cube.
- Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. Make sure the instance you are attempting to connect to is actually up and running.
- ORA-06256: NETNTT: remote fork failed
- Cause: The Oracle listener process on the cube could not fork off a shadow process.
- Action: The instance you are trying to connect to probably doesn't have enough memory to run another shadow process. Ask someone else to log off, or connect to a different instance.
- ORA-06268: NETNTT: cannot read /etc/oratab
- Cause: The NTT two-task driver could not read configuration information from /etc/oratab.
- Action: Make sure /etc/oratab exists and is readable. This error may occur if the file is incorrectly formatted. It also may occur if the driver has run out of memory.
- ORA-06300: IPA: Disconnect failure
- Cause: A fatal error occurred during the disconnect from the server. This was probably caused by inaccessible message queues.
- Action: If there is no message queue, restart the SQL*Net IPA servers using ipactl. Otherwise contact your customer support representative.
- ORA-06318: IPA: Local maximum number of connections exceeded
- Cause: The maximum number of simultaneous connections that SQL*Net IPA can handle to different hosts has been exceeded on the local side.
- Action: Wait for free connections to become available. If the problem persists, contact your system manager.
- ORA-06320: IPA: Remote maximum number of connections exceeded
- Cause: The maximum number of simultaneous connections that SQL*Net IPA can handle from different hosts has been exceeded on the remote side.
- Action: Wait for free connections to become available. If the problem persists, contact your system manager.
- ORA-06321: IPA: Cannot reach the remote side
- Cause: There has been a timeout on an attempt to connect to a remote server the reason for which is most likely to be the remote SQL*Net IPA software is not running. An alternative reason could be that the remote initiator service name is incorrect.
- Action: Check and start the remote SQL*Net software. Check that it is started with the correct service names supplied.
- ORA-06431: ssaio: Invalid Block number
- Cause: The file block number is out of range of the file. The additional information returns the block number.
- Action: Verify that the block number is correct. Run dbfsize and check if the block number is in that range. Contact your Oracle Customer Support Representative.
- ORA-06449: The list IO or the sysvendor is not installed.
- Cause: ORACLE tries to use the sysvendor interface (INIT.ORA parameter use_sysvendor=true) but the UNIX kernel does not have the ORACLE sysvendor interface linked in.
- Action: Set use_sysvendor=false in INIT.ORA, if you don't want to use this interface or link the UNIX kernel with this interface so that ORACLE can use it.
- ORA-06500: PL/SQL: storage error
- Action: 1) Ensure there are no issues or bugs in your PL/SQL program which are causing excessive amounts of memory to be used. 2) Programmatically cause unused objects to be freed (e.g. by setting them to NULL). 3) Increase the amount of shared or process memory (as appropriate) available to you.
- ORA-06502: PL/SQL: numeric or value errorstring
- Cause: An arithmetic, numeric, string, conversion, or constraint error occurred. For example, this error occurs if an attempt is made to assign the value NULL to a variable declared NOT NULL, or if an attempt is made to assign an integer larger than 99 to a variable declared NUMBER(2).
- Action: Change the data, how it is manipulated, or how it is declared so that values do not violate constraints.
- ORA-06504: PL/SQL: Return types of Result Set variables or query do not match
- Cause: Number and/or types of columns in a query does not match declared return type of a result set variable, or declared types of two Result Set variables do not match.
- Action: Change the program statement or declaration. Verify what query the variable actually refers to during execution.
- ORA-06505: PL/SQL: variable requires more than 32767 bytes of contiguous memory
- Cause: A PL/SQL variable was declared with a constraint which required more than 32767 bytes of memory. PL/SQL does not currently support allocations of contiguous memory greater than 32767 bytes.
- Action: Consider reducing the constraint in the variable declaration. If that is not possible, try changing the database or national character set to such, that requires less memory for the same constraint. Note: changing the character set will impact execution of all PL/SQL code.
- ORA-06513: PL/SQL: index for PL/SQL table out of range for host language array
- Cause: An attempt is being made to copy a PL/SQL table to a host language array. But an index in the table is either less than one or greater than the maximum size of the host language array. When copying PL/SQL tables to host language arrays, the table entry at index 1 is placed in the first element of the array, the entry at index 2 is placed in the second element of the array, etc. If an table entry has not been assigned then the corresponding element in the host language array is set to null.
- Action: Increase size of host language array, or decrease size of PL/SQL table. Also make sure that you don't use index values less than 1.
- ORA-06514: PL/SQL: The remote call cannot be handled by the server
- Cause: The remote call has parameters that are cursor variables or lob variables. This cannot be handled by stored procedures on your server.
- Action: Avoid using cursor variables or lob variables as parameters for stored procedures on this server or upgrade your server to a version that supports this.
- ORA-06515: PL/SQL: unhandled exception string
- Cause: An exception was raised by PL/SQL code, but not handled. The exception number is outside the legal range of Oracle errors.
- Action: Fix the problem causing the exception or write an exception handler for this condition. Or you may need to contact your application administrator or DBA.
- ORA-06516: PL/SQL: the Probe packages do not exist or are invalid
- Cause: A Probe operation, probably an attempt to initialize the ORACLE server to debug PL/SQL, could not be completed because the Probe packages were not loaded or have become invalid.
- Action: DBA should load the Probe packages. This can be done by running the pbload.sql script supplied with the RDBMS.
- ORA-06519: active autonomous transaction detected and rolled back
- Cause: Before returning from an autonomous PL/SQL block, all autonomous transactions started within the block must be completed (either committed or rolled back). If not, the active autonomous transaction is implicitly rolled back and this error is raised.
- Action: Ensure that before returning from an autonomous PL/SQL block, any active autonomous transactions are explicitly committed or rolled back. ----------------------------------------------------------------------- 06520 through 06529 reserved for Foreign function errors
- ORA-06525: Length Mismatch for CHAR or RAW data
- Cause: The length specified in the length variable has an illegal value. This can happen if you have requested requested a PL/SQL INOUT, OUT or RETURN raw variable to be passed as a RAW with no corresponding length variable. This error can also happen if there is a mismatch in the length value set in the length variable and the length in the orlvstr or orlraw.
- Action: Correct the external procedure code and set the length variable correctly.
- ORA-06527: External procedure SQLLIB error: string
- Cause: An error occurred in sqllib during execution of a Pro* external procedure.
- Action: The message text indicates the actual SQLLIB error that occurred. Consult the Oracle Error Messages and Codes manual for a complete description of the error message and follow the appropriate action.
- ORA-06529: Version mismatch - PL/SQL profiler
- Cause: The PL/SQL profiler package (dbmspb.sql, prvtpbp.plb) does not match the version of the code in the server implementing the profiler.
- Action: Run the package profload.sql in $ORACLE_HOME/rdbms/admin to load the correct version of the PL/SQL profiler packages
- ORA-06531: Reference to uninitialized collection
- Cause: An element or member function of a nested table or varray was referenced (where an initialized collection is needed) without the collection having been initialized.
- Action: Initialize the collection with an appropriate constructor or whole-object assignment.
- ORA-06534: Cannot access Serially Reusable package string
- Cause: The program attempted to access a Serially Reusable package in PL/SQL called from SQL context (trigger or otherwise). Such an access is currently unsupported.
- Action: Check the program logic and remove any references to Serially Reusable packages (procedure, function or variable references) which might happen in PL/SQL called from sql context (trigger or otherwise).
- ORA-06538: statement violates string RESTRICT_REFERENCES pragma
- Cause: The program attempted to execute a dynamic statement which does not meet the purity level specified (in the pragma RESTRICT_REFERENCES directive) for the module executing the statement.
- Action: Ensure that the dynamic statement meets the purity level specified for the module executing the statement.
- ORA-06539: target of OPEN must be a query
- Cause: The program attempted to perform an OPEN cursor operation on a dynamic statement that was not a query.
- Action: Ensure that the OPEN cursor operation is done on a dynamic query statement. -------------------------------------------------------- 06540 through 06549 reserved for pl/sql error handling
- ORA-06541: PL/SQL: compilation error - compilation aborted
- Cause: A pl/sql compilation error occurred and the compilation was aborted; but the compilation unit was written out to the backing store. However, unlike ora-06545, the user generally will not see this error message. Instead, there will be accompanying PLS-nnnnn error messages.
- Action: See accompanying PLS-nnnnn error messages.
- ORA-06545: PL/SQL: compilation error - compilation aborted
- Cause: A pl/sql compilation error occurred and the compilation was aborted completely without the compilation unit being written out to the backing store. Unlike ora-06541, the user will always see this error along with the accompaning PLS-nnnnn error messages.
- Action: See accompanying PLS-nnnnn error messages.
- ORA-06546: DDL statement is executed in an illegal context
- Cause: DDL statement is executed dynamically in illegal PL/SQL context. - Dynamic OPEN cursor for a DDL in PL/SQL
- Bind variable's used in USING clause to EXECUTE IMMEDIATE a DDL
- Define variable's used in INTO clause to EXECUTE IMMEDIATE a DDL - Action: Use EXECUTE IMMEDIATE without USING and INTO clauses to execute the DDL statement.
- ORA-06547: RETURNING clause must be used with INSERT, UPDATE, or DELETE statements
- Cause: EXECUTE IMMEDIATE with a RETURNING clause is used to execute dynamic UPDATE, INSERT, or DELETE statements only.
- Action: use RETURNING clause in EXECUTE IMMEDIATE for INSERT, UPDATE, or DELETE statements only. For other statements, use USING clause instead.
- ORA-06554: package DBMS_STANDARD must be created before using PL/SQL
- Cause: The DBMS specific extensions to PL/SQL's package "STANDARD" are in package "DBMS_STANDARD". This package must be created before using PL/SQL.
- Action: Create package "DBMS_STANDARD". The source for this PL/SQL stored package is provided with the distribution.
- ORA-06559: wrong datatype requested, string, actual datatype is string
- Cause: The sender put different datatype on the pipe than that being requested (package 'dbms_pipe'). The numbers are: 6 - number, 9 - char, 12 - date.
- Action: Check that the sender and receiver agree on the number and types of items placed on the pipe.
- ORA-06561: given statement is not supported by package DBMS_SQL
- Cause: Attempting to parse an unsupported statement using procedure PARSE provided by package DBMS_SQL.
- Action: Only statements which begin with SELECT, DELETE, INSERT, UPDATE, LOCK, BEGIN, DECLARE or << (PL/SQL label delimiter) are supported.
- ORA-06562: type of out argument must match type of column or bind variable
- Cause: Attempting to get the value of a column or a bind variable by calling procedure COLUMN_VALUE or VARIABLE_VALUE of package DBMS_SQL but the type of the given out argument where to place the value is different from the type of the column or bind variable that was previously defined by calling procedure DEFINE_COLUMN (for defining a column) or BIND_VARIABLE (for binding a bind variable) of package DBMS_SQL.
- Action: Pass in an out argument of the correct type when calling procedure COLUMN_VALUE or VARIABLE_VALUE. The right type is the type that was provided when defining the column or binding the bind variable.
- ORA-06563: top level procedure/function specified, cannot have subparts
- Cause: The name to be resolved was specified with three parts (a.b.c) but the a.b part resolves to a top level procedure or function (which don't have nested procedures). This can also happen with a two-part name, a.b, where a is a synonym for a top level package or procedure.
- Action: Specify a procedure/function within a package, or a top level procedure/function.
- ORA-06566: invalid number of rows specified
- Cause: An invalid number of rows was specified in a call to the procedure DEFINE_COLUMN in the package DBMS_SQL. For a given parsed statement in a given cursor, all columns must be defined to have the same number of rows, so all the calls to DEFINE_COLUMN must specify the same number of rows.
- Action: Specify a number that matches that for previously defined columns.
- ORA-06567: invalid number of values specified
- Cause: An invalid number of values to be bound was specified in a call to the procedure BIND_VARIABLE in the package DBMS_SQL. In order to execute a given parsed statement in a given cursor, the same number of values must have been bound for all bind variables, so when EXECUTE is called, the latest calls to BIND_VARIABLE must must have specified the same number of values to be bound for all bind variables.
- Action: Make sure that the same number of values have been bound for all of the bind variables.
- ORA-06568: obsolete ICD procedure called
- Cause: An obsolete ICD procedure was called by a PL/SQL program. The PL/SQL program was probably written for an eralier release of RDBMS.
- Action: Make sure that all PL/SQL programs have been upgraded to the latest release of the RDBMS. This can be accomplished by following upgrade instructions in the README file, or by running the catproc.sql script supplied with the RDBMS.
- ORA-06569: Collection bound by bind_array contains no elements
- Cause: A collection with zero elements was bound to a bind variable in a call to procedure BIND_ARRAY in the package DBMS_SQL. In order to execute a bind of a collection, the collection must contain at least one element. If no elements are present then at execute time there will be no value for this bind and the statement is meaningless.
- Action: Fill the collection with the elements you want to bind and try the bind call again.
- ORA-06571: Function string does not guarantee not to update database
- Cause: There are two possible causes for this message: * A SQL statement references a packaged, PL/SQL function that does not contain a pragma that prevents the database from being updated.
* A SQL statement references a stand-alone, PL/SQL function that contains an instruction to update the database. - Action: If the referenced function is a packaged, PL/SQL function: Recreate the PL/SQL function with the required pragma; be certain to include the 'Write No Database State' (WNDS) argument in the argument list of the pragma. If the referenced function is a stand-alone, PL/SQL function: Do not use the function.
- ORA-06572: Function string has out arguments
- Cause: A SQL statement references either a packaged, or a stand-alone, PL/SQL function that contains an OUT parameter in its argument list. PL/SQL functions referenced by SQL statements must not contain the OUT parameter.
- Action: Recreate the PL/SQL function without the OUT parameter in the argument list.
- ORA-06573: Function string modifies package state, cannot be used here
- Cause: There are two possible causes for this message: * A SQL statement references a packaged, PL/SQL function that does not contain a pragma containing the 'Write no Package State' (WNPS).
* A SQL statement references a stand-alone, PL/SQL function that modifies a package state. A stand-alone, PL/SQL function referenced by a SQL statement cannot modify a package state. - Action: If the function is a packaged, PL/SQL function: Recreate the function and include a pragma containing the 'Write no Package State' (WNPS). If the function is a stand-alone, PL/SQL function: Delete the function from the SQL statement.
- ORA-06574: Function string references package state, cannot execute remotely
- Cause: There are two possible causes for this message: * A remote, packaged function or a remote-mapped, local, packaged function that does not contain a pragma with the 'Write no Package State' (WNPS) and 'Read no Package State' (RNPS) arguments references a package state.
* A remote, stand-alone function or a remote-mapped, local, stand-alone function contains a reference to a package state (reads or writes a package variable). Only local functions that are referenced in a SELECT list, VALUES clause of an INSERT statement, or SET clause of an UPDATE statement can modify a package state. - Action: If the function is a packaged function: Recreate the function and include a pragma containing the 'Write no Package State' (WNPS) and 'Read no Package State' (RNPS) arguments. If the function is a stand-alone function: Do not call the function.
- ORA-06575: Package or function string is in an invalid state
- Cause: A SQL statement references a PL/SQL function that is in an invalid state. Oracle attempted to compile the function, but detected errors.
- Action: Check the SQL statement and the PL/SQL function for syntax errors or incorrectly assigned, or missing, privileges for a referenced object.
- ORA-06580: Hash Join ran out of memory while keeping large rows in memory
- Cause: Hash Join reserves 3 slots (each slot size = DB_BLOCK_SIZE * HASH_JOIN_MULTIBLOCK_IO_COUNT) for a row. If a row is larger than that, this error will be raised.
- Action: Increase HASH_JOIN_MULTIBLOCK_IO_COUNT so that each joined row fits in a slot. HASH_AREA_SIZE may also need to be increaed.
- ORA-06595: REF CURSOR parameters are not supported in forwarded RPC calls
- Cause: An attempt was made to make a forwarded RPC call with a REF CURSOR parameter.
- Action: Either call the remote function directly (i.e., not by way of forwarding), or move the remote function to a database where it can be called directly.
- ORA-06616: LU6.2 Driver: Attach to LU failed
- Cause: The SQL*Net LU6.2 driver was unable to attach to the LU specified in the connect string, or was unable to attach to the default LU.
- Action: Check that the LU name specified in the connect string, or the default LU name if no LU was specified, is correctly configured and operational.
- ORA-06706: TLI Driver: service not found
- Cause: TLI could not find service information for the specified service name.
- Action: If you specified the service name on the command line or with the environment variable TLI_SERVER, make sure you specified it correctly. If the service name is not in the SERVICES file for your protocol, ask your system adminstrator to add it.
- ORA-06707: TLI Driver: connection failed
- Cause: TLI failed to establish the connection to a SQL*Net TCP/IP server due to an error encountered by the remote server, which has supplied a string describing the remote error.
- Action: See the SQL*Net TCP/IP User's Guide section "orasrv Messages" for the specific cause and action.
- ORA-06745: TLI Driver: listener already running
- Cause: The network address on which the TLI server awaits connection requests is in use, possibly because the server is already running.
- Action: Ensure that the TLI server is not already running. If it is not running and this error message recurs, contact your customer support representative.
- ORA-06792: TLI Driver: server cannot exec oracle
- Cause: The remote TLI server was unable to start an ORACLE process on behalf of the client.
- Action: Note the operating system error message or number and contact your system adminstrator. The permissions on the remote ORACLE program may be set incorrectly.
- ORA-06793: TLI Driver: server cannot create new process
- Cause: The remote TLI server was unable to start an ORACLE process on behalf of the client.
- Action: Note the operating system error message or number and contact your system adminstrator. The remote host may be unable to create any new processes due to a full process table.
- ORA-06802: TLI Driver: could not open the /etc/netware/yellowpages file
- Cause: The /etc/netware/yellowpages file does not exist, or is not readable by the TLI listener process.
- Action: Insure the file exists and is readable. Make sure that the server machine's node name, network number, ethernet address, and listening socket number are encoded in the file.
- ORA-06807: TLI Driver: could not open ethernet device driver file
- Cause: The file /dev/eth does not exist, or the driver it references could not be opened.
- Action: The system's real ethernet device file, for example /dev/wd, for the Western Digital ethernet driver, should be linked to the file /dev/eth. If this has been done, insure that the ethernet driver has been installed by completing the TCP/IP installation on your system, and testing a connection. If problem continues, contact your customer support representative for a list of supported ethernet drivers.
- ORA-06808: TLI Driver: could not link IPX and ethernet streams
- Cause: Either the ethernet driver has not been installed in the system correctly, or the ethernet driver is not supported.
- Action: Insure that the ethernet driver has been installed by completing the TCP/IP installation on your system, and testing a connection. If problem continues, contact your customer support representative for a list of supported ethernet drivers.
- ORA-06811: TLI Driver: could not set the IPX network number at init
- Cause: The IPX driver has not been correctly installed, or the network number encoded in the /etc/netware/yellowpages file is invalid.
- Action: The network number in the yellowpages file should match the four-byte network number of your Novell file server. If this is configured correctly, reinvoke the Oracle root installation. If problem continues, contact your customer support representative.
- ORA-06813: TLI Driver: the configured ethernet address is incorrect
- Cause: The node address read from the ethernet driver does not match the value encoded in the /etc/netware/yellowpages file for this server.
- Action: Confirm the correct ethernet node address for your LAN card, and enter this value in the yellowpages file.
- ORA-06817: TLI Driver: could not read the Novell network address
- Cause: The file $ORACLE_HOME/spx/address could not be opened for reading and writing.
- Action: Make sure ORACLE_HOME is set, and the permissions on the ORACLE_HOME are read, write. If this file has been unintentially deleted, run spxctl (net option) to reset the configured Novell network number for SQL*Net SPX.
- ORA-07204: sltln: name translation failed due to lack of output buffer space.
- Cause: The sltln routine is given a maximum length buffer to expand the name into. An overflow of this buffer occurred.
- Action: Possible internal error. Check output buffer length stored in sercose[0]. Pathnames are limited to 255 characters.
- ORA-07221: slspool: exec error, unable to start spooler program.
- Cause: Exec failed when starting line printer spooler command. Likely that either the default line printer command, or ORACLE_LPPROG, is incorrectly set.
- Action: Verify default line printer command and ORACLE_LPPROG are set correctly. Set ORACLE_LPPROG to working line printer spooler.
- ORA-07222: slspool: line printer spooler command exited with an error.
- Cause: The line printer spooler exited with a non-zero return value. This probably indicates an error in spooling file.
- Action: Verify that line printer spooler is up. Verify that ORACLE_LPPROG, and ORACLE_LPARG are set properly. Check exit value returned as additional informatin.
- ORA-07250: spcre: semget error, unable to get first semaphore set.
- Cause: An error occurred when trying to get first semaphore set.
- Action: Check errno. Verify that system is configured to have semaphores. Verify that enough semaphores are available. Additional information indicates how many semaphores were requested.
- ORA-07251: spcre: semget error, could not allocate any semaphores.
- Cause: Semget failed to even allocate a single semaphore. Either they are all in use or the system is not configured to have any semaphores.
- Action: Check to see if all semaphores are in use. Check to see if system is configured to have semaphores. Check errno.
- ORA-07252: spcre: semget error, could not allocate semaphores.
- Cause: Semget system call returned an error. Possible resource limit problem.
- Action: Check errno. Verify that enough semaphores are available in system. If additional errors occur in destroying the semaphore sets then sercose[0] will be non-zero. If this occurs, remove the semaphore sets using ipcrm.
- ORA-07264: spwat: semop error, unable to decrement semaphore.
- Cause: Semop system call returned an error. Semaphore set may not exist.
- Action: Check errno. Semaphore ID is returned in sercose[0]. Verify semaphore set exists. A possible cause for this error is that a "shutdown abort" was done while this process was running.
- ORA-07265: sppst: semop error, unable to increment semaphore.
- Cause: Semop system call returned an error. Semaphore set may not exist.
- Action: Check errno. Semaphore ID is returned in sercose[0]. Check semaphore set existence. A possible cause for this error is that a "shutdown abort" was done while this process was running.
- ORA-07269: spdcr: detached process died after exec.
- Cause: Detached process succesfully execed, but died shortly thereafter. Additional information indicates exit code, and termination status.
- Action: Check termination code for information as to why process exited. Check for core dump or trace file.
- ORA-07279: spcre: semget error, unable to get first semaphore set.
- Cause: An error occurred when trying to get first semaphore set.
- Action: Check errno. Verify that system is configured to have semaphores. Verify that enough semaphores are available. Additional information indicates how many semaphores were requested.
- ORA-07404: sfareq: Timeout occurred waiting for request to complete.
- Cause: The master database writer timed out waiting for a write or close to complete. One of the database writers may have stopped running.
- Action: Check all database writer trace files. Shut down the database and try to warm start.
- ORA-07416: slpath: pathname construction failed; lack of output buffer space.
- Cause: The slpath routine is given a maximum length buffer to expand the name into. An overflow of this buffer occurred.
- Action: Possible internal error. Check output buffer length stored in sercose[0] and constructed pathname length in sercose[1].
- ORA-07457: cannot set _INTERNAL_RESOURCE_MANAGER_PLAN because of FORCE
- Cause: An attempt was made to set the _INTERNAL_RESOURCE_MANAGER_PLAN parameter, however this failed because the current RESOURCE_MANAGER_PLAN has the FORCE prefix.
- Action: Remove the FORCE prefix from the RESOURCE_MANAGER_PLAN parameter.
- ORA-07459: cannot restore the RESOURCE_MANAGER_PLAN parameter
- Cause: An attempt was made to internally restore the RESOURCE_MANAGER_PLAN parameter to the value before it was internally set. This failed because the current plan was set by the user and therefore did not need to be restored.
- Action: No action needed.
