Oracle Database Server Messages(一)

Skip Headers

Oracle9i Database Error Messages
Release 2 (9.2)
Part Number A96525-01
Home
Book List
Contents
Index
Master Index
Feedback

---

Part II
Oracle Database Server Messages

This part contains the following chapters:

• Chapter 2, "ORA-00000 to ORA-00899"
• Chapter 3, "ORA-00900 to ORA-01499"
• Chapter 4, "ORA-01500 to ORA-02099"
• Chapter 5, "ORA-02100 to ORA-04099"
• Chapter 6, "ORA-04100 to ORA-07499"
• Chapter 7, "ORA-07500 to ORA-09857"
• Chapter 8, "ORA-09858 to ORA-12299"
• Chapter 9, "ORA-12300 to ORA-12399"
• Chapter 10, "ORA-12400 to ORA-12699"
• Chapter 11, "ORA-12700 to ORA-19399"
• Chapter 12, "ORA-19400 to ORA-24279"
• Chapter 13, "ORA-24280 to ORA-29249"
• Chapter 14, "ORA-29250 to ORA-32799"

---

Copyright © 1996, 2002 Oracle Corporation.
All Rights Reserved.

Home

Book List

Contents

Index

Master Index

Feedback

 

 

Skip Headers

Oracle9i Database Error Messages
Release 2 (9.2)
Part Number A96525-01
Home
Book List
Contents
Index
Master Index
Feedback

---

 

2
ORA-00000 to ORA-00899

ORA-00000 normal, successful completion

Cause: An operation has completed normally, having met no exceptions.

Action: No action required.

ORA-00001 unique constraint (string.string) violated

Cause: An UPDATE or INSERT statement attempted to insert a duplicate key.

Action: Either remove the unique restriction or do not insert the key.

ORA-00017 session requested to set trace event

Cause: The current session was requested to set a trace event by another session.

Action: This is used internally; no action is required.

ORA-00018 maximum number of sessions exceeded

Cause: All session state objects are in use.

Action: Increase the value of the SESSIONS initialization parameter.

ORA-00019 maximum number of session licenses exceeded

Cause: All licenses are in use.

Action: Increase the value of the LICENSE MAX SESSIONS initialization parameter.

ORA-00020 maximum number of processes (string) exceeded

Cause: All process state objects are in use.

Action: Increase the value of the PROCESSES initialization parameter.

ORA-00021 session attached to some other process; cannot switch session

Cause: The user session is currently used by others.

Action: Do not switch to a session attached to some other process.

ORA-00022 invalid session ID; access denied

Cause: Either the session specified does not exist or the caller does not have the privilege to access it.

Action: Specify a valid session ID that you have privilege to access, that is either you own it or you have the CHANGE_USER privilege.

ORA-00023 session references process private memory; cannot detach session

Cause: An attempt was made to detach the current session when it contains references to process private memory.

Action: A session may contain references to process memory (PGA) if it has an open network connection, a very large context area, or operating system privileges. To allow the detach, it may be necessary to close the session's database links and/or cursors. Detaching a session with operating system privileges is always disallowed.

ORA-00024 logins from more than one process not allowed in single-process mode

Cause: An attempt was made to log in more than once from different processes for Oracle started in single-process mode.

Action: Log off from the other process.

ORA-00025 failed to allocate string

Cause: An application failed because Oracle ran out of memory.

Action: Restart Oracle with a larger SGA heap.

ORA-00026 missing or invalid session ID

Cause: The session ID string specified in the ALTER SYSTEM KILL SESSION command was invalid, or no string was specified.

Action: Retry the command with a valid session ID.

ORA-00027 cannot kill current session

Cause: An attempt was made to use ALTER SYSTEM KILL SESSION to kill the current session.

Action: If it is necessary to kill the current session, do so from another session.

ORA-00028 your session has been killed

Cause: A privileged user killed the session and it is no longer logged in to the database.

Action: Contact the database administrator. The administrator may be attempting to perform an operation that requires users to be logged out. When the database administrator announces that the database is available, log in and resume work.

ORA-00029 session is not a user session

Cause: The session ID specified in an ALTER SYSTEM KILL SESSION command was not a user session. For example, the session may be recursively started.

Action: Retry the command with a valid session ID.

ORA-00030 User session ID does not exist.

Cause: The user session ID no longer exists, probably because the session was logged out.

Action: Use a valid session ID.

ORA-00031 session marked for kill

Cause: The session specified in an ALTER SYSTEM KILL SESSION command cannot be killed immediately because the session is involved in a non-interruptible operation (for example, rolling back a transaction or being blocked by a network operation). The session has been marked to be killed as soon as possible after the current operation is done.

Action: No action is required for the session to be killed, but further executions of the ALTER SYSTEM KILL SESSION command on this session may cause the session to be killed sooner.

ORA-00032 invalid session migration password

Cause: The session migration password specified in a session creation call was invalid (probably too long).

Action: Retry with a valid password (less than 30 characters).

ORA-00033 current session has empty migration password

Cause: An attempt was made to detach or clone the current session and it has an empty migration password. This is not allowed.

Action: Create the session with a non-empty migration password.

ORA-00034 cannot string in current PL/SQL session

Cause: An attempt was made to issue a commit or rollback from a PL/SQL object (procedure, function, package) in a session that has this disabled by a ALTER SESSION DISABLE COMMIT IN PROCEDURE statement.

Action: Enable commits from PL/SQL in this session, or do not attempt to use commit or rollback in PL/SQL when they are disabled in the current session.

ORA-00035 LICENSE_MAX_USERS cannot be less than current number of users

Cause: Specified values for LICENSE_MAX_USERS is less than the current number of users.

Action: Check the license limit and drop extra users or purchase more licenses.

ORA-00036 maximum number of recursive SQL levels (string) exceeded

Cause: An attempt was made to go more than the specified number of recursive SQL levels.

Action: Remove the recursive SQL, possibly a recursive trigger.

ORA-00037 cannot switch to a session belonging to a different server group

Cause: An attempt was made to switch to a session in a different server group. This is not allowed.

Action: Make sure the server switches to a session that belongs to its server group.

ORA-00038 Cannot create session: server group belongs to another user

Cause: An attempt was made to create a non-migratable session in a server group that is owned by a different user.

Action: A server group is owned by the first user who logs into a server in the server group in non-migratable mode. All subsequent non-migratable mode logins must be made by the user who owns the server group. To have a different user log in non-migratable mode, the ownership of the server group will have to be changed. This can be done by logging off all current sessions and detaching from all existing servers in the server group and then having the new user login to become the new owner.

ORA-00050 operating system error occurred while obtaining an enqueue

Cause: Could not obtain the operating system resources necessary to cover an Oracle enqueue. This is normally the result of an operating system user quota that is too low.

Action: Look up the operating system error in your system documentation and perform the needed action.

ORA-00051 timeout occurred while waiting for a resource

Cause: This message is usually caused by an instance that has terminated abnormally.

Action: Restart any non-recovered instances.

ORA-00052 maximum number of enqueue resources (string) exceeded

Cause: Ran out of enqueue resources.

Action: Increase the value of the ENQUEUE_RESOURCES initialization parameter.

ORA-00053 maximum number of enqueues exceeded

Cause: Ran out of enqueue state objects.

Action: Increase the value of the ENQUEUES initialization parameter.

ORA-00054 resource busy and acquire with NOWAIT specified

Cause: The NOWAIT keyword forced a return to the command prompt because a resource was unavailable for a LOCK TABLE or SELECT FOR UPDATE command.

Action: Try the command after a few minutes or enter the command without the NOWAIT keyword.

ORA-00055 maximum number of DML locks exceeded

Cause: Ran out of DML lock state objects.

Action: Increase the value of the DML_LOCKS initialization parameter and restart Oracle.

ORA-00056 DDL lock on object 'string.string' is already held in an incompatible mode

Cause: The attempted lock is incompatible with the DDL lock already held on the object. This happens if you attempt to drop a table that has parse locks.

Action: Before attempting to drop a table, check that it has no parse locks. Wait a few minutes before retrying the operation.

ORA-00057 maximum number of temporary table locks exceeded

Cause: The number of temporary tables equals or exceeds the number of temporary table locks. Temporary tables are often created by large sorts.

Action: Increase the value of the TEMPORARY_TABLE_LOCKS initialization parameter and restart Oracle.

ORA-00058 DB_BLOCK_SIZE must be string to mount this database (notstring)

Cause: The value of the DB_BLOCK_SIZE initialization parameter used to start this database does not match the value used when that database was created. Potential reasons for this mismatch are:

• mounting the wrong database
• using the wrong initialization parameter file
• the value of the DB_BLOCK_SIZE parameter was changed

Action: For one of the above causes, either:

• mount the correct database
• use the correct initialization parameter file
• correct the value of the DB_BLOCK_SIZE parameter

ORA-00059 maximum number of DB_FILES exceeded

Cause: The value of the DB_FILES initialization parameter was exceeded.

Action: Increase the value of the DB_FILES parameter and restart Oracle.

ORA-00060 deadlock detected while waiting for resource

Cause: Your session and another session are waiting for a resource locked by the other. This condition is known as a deadlock. To resolve the deadlock, one or more statements were rolled back for the other session to continue work.

Action: Either:

• Enter a ROLLBACK statement and re-execute all statements since the last commit or
• Wait until the lock is released, possibly a few minutes, and then re-execute the rolled back statements.

ORA-00061 another instance has a different DML_LOCKS setting

Cause: The shared instance being started is using DML locks, and the running instances are not, or vice-versa.

Action: Either:

• Do not use DML_LOCKS by setting DML_LOCKS to zero at all instances or
• Use DML_LOCKS by setting DML_LOCKS to a positive integer at all instances.

ORA-00062 DML full-table lock cannot be acquired; DML_LOCKS is 0

Cause: The instance was started with the value of DML_LOCKS set to zero, and the statement being executed needs a full-table lock (S, X, or SSX).

Action: Restart the instance with DML_LOCKS not equal to zero, and re-execute the statement.

ORA-00063 maximum number of LOG_FILES exceeded

Cause: The value of the LOG_FILES initialization parameter was exceeded.

Action: Increase the value of the LOG_FILES initialization parameter and restart Oracle. The value of the parameter needs to be as large as the highest number of log files that currently exist rather than just the count of logs that exist.

ORA-00064 object is too large to allocate on this O/S (string,string)

Cause: An initialization parameter was set to a value that required allocating more contiguous space than can be allocated on this operating system.

Action: Reduce the value of the initialization parameter.

ORA-00065 initialization of FIXED_DATE failed

Cause: The FIXED_DATE string was not in date format yyyy-mm-dd:hh24:mi:ss.

Action: Make sure the initialization parameter is in the correct date format.

ORA-00066 LOG_FILES is string but needs to be string to be compatible

Cause: The maximum number of log files supported by this instance is not the same as for the other instances. All instances must be able to open all the files any instance can open.

Action: Change the value of the LOG_FILES initialization parameter to be compatible.

ORA-00067 invalid value string for parameter string; must be at least string

Cause: The value for the initialization parameter is invalid.

Action: Choose a value as indicated by the message.

ORA-00068 invalid value string for parameter string, must be between string and string

Cause: The value for the initialization parameter is invalid.

Action: Choose a value as indicated by the message.

ORA-00069 cannot acquire lock -- table locks disabled for string

Cause: A command was issued that tried to lock the table indicated in the message. Examples of commands that can lock tables are: LOCK TABLE, ALTER TABLE... ADD (...), and so on.

Action: Use the ALTER TABLE... ENABLE TABLE LOCK command, and retry the command.

ORA-00070 command string is not valid

Cause: An invalid debugger command was specified.

Action: Type HELP to see the list of available commands.

ORA-00071 process number must be between 1 and string

Cause: An invalid process number was specified.

Action: Specify a valid process number.

ORA-00072 process "string" is not active

Cause: An invalid process was specified.

Action: Specify a valid process.

ORA-00073 command string takes between string and string argument(s)

Cause: An incorrect number of arguments was specified.

Action: Specify the correct number of arguments. Type HELP to see the list of commands and their syntax.

ORA-00074 no process has been specified

Cause: No debug process has been specified.

Action: Specify a valid process.

ORA-00075 process "string" not found in this instance

Cause: The specified process was not logged on to the current instance.

Action: Specify a valid process.

ORA-00076 dump string not found

Cause: An attempt was made to invoke a dump that does not exist.

Action: Type DUMPLIST to see the list of available dumps.

ORA-00077 dump string is not valid

Cause: An attempt was made to invoke an invalid dump.

Action: Try another dump.

ORA-00078 cannot dump variables by name

Cause: An attempt was made to dump a variable by name on a system that does not support this feature.

Action: Try the PEEK command.

ORA-00079 variable string not found

Cause: An attempt was made to dump a variable that does not exist.

Action: Use a valid variable name.

ORA-00080 invalid global area specified by level string

Cause: An attempt was made to dump an invalid global area.

Action: Use level 1 for the PGA, 2 for the SGA, and 3 for the UGA. Useextra + level to dump global area level as well asextra bytes for every pointer; extra must be a multiple of 4.

ORA-00081 address range [string, string) is not readable

Cause: An attempt was made to read/write an invalid memory address range.

Action: Try another address or length.

ORA-00082 memory size of string is not in valid set of [1], [2], [4]stringstringstringstringstring

Cause: An invalid length was specified for the POKE command.

Action: Use a valid length (either 1, 2, 4, or possibly 8).

ORA-00083 warning: possibly corrupt SGA mapped

Cause: Even though there may be SGA corruptions, the SGA was mapped.

Action: Use the DUMPSGA command to dump the SGA.

ORA-00084 global area must be PGA, SGA, or UGA

Cause: An attempt was made to dump an invalid global area.

Action: Specify either PGA, SGA, or UGA.

ORA-00085 current call does not exist

Cause: An invalid attempt was made to dump the current call heap.

Action: Wait until the process starts a call.

ORA-00086 user call does not exist

Cause: An invalid attempt was made to dump the user call heap.

Action: Wait until the process starts a call.

ORA-00087 command cannot be executed on remote instance

Cause: Cluster database command issued for non cluster database ORADEBUG command.

Action: Issue the command without the cluster database syntax.

ORA-00088 command cannot be executed by shared server

Cause: A debug command was issued on a shared server.

Action: Reissue the command using a dedicated server.

ORA-00089 invalid instance number in ORADEBUG command

Cause: An invalid instance number was specified in a cluster database ORADEBUG command.

Action: Reissue the command with valid instance numbers.

ORA-00090 failed to allocate memory for cluster database ORADEBUG command

Cause: Could not allocate memory needed to execute cluster database oradebug.

Action: Reissue the command on each instance with single-instance ORADEBUG.

ORA-00091 LARGE_POOL_SIZE must be at least string

Cause: The value of LARGE_POOL_SIZE is below the minimum size.

Action: Increase the value of LARGE_POOL_SIZE past the minimum size.

ORA-00092 LARGE_POOL_SIZE must be greater than LARGE_POOL_MIN_ALLOC

Cause: The value of LARGE_POOL_SIZE is less than the value of LARGE_POOL_MIN_ALLOC.

Action: Increase the value of LARGE_POOL_SIZE past the value of LARGE_POOL_MIN_ALLOC.

ORA-00093 string must be between string and string

Cause: The parameter value is not in a valid range.

Action: Modify the parameter value to be within the specified range.

ORA-00094 string requires an integer value

Cause: The parameter value is not an integer.

Action: Modify the parameter value to be an integer.

ORA-00096 invalid value string for parameter string, must be from among string

Cause: The value for the initialization parameter is invalid.

Action: Choose a value as indicated by the message.

ORA-00097 use of Oracle SQL feature not in SQL92 string Level

Cause: An attempt was made to use an Oracle SQL feature that is not compliant with the SQL92 standard.

Action: Do not use the feature or use the ALTER SESSION SET FLAGGER command to set the appropriate level of SQL92 compliance.

ORA-00099 timed out while waiting for resource, potential PDML deadlock

Cause: The resource needed by the transaction was busy. The PDML transaction could not acquire the resource within the specified amount of time. This indicates potential deadlock involving this PDML transaction and other transactions currently running in the system.

Action: Increase the value of the PARALLEL_TRANSACTION_RESOURCE_TIMEOUT parameter; then retry the operation.

ORA-00100 no data found

Cause: An application made a reference to unknown or inaccessible data.

Action: Handle this condition within the application or make appropriate modifications to the application code.

ORA-00101 invalid specification for system parameter DISPATCHERS

Cause: The syntax for the DISPATCHERS initialization parameter is incorrect.

Action: Enter the DISPATCHERS initialization parameter into the initialization parameter file with the correct syntax and then shut down and restart the instance.

ORA-00102 network protocol string cannot be used by dispatchers

Cause: The network specified in DISPATCHERS does not have the functionality required by the dispatchers.

Action: Refer to your Oracle operating system-specific documentation for network protocols supported by the dispatchers.

ORA-00103 invalid network protocol; reserved for use by dispatchers

Cause: The network specified in the Net8 connect string is reserved for use by the dispatchers.

Action: Specify other network protocols in the connection string.

ORA-00104 deadlock detected; all public servers blocked waiting for resources

Cause: All available public servers are servicing requests that require resources locked by a client which is unable to get a public server to release the resources.

Action: Increase the limit for the system parameter MAX_SHARED_SERVERS as the system will automatically start new servers to break the deadlock until the number of servers reaches the value specified inMAX_SHARED_SERVERS.

ORA-00105 dispatching mechanism not configured for network protocol string

Cause: An attempt was made to alter the dispatcher's configuration for a network protocol that was not specified in the initialization parameter file.

Action: Do one of the following:

• Include the network protocol in the definition for theDISPATCHERS initialization parameter and restart the system.
• Use the ALTER SYSTEM SET DISPATCHERS statement with a network protocol that exists in the initialization parameter file.

ORA-00106 cannot startup/shutdown database when connected to a dispatcher

Cause: An attempt was made to start or shut down an instance while connected to a shared server via a dispatcher.

Action: Reconnect as user INTERNAL without going through the dispatcher. For most cases, this can be done by connect to INTERNAL without specifying a network connect string.

ORA-00107 failed to connect to ORACLE listener process

Cause: Most likely due to the fact that the network listener process has not been started.

Action: Check for the following:

• The network configuration file is not set up correctly.
• The client side address is not specified correctly.
• The listener initialization parameter file is not set up correctly.

ORA-00108 failed to set up dispatcher to accept connection asynchronously

Cause: The network protocol used by the dispatcher does not support asynchronous operations.

Action: Contact Oracle Support Services.

ORA-00111 not all servers started because number of servers is limited tostring

Cause: An attempt was made to start more servers than the maximum number specified by the system parameterMAX_SHARED_SERVERS.

Action: Increase the value of the MAX_SHARED_SERVERS initialization parameter as needed or re-issue theALTER SYSTEM SET SHARED_SERVERS statement with an appropriate number of servers.

ORA-00112 only created up to string (maximum specified) dispatchers

Cause: An attempt was made to start more dispatchers than the maximum number specified by the system parameterMAX_DISPATCHERS.

Action: Increase the value of the MAX_DISPATCHERS initialization parameter as needed.

ORA-00113 protocol name string is too long

Cause: A protocol name specified in the DISPATCHERS initialization parameter is too long.

Action: Use a valid protocol name for the DISPATCHERS value.

ORA-00114 missing value for system parameter SERVICE_NAMES

Cause: No value was specified for the SERVICE_NAMES initialization parameter, nor for theDB_NAME parameter.

Action: Add an SERVICE_NAMES or DB_NAME definition to the initialization parameter file. By default,SERVICE_NAMES is the value of DB_NAME unless SERVICE_NAMES is explicitly specified.

ORA-00115 connection refused; dispatcher connection table is full

Cause: A connection request was refused by a dispatcher because the dispatcher cannot support any more connections.

Action: Connect to a different dispatcher or use a dedicated server.

ORA-00116 SERVICE_NAMES name is too long

Cause: The service name specified in the SERVICE_NAMES initialization parameter is too long.

Action: Use a shorter name for the SERVICE_NAMES value (less than or equal to 255 characters).

ORA-00117 value out of range for system parameter SHARED_SERVERS

Cause: The specified value of the SHARED_SERVERS initialization parameter is incorrect.

Action: SHARED_SERVERS must be greater than or equal to 0 and less than or equal to the value ofMAX_SHARED_SERVERS.

ORA-00118 value out of range for system parameter DISPATCHERS

Cause: The value of the DISPATCHERS parameter is incorrect.

Action: The sum of all DISPATCHERS values must be greater than or equal to 0 and less than or equal to the value ofMAX_DISPATCHERS.

ORA-00119 invalid specification for system parameter string

Cause: The syntax for the specified parameter is incorrect.

Action: Refer to the Oracle9i Database Reference for the correct syntax.

ORA-00120 dispatching mechanism not enabled or installed

Cause: Either the dispatching mechanism was not enabled or the Oracle executable image was not installed with the dispatching mechanism.

Action: Refer to the Oracle9i Database Administrator's Guide and your operating system-specific documentation for procedures for starting and configuring the dispatcher process.

ORA-00121 SHARED_SERVERS specified without DISPATCHERS

Cause: A definition for SHARED_SERVERS was specified in the initialization parameter file, but no definition forDISPATCHERS was specified. Without a value for DISPATCHERS, shared servers will never be used.

Action: Add a definition for DISPATCHERS in the initialization parameter file (or remove the definition forSHARED_SERVERS, if shared servers are not being used).

ORA-00122 cannot initialize network configuration

Cause: Oracle could not initialize Net8.

Action: See accompanying messages.

ORA-00123 idle public server terminating

Cause: Too many idle servers were waiting on the common queue.

Action: This error is used internally, no action is required.

ORA-00124 DISPATCHERS specified without MAX_SHARED_SERVERS

Cause: A definition for DISPATCHERS was specified in the initialization parameter file, butMAX_SHARED_SERVERS was specified as zero.

Action: Specify MAX_SHARED_SERVERS to be greater than zero.

ORA-00125 connection refused; invalid presentation

Cause: The PRESENTATION in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported.

Action: Correct the PRESENTATION specified in the TNS address.

ORA-00126 connection refused; invalid duplicity

Cause: The DUPLICITY in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported.

Action: Correct the DUPLICITY specified in the TNS address.

ORA-00127 dispatcher string does not exist

Cause: There is currently no dispatcher running with the specified name.

Action: Retry with a name of the form "D###" denoting an existing dispatcher process.

ORA-00128 this command requires a dispatcher name

Cause: Wrong syntax for ALTER SYSTEM SHUTDOWN.

Action: Use correct syntax:

ALTER SYSTEM SHUTDOWN [ IMMEDIATE ] 'dispatcher name'

ORA-00129 listener address validation failed 'string'

Cause: An error was encountered while validating the listener address.

Action: Resolve the error or contact Oracle Support Services.

ORA-00130 invalid listener address 'string'

Cause: The listener address specification is not valid.

Action: Make sure that all fields in the listener address (protocol, port, host, key, ...) are correct.

ORA-00131 network protocol does not support registration 'string'

Cause: The specified protocol does not support async notification.

Action: Refer to the manual for information on supported network protocols.

ORA-00132 syntax error or unresolved network name 'string'

Cause: Listener address has syntax error or cannot be resolved.

Action: If a network name is specified, check that it corresponds to an entry in TNSNAMES.ORA or other address repository as configured for your system. Make sure that the entry is syntactically correct.

ORA-00150 duplicate transaction ID

Cause: An attempt was made to start a new transaction with an ID already in use by an existing transaction.

Action: Check your application.

ORA-00151 invalid transaction ID

Cause: The specified transaction ID does not correspond to an existing valid transaction.

Action: Check your application.

ORA-00152 current session does not match requested session

Cause: The current session is not the same as the session that was passed into a UPIXADO() call.

Action: Check your application.

ORA-00153 internal error in XA library

Cause: The XA library could not access thread-specific pointers.

Action: Contact Oracle Support Services.

ORA-00154 protocol error in transaction monitor

Cause: The transaction monitor returned TMJOIN on an AX_REG call but the transaction was locally suspended.

Action: Contact the transaction monitor customer support.

ORA-00155 cannot perform work outside of global transaction

Cause: The application tried to perform some work on either an Oracle 7.3 server or an Oracle8 server with local transactions disabled while outside of a global transaction.

Action: Check if the application is connected to an Oracle 7.3 server. The Transaction monitor must not return a NULL XID on an AX_REG call when the resource manager is Oracle 7.3. If the application is connected to an Oracle8 server, either set nolocal=f in the xa_open string or start a global transaction prior to attempting the work.

ORA-00160 global transaction length string is greater than maximum (string)

Cause: An external global transaction ID with a too large length field was passed in.

Action: Report the problem to your external transaction coordinator vendor.

ORA-00161 transaction branch length string is illegal (maximum allowedstring)

Cause: An external transaction branch ID with a length either too large or 0 was passed in.

Action: Report the problem to your external transaction coordinator vendor.

ORA-00162 external dbid length string is greater than maximum (string)

Cause: An external database name with too large a length field was passed in.

Action: Report the problem to your external transaction coordinator vendor.

ORA-00163 internal database name length string is greater than maximum (string)

Cause: An internal database name with a too large length field was passed in.

Action: Report the problem to your external transaction coordinator vendor.

ORA-00164 distributed autonomous transaction disallowed within migratable distributed transaction

Cause: A request was made by the application to start a distributed autonomous transaction when the application was in a migratable distributed transaction.

Action: Roll back or commit the current distributed transaction first.

ORA-00165 migratable distributed autonomous transaction with remote operation is not allowed

Cause: A request was made by the application to start a migratable distributed autonomous transaction with remote operation.

ORA-00200 controlfile could not be created

Cause: It was not possible to create the control file.

Action: Check that there is sufficient disk space and no conflicts in file names and try to create the control file again.

ORA-00201 controlfile version string incompatible with ORACLE versionstring

Cause: The control file was created by incompatible software.

Action: Either restart with a compatible software release or use CREATE CONTROLFILE to create a new control file that is compatible with this release.

ORA-00202 controlfile: 'string'

Cause: This message reports the name file involved in other messages.

Action: See associated error messages for a description of the problem.

ORA-00203 using the wrong controlfiles

Cause: The mount ID in the control file is not the same as the mount ID in the control file used by the first instance to mount this database. The control files are for the same database but they are not the same files. Most likely one instance is using a backup control file.

Action: Check that the correct control files were specified.

ORA-00204 error in reading (block string, # blocksstring) of controlfile

Cause: A disk I/O failure was detected on reading the control file.

Action: Check that the disk is online. If it is not, bring it online and shut down and restart Oracle. If it is online, then look for operating system reasons for Oracle's inability to read the disk or control file. See theOracle9i Database Administrator's Guide for information on recovering from the loss of a control file. See also your operating system-specific Oracle documentation.

ORA-00205 error in identifying controlfile, check alert log for more info

Cause: The system could not find a control file of the specified name and size.

Action: One of the following:

• Check that the proper control file name is referenced in the CONTROL_FILES initialization parameter in the initialization parameter file and try again.
• When using mirrored control files, that is, more than one control file is referenced in the initialization parameter file, remove the control file name listed in the message from the initialization parameter file and restart the instance. If the message does not recur, remove the problem control file from the initialization parameter file and create another copy of the control file with a new file name in the initialization parameter file.

ORA-00206 error in writing (block string, # blocksstring) of controlfile

Cause: A disk I/O failure was detected on writing to the control file.

Action: Check that the disk is online. If it is not, bring it online and shut down and restart Oracle. If it is online, then look for operating system reasons for Oracle's inability to write to the disk or control file. See theOracle9i Database Administrator's Guide for information on recovering from the loss of a control file. See also your operating system-specific Oracle documentation.

ORA-00207 controlfiles are not for the same database

Cause: The database ID in the control file is not the same as the database ID in the control file used by the first instance to mount this database. Most likely one of the mounts used the wrong control file or there are two databases with the same name.

Action: Check that the control file is for the correct database and is not an old version. When using multiplexed control files, that is, more than one control file is referenced in the initialization parameter file, remove the control file name listed in the message from the initialization parameter file and restart the instance. If the message does not recur, remove the problem control file from the initialization parameter file and create another copy of the control file using a new file name in the initialization parameter file.

ORA-00208 number of controlfile names exceeds limit of string

Cause: An attempt was made to use more control files than Oracle supports.

Action: Shut down Oracle. Reduce the number of control files specified in the CONTROL_FILES parameter in the initialization parameter file, and restart Oracle. Delete unused files.

ORA-00209 control file blocksize mismatch, check alert log for more info

Cause: The block size in the control file header does not match the size specified in the DB_BLOCK_SIZE parameter.

Action: Reduce the block size to the amount specified in the message and try again.

ORA-00210 cannot open the specified controlfile

Cause: Cannot open the control file.

Action: Check to make sure the control file exists and is not locked by some other program.

ORA-00211 controlfile does not match previous controlfiles

Cause: A control file was specified that belongs to another database.

Action: Find and install the correct control file.

ORA-00212 block size string below minimum required size ofstring bytes

Cause: The block size specified was too small. Space for the system overhead is required.

Action: Specify a larger block size and retry the operation.

ORA-00213 cannot reuse controlfile; old file size string,string required

Cause: To reuse a control file, it must be the same size as the one previously used.

Action: Either do not specify REUSE, or specify a matching combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses in the CREATE DATABASE or CREATE CONTROLFILE statement.

ORA-00214 controlfile 'string' version string inconsistent with file 'string' version string

Cause: An inconsistent set of control files, datafiles, and redo log files was used.

Action: Use a consistent set of control files, datafiles, and redo log files. That is, all the files must be for the same database and from the same time period.

ORA-00215 must be at least one controlfile

Cause: No control file is specified or the control file specified does not exist.

Action: Specify at least one valid control file and retry the operation.

ORA-00216 controlfile could not be resized for migration from 8.0.2

Cause: Control files created by release 8.0.2 were missing some records. These records are automatically added by resizing the control file when attempting to run a later release. The resize failed.

Action: Look in the alert log for the reason that the resize failed. If it can be fixed by giving the control file more space, then do that. Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file.

ORA-00217 controlfile could not be resized for migration from 9.0.1

Cause: Controlfiles created by release 9.0.1 were missing some records. These records are automatically added by resizing the controlfile when attempting to run a later release. The resize failed.

Action: Look in the alert log for the reason the resize failed. If it can be fixed by giving the controlfile more space, then do that. Otherwise, use theCREATE CONTROLFILE script dumpped to the trace file to create a new controlfile.

ORA-00218 block size string of controlfile does not match DB_BLOCK_SIZE (string)

Cause: The block size as stored in the control file header is different from the value of the initialization parameter DB_BLOCK_SIZE. This might be due to an incorrect setting of DB_BLOCK_SIZE, or else might indicate that the control file has either been corrupted or belongs to a different database.

Action: Restore a good copy of the control file.

ORA-00219 required controlfile size string exceeds maximum allowable sizestring

Cause: An invocation of CREATE DATABASE, CREATE CONTROLFILE, cfileCalcSizeList, or cfileCalcSizeArray was executed specifying a combination of parameters that would require the control file size in blocks to exceed the maximum allowable value.

Action: In the case of CREATE DATABASE or CREATE CONTROLFILE, use a different combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses. In the case of cfileCalcSizeList() or cfileCalcSizeArray(), use a different combination of record type counts.

ORA-00220 controlfile not mounted by first instance, check alert log for more info

Cause: The specified control file has a different mount ID than the other control files that are being mounted. This means that the first instance to mount the database did not use this control file.

Action: Find and install the correct control file.

ORA-00221 error on write to controlfile

Cause: An error occurred when writing to one or more of the control files.

Action: See accompanying messages.

ORA-00222 operation would reuse name of a currently mounted controlfile

Cause: The file name supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of the specified currently mounted control file.

Action: Retry the operation with a different file name.

ORA-00223 convert file is invalid or incorrect version

Cause: An Oracle7 to Oracle8 convert file contains invalid data or was created with an different version of the migration utility. This error can also be caused by incorrect ORACLE_HOME environment variable when the ALTER DATABASE CONVERT command is issued.

Action: Use a correct version of the convert file or regenerate it with the migration utility. Make sure that the migration utility is the same version as the Oracle8 RDBMS executable and that the ORACLE_HOME environment variable is properly set.

ORA-00224 controlfile resize attempted with illegal record type (string)

Cause: An attempt was made to expand or shrink the control file by calling cfileResizeSection using an invalid value for the RECORD_TYPE parameter.

Action: Use a value for the RECORD_TYPE parameter that specifies a valid record type other than type 0 (valid range is 1 to 16).

ORA-00225 expected size string of controlfile differs from actual sizestring

Cause: The expected size of the control file as stored in its header was different than the actual operating system file size. This usually indicates that the control file was corrupted.

Action: Restore a good copy of the control file.

ORA-00226 operation disallowed while alternate controlfile open

Cause: The attempted operation could not be executed at this time because this process had an alternate control file open for fixed table access.

Action: Retry the operation after calling cfileUseCurrent.

ORA-00227 corrupt block detected in controlfile: (block string, # blocks string)

Cause: A block header corruption or checksum error was detected on reading the control file.

Action: Use the CREATE CONTROLFILE or RECOVER DATABASE USING BACKUP CONTROLFILE command.

ORA-00228 length of alternate controlfile name exceeds maximum of string

Cause: The specified file name, which was supplied as a parameter to cfileSetSnapshotName or cfileUseCopy, exceeds the maximum file name length for this operating system.

Action: Retry the operation with a shorter file name.

ORA-00229 operation disallowed: already hold snapshot controlfile enqueue

Cause: The attempted operation cannot be executed at this time because this process currently holds the snapshot control file enqueue.

Action: Retry the operation after calling cfileUseCurrent to release the snapshot control file enqueue.

ORA-00230 operation disallowed: snapshot controlfile enqueue unavailable

Cause: The attempted operation cannot be executed at this time because another process currently holds the snapshot control file enqueue.

Action: Retry the operation after the concurrent operation that is holding the snapshot control file enqueue terminates.

ORA-00231 snapshot controlfile has not been named

Cause: During an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot, it was detected that no file name for the snapshot control file had previously been specified.

Action: Specify a name for the snapshot control file by calling cfileSetSnapshotName.

ORA-00232 snapshot controlfile is nonexistent, corrupt, or unreadable

Cause: The snapshot control file was found to be non-existent, corrupt, or unreadable during an invocation of cfileUseSnapshot.

Action: Call cfileMakeAndUseSnapshot again (or for the first time).

ORA-00233 copy controlfile is corrupt or unreadable

Cause: The specified copy control file was found to be corrupt or unreadable during an invocation of cfileUseCopy.

Action: Before retrying cfileUseCopy, use the ALTER DATABASE BACKUP CONTROLFILE command and specify the same file name that was specified for cfileUseCopy.

ORA-00234 error in identifying or opening snapshot or copy controlfile

Cause: A snapshot or copy control file of the specified name could not be found or opened during an invocation of cfileUseSnapshot, cfileMakeAndUseSnapshot, or cfileUseCopy.

Action: Re-create the snapshot or copy control file using cfileMakeAndUseSnapshot or ALTER DATABASE BACKUP CONTROLFILE, respectively.

ORA-00235 controlfile fixed table inconsistent due to concurrent update

Cause: Concurrent update activity on a control file caused a query on a control file fixed table to read inconsistent information.

Action: Retry the operation.

ORA-00236 snapshot operation disallowed: mounted controlfile is a backup

Cause: Attempting to invoke cfileSetSnapshotName, cfileMakeAndUseSnapshot, or cfileUseSnapshot when the currently mounted control file is a backup control file.

Action: Mount a current control file and retry the operation.

ORA-00237 snapshot operation disallowed: controlfile newly created

Cause: An attempt to invoke cfileMakeAndUseSnapshot with a currently mounted control file that was newly created with CREATE CONTROLFILE was made.

Action: Mount a current control file and retry the operation.

ORA-00238 operation would reuse a filename that is part of the database

Cause: The file name supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of a file that is currently part of the database.

Action: Retry the operation with a different file name.

ORA-00250 archiver not started

Cause: An attempt was made to stop automatic archiving, but the archiver process was not running.

Action: No action is required.

ORA-00251 LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as stringstring

Cause: The destination specified by the LOG_ARCHIVE_DUPLEX_DEST parameter is the same as the destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command.

Action: Specify a different destination for parameter LOG_ARCHIVE_DUPLEX_DEST, or specify a different destination with the ALTER SYSTEM command.

ORA-00252 log string of thread string is empty, cannot archive

Cause: A log must be used for redo generation before it can be archived. The specified redo log was not been used since it was introduced to the database. However, it is possible that the instance died during a log switch and the log was empty.

Action: Empty logs do not need to be archived. Do not attempt to archive the redo log file.

ORA-00253 character limit string exceeded by archive destination stringstring

Cause: The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command was too long.

Action: Retry the ALTER SYSTEM command using a string shorter than the limit specified in the error message.

ORA-00254 error in archive control string 'string'

Cause: The specified archive log location is invalid in the archive command or the LOG_ARCHIVE_DEST initialization parameter.

Action: Check the archive string used to make sure it refers to a valid online device.

ORA-00255 error archiving log string of thread string, sequence # string

Cause: An error occurred during archiving.

Action: Check the accompanying message stack for more detailed information. If the online log is corrupted, then the log can be cleared using the UNARCHIVED option. This will make any existing backups useless for recovery to any time after the log was created, but will allow the database to generate redo.

ORA-00256 cannot translate archive destination string string

Cause: The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command could not be translated.

Action: Check the accompanying message stack for more detailed information. Then, retry the ALTER SYSTEM command using a different string.

ORA-00257 archiver error. Connect internal only, until freed.

Cause: The archiver process received an error while trying to archive a redo log. If the problem is not resolved soon, the database will stop executing transactions. The most likely cause of this message is the destination device is out of space to store the redo log file.

Action: Check the archiver trace file for a detailed description of the problem. Also, verify that the device specified in the initialization parameter ARCHIVE_LOG_DEST is set up properly for archiving.

ORA-00258 manual archiving in NOARCHIVELOG mode must identify log

Cause: The database is in NOARCHIVELOG mode and a command to manually archive a log did not specify the log explicitly by sequence number, group number or file name.

Action: Specify the log by file name, by group number or by thread and sequence number.

ORA-00259 log string of open thread string is the current log, cannot archive

Cause: An attempt was made to archive the current log of an open thread. This is not allowed because the redo log file may still be in use for the generation of redo entries.

Action: Force a log switch in the instance where the thread is open. If no instances are open, open the database so that instance recovery can recover the thread.

ORA-00260 cannot find online log sequence string for threadstring

Cause: The log sequence number supplied in the ARCHIVE statement does not match any of the online logs for the thread. This can result from any of the following situations:

• The log might have been reused for another sequence number.
• The log might have been dropped.
• The sequence number might be greater than the current log sequence number.
• The thread might not have any logs.

Action: Check the ARCHIVE statement, then specify a valid log sequence number. Specify a valid log sequence number.

ORA-00261 log string of thread string is being archived or modified

Cause: The log is either being archived by another process or an administrative command is modifying the log. Operations that modify the log include clearing, adding a member, dropping a member, renaming a member, and dropping the log.

Action: Wait for the current operation to complete and try again.

ORA-00262 current log string of closed thread string cannot switch

Cause: The log cannot be cleared or manually archived because it is the current log of a closed thread, and it is not possible to switch logs so another log is current. All other logs for the thread need to be archived, or cleared, and cannot be reused.

Action: Archive another log in the same thread first, or complete the clearing. See attached errors for the reason the switch cannot be completed.

ORA-00263 there are no logs that need archiving for thread string

Cause: An attempt was made to manually archive the unarchived logs in this thread but no logs needed archiving.

Action: No action required.

ORA-00264 no recovery required

Cause: An attempt was made to perform media recovery on files that do not need any type of recovery.

Action: Do not attempt to perform media recovery on the selected files. Check to see that the file names were entered properly. If not, retry the command with the proper file names.

ORA-00265 instance recovery required, cannot set ARCHIVELOG mode

Cause: The database either crashed or was shut down with the ABORT option. Media recovery cannot be enabled because the online logs may not be sufficient to recover the current datafiles.

Action: Open the database and then enter the SHUTDOWN command with the NORMAL or IMMEDIATE option.

ORA-00266 name of archived log file needed

Cause: During media recovery, the name of an archived redo log file was requested, but no name was entered.

Action: Mount the correct redo log file and enter its name when it is requested.

ORA-00267 name of archived log file not needed

Cause: During media recovery, the name of an archived redo log file was entered, but no name was requested.

Action: Continue media recovery, but do not enter a new log name.

ORA-00268 specified log file does not exist 'string'

Cause: The given redo log file does not exist.

Action: Check the spelling and capitalization of the file name and retry the command.

ORA-00269 specified log file is part of thread string notstring

Cause: The given redo log file is not part of the given thread.

Action: Check that the thread of the redo log file matches the thread on the command line. If not, use a redo log file from the appropriate thread. Retry the command after correcting the error.

ORA-00270 error creating archive log string

Cause: An error was encountered when either creating or opening the destination file for archiving.

Action: Check that the archive destination is valid and that there is sufficient space on the destination device.

ORA-00271 there are no logs that need archiving

Cause: An attempt was made to archive the unarchived redo log files manually, but there are no files that need to be archived.

Action: No action is required.

ORA-00272 error writing archive log string

Cause: An I/O error occurred while archiving a redo log file.

Action: Check that the output device is still available and correct any device errors that may have occurred. Also, make certain that sufficient space for archiving is available on the output device.

ORA-00273 media recovery of direct load data that was not logged

Cause: A media recovery session encountered a table that was loaded by the direct loader without logging any redo information. Some or all of the blocks in this table are now marked as corrupt.

Action: The table must be dropped or truncated so that the corrupted blocks can be reused. If a more recent backup of the file is available, try to recover this file to eliminate this error.

ORA-00274 illegal recovery option string

Cause: An illegal option was specified for a recovery command.

Action: Correct the syntax and retry the command.

ORA-00275 media recovery has already been started

Cause: An attempt was made to start a second media recovery operation in the same session.

Action: Complete or cancel the first media recovery session or start another session to perform media recovery.

ORA-00276 CHANGE keyword specified but no change number given

Cause: The CHANGE keyword was specified on the command line, but no change number was given.

Action: Retry the command using a valid change number after the CHANGE keyword.

ORA-00277 illegal option to the UNTIL recovery flag string

Cause: Only CANCEL, CHANGE and TIME can be used with the UNTIL keyword.

Action: Correct the syntax.

ORA-00278 log file 'string' no longer needed for this recovery

Cause: The specified redo log file is no longer needed for the current recovery.

Action: No action is required. The archived redo log file may be removed from its current location to conserve disk space, if needed. However, the redo log file may still be required for another recovery session in the future.

ORA-00279 change string generated at string needed for thread string

Cause: The requested log is required to proceed with recovery.

Action: Supply the requested log with ALTER DATABASE RECOVER LOGFILEfilename or cancel recovery with ALTER DATABASE RECOVER CANCEL.

ORA-00280 change string for thread string is in sequence #string

Cause: This message helps to locate the redo log file with the specified change number requested by other messages.

Action: Use the information provided in this message to specify the required archived redo log files for other errors.

ORA-00281 media recovery may not be performed using dispatcher

Cause: An attempt was made to use a dispatcher process for media recovery. Memory requirements disallow this recovery method.

Action: Connect to the instance via a dedicated server process to perform media recovery.

ORA-00282 UPI string call not supported, use ALTER DATABASE RECOVER

Cause: The given UPI call is no longer supported.

Action: Use the ALTER DATABASE RECOVER command for all recovery actions.

ORA-00283 recovery session canceled due to errors

Cause: An error during recovery was determined to be fatal enough to end the current recovery session.

Action: More specific messages will accompany this message. Refer to the other messages for the appropriate action.

ORA-00284 recovery session still in progress

Cause: An error during recovery was determined to be minor enough to allow the current recovery session to continue.

Action: More specific messages will accompany this message. Refer to the other messages for the appropriate action.

ORA-00285 TIME not given as a string constant

Cause: UNTIL TIME was not followed by a string constant for the time.

Action: Enter the time enclosed in single quotation marks.

ORA-00286 no members available, or no member contains valid data

Cause: None of the members of a redo log file group are available, or the available members do not contain complete data.

Action: If a member is temporarily offline, attempt to make it available. Make sure that the correct file names are being used, especially if the redo log file is being accessed from a remote location.

ORA-00287 specified change number string not found in threadstring

Cause: The given change number does not appear in any of the online redo logs for the given thread.

Action: Check the statement to make certain a valid change number is given. Perhaps try to use the NEXT option for archiving logs.

ORA-00288 to continue recovery type ALTER DATABASE RECOVER CONTINUE

Cause: During media recovery, a new log is not required but the continuation command is necessary to do a checkpoint and report errors.

Action: Type ALTER DATABASE RECOVER CONTINUE and recovery will resume.

ORA-00289 suggestion : string

Cause: This message reports the next redo log file name that is needed, according to the initialization parameters LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT. This message assumes that LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT are the same now as when the required redo log file was archived.

Action: Consider using this file name for the next log needed for recovery.

ORA-00290 operating system archival error occurred. See error below

Cause: While attempting to archive to a redo log file, the server encountered an unexpected operating system error.

Action: Correct the operating system error given in the messages and retry the operation. See also your operating system-specific Oracle documentation.

ORA-00291 numeric value required for PARALLEL option

Cause: A recovery command was specified incorrectly. The PARALLEL option must be followed by a numeric argument that specifies the degree of parallelism.

Action: Re-enter the command with a numeric argument specifying the degree of parallelism desired.

ORA-00292 parallel recovery feature not installed

Cause: A parallel recovery was requested when the parallel recovery option is not installed.

Action: Delete the PARALLEL clause from the RECOVER command. Also, delete the RECOVERY_PARALLELISM parameter in the initialization file.

ORA-00293 controlfile out of sync with redo log

Cause: The redo log file and control file are out of sync because a non-current control file was specified when the instance was started.

Action: Retry the RECOVER command using the current control file, or retry the RECOVER command using the USING BACKUP CONTROLFILE clause.

ORA-00294 invalid archivelog format specifier 'string'

Cause: An invalid format specifier was found in the LOG_ARCHIVE_FORMAT initialization parameter. The only characters permitted forstring are s, S, t, and T.

Action: Correct the initialization file and restart the instance.

ORA-00295 datafile/tempfile number string is invalid, must be between 1 andstring

Cause: An invalid file number was specified.

Action: Specify a valid datafile or tempfile number and retry the operation.

ORA-00296 maximum number of files (string) exceeded for RECOVER DATAFILE LIST

Cause: The RECOVER DATAFILE LIST command specified more datafiles than are allowed by the DB_FILES initialization parameter. This error occurs when doing recovery with Recovery Manager, and the instance has been started with a DB_FILES parameter specifying fewer datafiles than Recovery Manager needs to recover to satisfy the user's RECOVER command.

Action: Restart the instance with a higher value for DB_FILES.

ORA-00297 must specify RECOVER DATAFILE LIST before RECOVER DATAFILE START

Cause: The RECOVER DATAFILE START command was issued, but no RECOVER DATAFILE LIST commands had been issued. This only happens when doing recovery with Recovery Manager, and is an internal error in Recovery Manager, because Recovery Manager should always issue RECOVER DATAFILE LIST before RECOVER DATAFILE START.

Action: Contact Oracle Support Services.

ORA-00298 Missing or invalid attribute value

Cause: A nonzero integer value is required when the following keyword attributes are specified:

• TIMEOUT
• EXPIRE
• DELAY
• NEXT

Action: Correct the syntax and retry the command.

ORA-00299 must use file-level media recovery on data file string

Cause: The control file does not contain an entry for this file, so block media recovery cannot be done.

Action: Restore the data file and perform file-level media recovery.

ORA-00300 illegal redo log block size string specified - exceeds limit ofstring

Cause: The specified block size of the redo log is greater than the maximum block size for the operating system.

Action: Create the redo log on a device with a smaller block size.

ORA-00301 error in adding log file 'string' - file cannot be created

Cause: The creation of the redo log file failed

Action: Check whether:

1. There is enough storage space on the device
2. The name of the file is valid
3. The device is online
4. An I/O error occurred

Also, it is possible REUSE was specified on the command line and a file of the incorrect size exists. Either do not specify REUSE or use a file of the correct size.

ORA-00302 limit of string logs exceeded

Cause: The maximum number of redo log files has been exceeded. There is a limit, set at database creation, on the number of redo log files (typically 16).

Action: Use the CREATE CONTROLFILE command with a larger value for MAXLOGFILES.

ORA-00303 cannot process Parallel Redo

Cause: A redo log containing Parallel Redo has been detected. The current Oracle release cannot process this format of redo.

Action: Use a later release that supports Parallel Redo.

ORA-00304 requested INSTANCE_NUMBER is busy

Cause: An instance tried to start by using a value of the initialization parameter INSTANCE_NUMBER that is already in use.

Action: Either:

• Specify another INSTANCE_NUMBER,
• Shut down the running instance with this number, or
• Wait for instance recovery to complete on the instance with this number.

ORA-00305 log string of thread string inconsistent; belongs to another database

Cause: The database ID in the redo log file does not match the database ID in the control file. This redo log file is not from the current database.

Action: Specify the correct redo log file, and then retry the operation.

ORA-00306 limit of string instances in this database

Cause: Starting this instance would exceed the maximum number of instances allowed for this database. This message occurs only with STARTUP shared and multiple instances.

Action: You cannot start more than the lower of:

• the operating system-specific maximum or
• the number of instances specified by the MAXINSTANCES option specified in the CREATE DATABASE statement

ORA-00307 requested INSTANCE_NUMBER out of range, maximum is string

Cause: The initialization parameter INSTANCE_NUMBER specified a number that was out of range.

Action: Change the value of INSTANCE_NUMBER to a valid range and restart the instance. The minimum value is 1 and the maximum value is the lower of the operating system-specific maximum or the value of the MAXINSTANCES option specified in the CREATE DATABASE statement. See also your operating system-specific Oracle documentation.

ORA-00308 cannot open archived log 'string'

Cause: The system cannot access a required archived redo log file.

Action: Check that the offline log exists, the storage device is online, and the archived file is in the correct location. Then attempt to continue recovery or restart the recovery session.

ORA-00309 log belongs to wrong database

Cause: The system cannot access the archived redo log because it belongs to another database.

Action: Specify the correct redo log file and then retry the operation.

ORA-00310 archived log contains sequence string; sequencestring required

Cause: The archived log is out of sequence, probably because it is corrupted or the wrong redo log file name was specified during recovery.

Action: Specify the correct redo log file and then retry the operation.

ORA-00311 cannot read header from archived log

Cause: An I/O error occurred when attempting to read the log file header from the specified archived redo log file.

Action: Other messages will accompany this message. See the associated messages for the appropriate action to take.

ORA-00312 online log string thread string: 'string'

Cause: This message reports the file name for details of another message.

Action: Other messages will accompany this message. See the associated messages for the appropriate action to take.

ORA-00313 open failed for members of log group string of threadstring

Cause: The online log cannot be opened. The file may not be in the expected location.

Action: Specify the correct redo log file or make the log available, if necessary. Also, see the accompanying messages.

ORA-00314 log string of thread string, expected sequence# string doesn't match string

Cause: The online log is corrupted or is an old version.

Action: Find and install the correct version of the log or reset the logs. Refer to theOracle9i Database Administrator's Guide for recovery procedures.

ORA-00315 log string of thread string, wrong thread # string in header

Cause: The online log is corrupted or is an old version.

Action: Find and install the correct version of the log or reset the logs. Refer to theOracle9i Database Administrator's Guide for recovery procedures.

ORA-00316 log string of thread string, type string in header is not log file

Cause: The online log is corrupted or is an old version.

Action: Find and install the correct version of the log or reset the logs. Refer to theOracle9i Database Administrator's Guide for recovery procedures.

ORA-00317 file type string in header is not log file

Cause: This is not an archived log file.

Action: Find the correct file and try again. Refer to the Oracle9i Database Administrator's Guide for recovery procedures.

ORA-00318 log string of thread string, expected file size string doesn't match string

Cause: The file size indicated in the control file did not match the file size contained in the log file.

Action: Restore the correct file or reset the logs. Refer to theOracle9i Database Administrator's Guide for recovery procedures.

ORA-00319 log string of thread string has incorrect log reset status

Cause: An online redo log has log reset data that is different from the log reset data in the control file. The log is probably an incorrectly restored backup.

Action: Restore the correct file or reset the logs. Refer to theOracle9i Database Administrator's Guide for recovery procedures.

ORA-00320 cannot read file header from log string of threadstring

Cause: The file is not available.

Action: Restore the log file.

ORA-00321 log string of thread string, cannot update log file header

Cause: Cannot write to the log file.

Action: Restore access to the file.

ORA-00322 log string of thread string is not current copy

Cause: An online log appears to be an incorrectly restored backup.

Action: Restore the correct file or reset the logs. Refer to theOracle9i Database Administrator's Guide for recovery procedures.

ORA-00323 Current log of thread string not useable and all others need archiving

Cause: An attempt to open the thread failed because it is necessary to switch redo generation to another online log, but all the other logs need to be archived before they can be used.

Action: Archive the logs for the thread and then retry the open.

ORA-00324 log file 'string' translated name 'string' too long,string characters exceeds string limit

Cause: The translated name for a log file is too long.

Action: Choose an untranslated name that yields a shorter translated name.

ORA-00325 archived log for thread string, wrong thread #string in header

Cause: The archived log is corrupted or for another thread. Cannot use the log for applying the redo.

Action: Find the correct archived log.

ORA-00326 log begins at change string, need earlier changestring

Cause: The archived log supplied for recovery was generated after the log that is needed. Cannot yet use the log for applying redo.

Action: Find the correct archived log.

ORA-00327 log string of thread string, physical size string less than needed string

Cause: A log file has shrunk in size. This is likely to have been caused by a computer operator's mistake or an operating system error.

Action: Restore the log file from backup. If a backup is not available, drop this log and re-create it. If the database was shut down cleanly, no further action should be required; otherwise, incomplete recovery may be required.

ORA-00328 archived log ends at change string, need later changestring

Cause: The archived log supplied for recovery was generated before the log that is needed. Cannot use the log for applying redo.

Action: Find the correct archived log.

ORA-00329 archived log begins at change string, need changestring

Cause: The archived log is not the correct log. An earlier log is needed.

Action: Restore the correct log file.

ORA-00330 archived log ends at change string, need changestring

Cause: The archived log is not the correct log. A later log is needed.

Action: Restore the correct log file.

ORA-00331 log version string incompatible with ORACLE versionstring

Cause: The log was written by an incompatible version of Oracle.

Action: Recover the database with the compatible software, shut it down cleanly, and then restart Oracle with the current software.

ORA-00332 archived log is too small - may be incompletely archived

Cause: The log is smaller than the space allocated in it. May be the result of a SHUTDOWN ABORT while it was being written by the archiver.

Action: Get a complete version of this log and use it for recovery. There should either be an online version of it or a copy that was successfully archived.

ORA-00333 redo log read error block string count string

Cause: An I/O error occurred while reading the log described in the accompanying error.

Action: Restore accessibility to file, or get another copy of the file.

ORA-00334 archived log: 'string'

Cause: This message reports the file name involved with other errors.

Action: See associated error messages.

ORA-00335 online log string: No log with this number, log does not exist

Cause: This message reports the file name involved with other errors.

Action: See associated error messages.

ORA-00336 log file size string blocks is less than minimumstring blocks

Cause: The log file size as specified in the CREATE DATABASE statement is too small.

Action: Increase the log file size.

ORA-00337 log file 'string' does not exist and no size specified

Cause: An attempt to add a log found neither an existing file nor a size for creating the file.

Action: Specify a size for the log file.

ORA-00338 log string of thread string is more recent than controlfile

Cause: The control file change sequence number in the log file is greater than the number in the control file. This implies that the wrong control file is being used. Note that repeatedly causing this error can make it stop happening without correcting the real problem. Every attempt to open the database will advance the control file change sequence number until it is great enough.

Action: Use the current control file or do backup control file recovery to make the control file current. Be sure to follow all restrictions on doing a backup control file recovery.

ORA-00339 archived log does not contain any redo

Cause: The archived log is not the correct log. It is a copy of a log file that has never been used for redo generation, or was an online log being prepared to be the current log.

Action: Restore the correct log file.

ORA-00340 IO error processing online log string of threadstring

Cause: An I/O error occurred on the named online log.

Action: Restore accessibility to the file or restore the file from backup.

ORA-00341 log string of thread string, wrong log # string in header

Cause: The internal information in an online log file does not match the control file.

Action: Restore the correct file or reset the logs. Refer to theOracle9i Database Administrator's Guide for recovery procedures.

ORA-00342 archived log was created before last RESETLOGS

Cause: Recovery was given a log that was created before the last ALTER DATABASE OPEN RESETLOGS command. There should be another log created since then that contains the correct redo.

Action: Supply the correct log file.

ORA-00343 too many errors, log member closed

Cause: The maximum number of errors on this log member has been exceeded.

Action: Correct the underlying problem by referring to the other error messages found with this one.

ORA-00344 unable to re-create online log 'string'

Cause: An I/O failure occurred when attempting to re-create an online log as part of either an ALTER DATABASE OPEN RESETLOGS or ALTER DATABASE CLEAR LOGFILE command.

Action: Correct the file/device as indicated by accompanying errors.

ORA-00345 redo log write error block string countstring

Cause: An I/O error occurred while writing the log.

Action: Correct the cause of the error, and then restart the system. If the log is lost, apply media/incomplete recovery.

ORA-00346 log member marked as STALE

Cause: A log file member no longer is complete.

Action: Correct the underlying problem by referring to the other error messages found with this one.

ORA-00347 log string of thread string, expected block size string doesn't match string

Cause: During online recovery, the block size specified in the control file did not match the block size contained in the redo log file.

Action: Restore the correct redo file from a backup or reset the online redo log files.

ORA-00348 single-process redo failure. Must abort instance

Cause: A failure occurred during a critical portion of the log code during single process operation. This error does not occur during normal multi-process operation.

Action: SHUTDOWN ABORT and restart the database.

ORA-00349 failure obtaining block size for 'string'

Cause: The operating system was unable to determine the block size for the given file name.

Action: Consult the accompanying error message, and correct the device or specify another file name.

ORA-00350 log string of thread string needs to be archived

Cause: The command cannot be done because the log has not been archived, and media recovery has been enabled.

Action: Archive the log or disable media recovery. If the command supports an UNARCHIVED option, then it can be used. However, this may result in making backups unusable, and forcing the drop of some offline files.

ORA-00351 recover-to time invalid

Cause: The time specified in a recover-until statement must be after January 1st 1988.

Action: Specify a time after January 1st 1988.

ORA-00352 all logs for thread string need to be archived - cannot enable

Cause: An attempt was made to enable a thread with all logs needing to be archived, and media recovery has been enabled. There is no log that can be made the new current log for the thread.

Action: Archive a log for the thread or disable media recovery.

ORA-00353 log corruption near block string changestring time string

Cause: Some type of redo log corruption has been discovered. This error describes the location of the corruption. Accompanying errors describe the type of corruption.

Action: Perform recovery with a good version of the redo log or do incomplete recovery up to the indicated change or time.

ORA-00354 corrupt redo log block header

Cause: The block header on the redo block indicated by the accompanying error is not valid. The block number and time-stamp are given in an accompanying message.

Action: Perform recovery with a good version of the redo log or perform cancel-based recovery up to, but not including, the corrupted redo log file. If this happens when archiving, archiving of the problem log can be skipped by clearing the log with the UNARCHIVED option. This must be followed by a backup of every datafile to insure recoverability of the database.

ORA-00355 change numbers out of order

Cause: A change number found in the redo log is lower than a previously encountered change number. The log is corrupted in some way. The corruption may be at the earlier change or at this one.

Action: Perform recovery with a good version of the log or perform time-based recovery up to the indicated time.

ORA-00356 inconsistent lengths in change description

Cause: A change record in the redo log contains lengths that do not add up to a consistent value. The log is corrupted in some way.

Action: Perform recovery with a good version of the log or do time-based recovery up to the indicated time.

ORA-00357 too many members specified for log file, the maximum is string

Cause: An ADD LOGFILE or ADD LOGFILE MEMBER command would result in a log with too many members. The number of members is set when the database is created.

Action: Use fewer log file members.

ORA-00358 Too many file members specified, the maximum is string

Cause: A CREATE or ALTER statement specified too many members in a parenthesised file list.

Action: Specify a number of file members that is within the port-defined limit.

ORA-00359 logfile group string does not exist

Cause: An ADD LOGFILE MEMBER or DROP LOGFILE request specified a log file group number that does not exist.

Action: Check the configuration of the log files and reissue the command.

ORA-00360 not a logfile member: string

Cause: A file name was given to DROP LOGFILE MEMBER command that is not a part of the database, or which is a datafile.

Action: Supply a valid log file member name.

ORA-00361 cannot remove last log member string for groupstring

Cause: An attempt has been made to remove the last member of a log file group.

Action: If desired, delete the entire log, by using DROP LOGFILE.

ORA-00362 member is required to form a valid logfile in group string

Cause: A request to drop a log file member was denied because it would remove data required to form a complete log file.

Action: If desired, delete the entire log (after archiving if required), by using DROP LOGFILE.

ORA-00363 log is not the archived version

Cause: The log given to recovery is a backup of the online version from the time it was the current log. The archived version of the log would not be marked as end of thread. This error can also be caused by failing to list the current log of an enabled thread in a CREATE CONTROLFILE command.

Action: Find the archived version of the log and supply its name. If this is media recovery immediately following a CREATE CONTROLFILE, be sure the current log for this thread was included.

ORA-00364 cannot write header to new log member

Cause: An I/O error occurred when attempting to write the header to a log member that is being added to an existing group.

Action: See accompanying errors. Fix the problem or use another file.

ORA-00365 the specified log is not the correct next log

Cause: The specified log failed to pass checks to ensure it corresponds to the log that was just applied. This is probably the result of using a log that was generated against a cold backup image of the database.

Action: Find the log that was generated by this copy of the database and give that file name to recovery.

ORA-00366 log string of thread string, checksum error in the file header

Cause: The file header for the redo log contains a checksum that does not match the value calculated from the file header as read from disk. This means the file header is corrupted.

Action: Find and install correct version of the log or reset the logs.

ORA-00367 checksum error in log file header

Cause: The file header for the redo log contains a checksum that does not match the value calculated from the file header as read from disk. This means the file header is corrupted.

Action: Find the correct file and try again.

ORA-00368 checksum error in redo log block

Cause: The redo block indicated by the accompanying error, is not valid. It has a checksum that does not match the block contents.

Action: Perform recovery with a good version of the log or do time-based recovery up to the indicated time. If this happens when archiving, archiving of the problem log can be skipped by clearing the log with the UNARCHIVED option. This must be followed by a backup of every datafile to insure recoverability of the database. Restore the correct file or reset logs.

ORA-00369 Current log of thread string not useable and other log being cleared

Cause: An attempt to open the thread failed because it is necessary to switch redo generation to another online log, but all the other logs are being cleared or need to be archived before they can be used.

Action: If the ALTER DATABASE CLEAR LOGFILE command is still active, then wait for it to complete. Otherwise, reissue the CLEAR command. If there are other online logs for the thread that are not being cleared, then archive the logs.

ORA-00371 not enough shared pool memory

Cause: The SHARED_POOL_SIZE initialization parameter is too small.

Action: Increase the parameter value.

ORA-00372 file string cannot be modified at this time

Cause: An attempt was made to modify the contents of a file that cannot be modified. The file is most likely part of a read-only tablespace but may be in the process of going offline, or the database may be in the process of closing.

Action: Check the status of the file and its tablespace.

ORA-00373 online log version string incompatible with ORACLE versionstring

Cause: The online log was written by an incompatible version of Oracle. This can occur when the log file was created by either a new or older version of Oracle.

Action: Recover the database with the compatible software, shut it down cleanly, and then restart with current software.

ORA-00374 parameter db_block_size = string invalid; must be a multiple ofstring in the range [string..string]

Cause: An invalid value was specified for the DB_BLOCK_SIZE parameter.

Action: Adjust the value of the parameter and restart the instance.

ORA-00375 unable to get default db_block_size

Cause: The system was unable to determine the default value for DB_BLOCK_SIZE.

Action: See the accompanying system-specific error. As a workaround, specify the block size in the initialization parameter file.

ORA-00376 file string cannot be read at this time

Cause: An attempt was made to read from a file that is not readable. Most likely the file is offline.

Action: Check the state of the file. Bring it online.

ORA-00377 Frequent backups of file string causing write operation to stall

Cause: Backups are occurring too frequently on this file. Each time a new backup is started for a file, any writes which have been previously issued (but not completed) have to be re-issued. If hot backups are started very, very frequently, it is possible that some writes will be re-issued repeatedly and never complete.

Action: Increase the interval between begin hot-backup commands for this file.

ORA-00378 buffer pools cannot be created as specified

Cause: The number of buffers or the number of LRU latches is too small to satisfy the specified buffer pool configuration.

Action: Either increase the number of buffers and/or number of LRU latches or configure smaller buffer pools.

ORA-00379 no free buffers available in buffer pool string for block sizestringK

Cause: All buffers in the specified buffer pool for the specified block size are in use and no free buffers are available.

Action: Increase the number of buffers in the specified pool for the specified block size.

ORA-00380 cannot specify db_numberk_cache_size sincenumberK is the standard block size

Cause: User specified the parameter DB_nK_CACHE_SIZE (wheren is one of 2,4,8,16,32), while the standard block size for this database is equal ton Kbytes. This is illegal.

Action: Specify the standard block size cache using DB_CACHE_SIZE (DEFAULT pool) (and DB_RECYCLE_CACHE_SIZE, DB_KEEP_CACHE_SIZE if additional buffer pools are required). Do NOT use the corresponding DB_nK_CACHE_SIZE parameter for the standard block size.

ORA-00381 cannot use both new and old parameters for buffer cache size specification

Cause: User specified one or more of {DB_CACHE_SIZE, DB_RECYCLE_CACHE_SIZE, DB_KEEP_CACHE_SIZE, DB_nK_CACHE_SIZE (wheren is one of {2, 4, 8, 16, 32}) AND one or more of {DB_BLOCK_BUFFERS, BUFFER_POOL_KEEP, BUFFER_POOL_RECYCLE}. This is illegal.

Action: Use EITHER the old (pre-Oracle 9.0.0) parameters OR the new ones. Don't specify both. If old size parameters are specified in the parameter file, you may want to replace them with new parameters since the new parameters can be modified dynamically and allow you to configure additional caches for additional block sizes.

ORA-00382 string not a valid block size, valid range [string..string]

Cause: User specified a value for DB_nK_CACHE_SIZE where n is one of {2, 4, 8, 16, 32}, butnk is not a valid block size for this platform.

Action: Remove corresponding parameter from the initialization parameter file and restart the instance.

ORA-00383 DEFAULT cache for blocksize string cannot be reduced to zero

Cause: User attempted to reduce DB_CACHE_SIZE to zero, or attempted to reduce DB_nK_CACHE_SIZE to zero while there were still online tablespaces with block sizenK. Note that since the SYSTEM tablespace cannot be taken offline, it is always illegal to set DB_CACHE_SIZE to zero.

Action: Offline any tablespaces with the corresponding block size and then perform the operation again.

ORA-00384 Insufficient memory to grow cache

Cause: The system could not allocate sufficient memory to grow the cache to the specified size.

Action: Attempt a smaller increase in the value of the parameter.

ORA-00390 log string of thread string is being cleared, cannot become current log

Cause: An attempt to switch to a new online log for the redo thread failed because no reusable log could be found. This log is being cleared and will be usable when the clearing completes. The command that began the clearing may have terminated without completing the clearing.

Action: If the clear command is still executing, then wait for its completion. If it terminated, then reissue the clear command, or drop the log.

ORA-00391 All threads must switch to new log format at the same time

Cause: An attempt to switch the current log of a single thread is not allowed because the compatibility requirements force a new log format version number. When changing log formats, all threads must switch to the new format at the same time.

Action: Open the database to cause the coordinated log switch. If that is not possible, then return to the same software version and compatibility setting last used to open the database.

ORA-00392 log string of thread string is being cleared, operation not allowed

Cause: An operation encountered this online log in the middle of being cleared. The command that began the clearing may have terminated without completing the clearing.

Action: If the clear command is still executing, then wait for its completion. If it terminated, then reissue the clear command or drop the log.

ORA-00393 log string of thread string is needed for recovery of offline datafiles

Cause: Log cannot be cleared because the redo in it is needed to recover offline datafiles. It has not been archived so there is no other copy available. If the log is cleared, the tablespaces containing the files will have to be dropped.

Action: Archive the log and then repeat the clear command. If archiving is not possible, and dropping the tablespaces is acceptable, then add the clause UNRECOVERABLE DATAFILE at the end of the clear command.

ORA-00394 online log reused while attempting to archive it

Cause: An attempt was made to reuse an online log file that is being archived.

Action: The online log file has been overwritten; it cannot be archived.

ORA-00395 online logs for the clone database must be renamed

Cause: A clone database open forces log file renaming to avoid overwriting the primary log files.

Action: Rename the log files manually or using the LOG_FILE_NAME_CONVERT initialization parameter.

ORA-00396 error string required fallback to single-pass recovery

Cause: The indicated error caused two-pass instance or crash recovery to fail. Recovery was retried with an alternate (slower) method to avoid the error.

Action: Correct the cause of the indicated error (also recorded) so that future instance or crash recovery can succeed with the new algorithm. This usually requires making more main storage available to the recovery process.

ORA-00397 lost write detected for file string, blockstring

Cause: The specified block is missing changes that should have been written to disk, indicating a lost write by the file I/O subsystem or volume manager.

Action: Run diagnostic checks on the I/O subsystem and resolve any errors

ORA-00398 abort thread recovery due to reconfiguration

Cause: Global enqueue service reconfiguration occurred during instance/crash recovery.

Action: This is used internally, no action is required.

ORA-00399 corrupt change description in redo log

Cause: A change vector in the redo log failed validation checks.

Action: Do recovery with a good version of the log or do time based recovery up to the indicated time.

ORA-00400 invalid release value string for parameterstring

Cause: The release level given for the specified initialization parameter is invalid.

Action: Correct the parameter value in the parameter file and retry.

ORA-00401 the value for parameter string is not supported by this release

Cause: The value specified cannot be supported by this release of the software.

Action: Choose an appropriate value, or remove the parameter value to use the default value.

ORA-00402 database changes by release string cannot be used by releasestring

Cause: Changes have been made to the database that require a newer software release or that violate the compatibility parameters.

Action: Use a version of the software that can understand the changes or relax the compatibility requirements in the initialization file.

ORA-00403 string (string) is not the same as other instances (string)

Cause: Another instance has set the COMPATIBLE or COMPATIBLE NO RECOVERY parameters differently than this instance.

Action: Change the parameters of the current instance to match other instances already running.

ORA-00404 Convert file not found: 'string'

Cause: The file used for converting the database from V7 to V8 could not be found.

Action: Verify that the migration process has been started on this database and that the convert file name is accessible.

ORA-00405 compatibility type "string"

Cause: Reporting a type associated with another error.

Action: See the accompanying error.

ORA-00406 COMPATIBLE parameter needs to be string or greater

Cause: The value of the COMPATIBLE initialization parameter is not high enough to allow the operation. Allowing the command would make the database incompatible with the release specified by the current COMPATIBLE parameter.

Action: Shut down and restart with a higher compatibility setting.

ORA-00407 rolling upgrade from release string.string tostring.string is not allowed

Cause: Another instance executing software at a different point release already has the database mounted.

Action: Shut down all instances then restart with the new software.

ORA-00408 parameter string is set to TRUE

Cause: Reporting the parameter that resulted in the compatibility error.

Action: Shut down and restart with a higher compatibility setting.

ORA-00409 COMPATIBLE needs to be string or higher to use AUTO SEGMENT SPACE MANAGEMENT

Cause: This is due to upgrading from an older release of Oracle with tablespaces created using automatic segment-space management. To open the database, theCOMPATIBLE parameter needs to be set to the specified value or higher.

Action: Shut down and start up with the specified compatibility setting.

ORA-00436 ORACLE is not licensed. Contact Oracle Corp. for assistance

Cause: This installed Oracle software is not licensed to run on this CPU. This can also occur if Oracle software has been installed incorrectly, for example, with the wrong licensing codes.

Action: Check that Oracle is installed correctly. Then contact Oracle Support Services.

ORA-00437 ORACLE feature is not licensed. Contact Oracle Corp. for assistance

Cause: This installed Oracle feature is not licensed to run on this CPU. This can also occur if Oracle software has been installed incorrectly, for example, with the wrong licensing codes.

Action: Check that Oracle is installed correctly. Then contact Oracle Support Services.

ORA-00438 string Option not installed

Cause: The specified option is not installed.

Action: Either avoid calling the option, or purchase and install the option.

ORA-00439 feature not enabled: string

Cause: The specified feature is not enabled.

Action: Do not attempt to use this feature.

ORA-00443 background process "string" did not start

Cause: The specified process did not start.

Action: Ensure that the executable image is in the correct place with the correct protections, and that there is enough memory.

ORA-00444 background process "string" failed while starting

Cause: Usually due to a bad (or non-existent) background process image.

Action: Get a good background process image.

ORA-00445 background process "string" did not start afterstring seconds

Cause: The specified process did not start after the specified time.

Action: Ensure that the background did not die and leave a trace file.

ORA-00446 background process started when not expected

Cause: The background process specified started after Oracle was already running.

Action: Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the other messages. If no user on site started the process, report the message to Oracle Support Services.

ORA-00447 fatal error in background process

Cause: One of the background processes died unexpectedly.

Action: Restart the system. Check and, if necessary, correct the problem indicated by the background trace file in BACKGROUND_DUMP_DEST.

ORA-00448 normal completion of background process

Cause: One of the background processes completed normally as requested by the user.

Action: If you are solving a problem, check for other messages and the background process trace file. Correct the problem mentioned in the other messages. Then shut down and restart Oracle.

ORA-00449 background process 'string' unexpectedly terminated with errorstring

Cause: A foreground process needing service from a background process has discovered the process died.

Action: Refer to the message code given in the message and the trace file for the foreground and the background processes.

ORA-00470 LGWR process terminated with error

Cause: The Log Writer process terminated abnormally.

Action: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.

ORA-00471 DBWR process terminated with error

Cause: The Database Writer process terminated abnormally.

Action: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.

ORA-00472 PMON process terminated with error

Cause: The Process Monitor process terminated abnormally.

Action: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.

ORA-00473 ARCH process terminated with error

Cause: The Archiver process terminated abnormally.

Action: Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.

ORA-00474 SMON process terminated with error

Cause: The System Monitor process terminated abnormally.

Action: Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.

ORA-00475 TRWR process terminated with error

Cause: The system tracing process terminated abnormally.

Action: Restart the instance.

ORA-00476 RECO process terminated with error

Cause: The distributed transaction (two-phase commit) recovery process terminated abnormally.

Action: Restart the instance.

ORA-00477 SNP* process terminated with error

Cause: A materialized view refresh process terminated abnormally.

Action: PMON will restart SNP process shortly. If SNP process does not get started, contact Oracle Support Services.

ORA-00478 SMON process terminated due to error string

Cause: SMON was unable to service the requests due to an error in cleanup of resources.

Action: Warm start the instance.

ORA-00480 LCK* process terminated with error

Cause: One Lock process terminated abnormally.

Action: Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.

ORA-00481 LMON process terminated with error

Cause: The global enqueue service monitor process terminated abnormally.

Action: Restart the instance.

ORA-00482 LMD* process terminated with error

Cause: A global enqueue service daemon process terminated abnormally.

Action: Restart the instance.

ORA-00483 During shutdown a process abnormally terminated

Cause: One of the background processes did not exit normally at or near the time of shutdown.

Action: Use the SHUTDOWN ABORT command. Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.

ORA-00484 LMS* process terminated with error

Cause: A global cache service process terminated abnormally.

Action: Warm start the instance.

ORA-00485 DIAG process terminated with error string

Cause: A global diagnostic process died.

Action: Wait for the process to restart.

ORA-00568 Maximum number of interrupt handlers exceeded

Cause: The number of registered interrupt handling routines for when the break key is entered exceeds the maximum allowed.

Action: Reduce the number of registered interrupt handlers.

ORA-00600 internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]

Cause: This is the generic internal error number for Oracle program exceptions. It indicates that a process has encountered a low-level, unexpected condition. Causes of this message include:

• timeouts
• file corruption
• failed data checks in memory
• hardware, memory, or I/O errors
• incorrectly restored files

The first argument is the internal message number. Other arguments are various numbers, names, and character strings. The numbers may change meanings between different versions of Oracle.

Action: Report this error to Oracle Support Services after gathering the following information:

• events that led up to the error
• the operations that were attempted that led to the error
• the conditions of the operating system and databases at the time of the error
• any unusual circumstances that occurred before receiving the ORA-00600 message
• contents of any trace files generated by the error
• the relevant portions of the Alter files

Note: The cause of this message may manifest itself as different errors at different times. Be aware of the history of errors that occurred before this internal error.

ORA-00601 cleanup lock conflict

Cause: The Process Monitor encountered a lock conflict while trying to recover processes. This is an internal error message not usually issued.

Action: Contact Oracle Support Services.

ORA-00602 internal programming exception

Cause: Internal programming exception occurred.

Action: Report this error as a program bug to Oracle Support Services.

ORA-00603 ORACLE server session terminated by fatal error

Cause: An Oracle Server session is in an unrecoverable state.

Action: Log in to Oracle again so a new server session will be created automatically. Examine the session trace file for more information.

ORA-00604 error occurred at recursive SQL level string

Cause: An error occurred while processing a recursive SQL statement (a statement applying to internal dictionary tables).

Action: If the situation described in the next error on the stack can be corrected, do so; otherwise contact Oracle Support Services.

ORA-00606 Internal error code

Cause: A call to deferred UPI functions was made in non-deferred mode.

Action: Contact Oracle Support Services.

ORA-00607 Internal error occurred while making a change to a data block

Cause: An internal error or memory exception occurred while Oracle was applying redo to a data block.

Action: Contact Oracle Support Services.

ORA-00701 object necessary for warmstarting database cannot be altered

Cause: An attempt was made to alter or drop a database object (table, cluster, or index) defined in the control file's bootstrap segment and needed to warm start the database.

Action: Correct the spelling of the object name or remove it from the ALTER or DROP statement.

ORA-00702 bootstrap verison 'string' inconsistent with version 'string'

Cause: The version of the bootstrap data is incompatible with the current version of the software.

Action: Restore a version of the software that is compatible with the datafiles.

ORA-00703 maximum number of row cache instance locks exceeded

Cause: There are not enough row cache enqueues.

Action: Increase the value of the ROW CACHE ENQUEUE parameter and restart the system.

ORA-00704 bootstrap process failure

Cause: Failure in processing bootstrap data. Refer to the accompanying messages for more information about the cause of the problem.

Action: Correct the problems mentioned in the other messages. If the problem persists, contact Oracle Support Services.

ORA-00705 inconsistent state during start up; shut down the instance, then restart it

Cause: A previous attempt to start an instance was terminated.

Action: Shut down the instance completely and then restart it.

ORA-00706 error changing format of file 'string'

Cause: An attempt to change the block0 format of the specified file failed because the file is read-only or offline.

Action: Make the file read-write or bring the file online and set theBLK0_FMTCHG event.

ORA-00816 error message translation failed

Cause: There is an internal error where a routine was unable to translate a message code.

Action: Contact Oracle Support Services.

---

Copyright © 1996, 2002 Oracle Corporation.
All Rights Reserved.
Home
Book List
Contents
Index
Master Index
Feedback

Skip Headers

Oracle9i Database Error Messages
Release 2 (9.2)
Part Number A96525-01
Home
Book List
Contents
Index
Master Index
Feedback

---

 

3
ORA-00900 to ORA-01499

ORA-00900 invalid SQL statement

Cause: The statement is not recognized as a valid SQL statement. This error can occur if the Procedural Option is not installed and a SQL statement is issued that requires this option (for example, a CREATE PROCEDURE statement). You can determine if the Procedural Option is installed by starting SQL*Plus. If the PL/SQL banner is not displayed, then the option is not installed.

Action: Correct the syntax or install the Procedural Option.

ORA-00901 invalid CREATE command

Cause: The CREATE command was not followed by a valid CREATE option.

Action: Correct the syntax.

ORA-00902 invalid datatype

Cause: The datatype entered in the CREATE or ALTER TABLE statement is not valid.

Action: Correct the syntax.

ORA-00903 invalid table name

Cause: A table or cluster name is invalid or does not exist. This message is also issued if an invalid cluster name or no cluster name is specified in an ALTER CLUSTER or DROP CLUSTER statement.

Action: Check spelling. A valid table name or cluster name must begin with a letter and may contain only alphanumeric characters and the special characters $, _, and #. The name must be less than or equal to 30 characters and cannot be a reserved word.

ORA-00904 string: invalid identifier

Cause: The column name entered is either missing or invalid.

Action: Enter a valid column name. A valid column name must begin with a letter, be less than or equal to 30 characters, and consist of only alphanumeric characters and the special characters $, _, and #. If it contains other characters, then it must be enclosed in double quotation marks. It may not be a reserved word.

ORA-00905 missing keyword

Cause: A required keyword is missing.

Action: Correct the syntax.

ORA-00906 missing left parenthesis

Cause: A required left parenthesis has been omitted. Certain commands, such as CREATE TABLE, CREATE CLUSTER, and INSERT, require a list of items enclosed in parentheses. Parentheses also are required around subqueries in WHERE clauses and in UPDATE table SET column = (SELECT...) statements.

Action: Correct the syntax, inserting a left parenthesis where required, and retry the statement.

ORA-00907 missing right parenthesis

Cause: A left parenthesis has been entered without a closing right parenthesis, or extra information was contained in the parentheses. All parentheses must be entered in pairs.

Action: Correct the syntax and retry the statement.

ORA-00908 missing NULL keyword

Cause: Either of the following: In a CREATE TABLE or ALTER TABLE statement, NOT was entered to specify that no null values are allowed in that column, but the keyword NULL was omitted. In the IS [NOT] NULL logical operator, the keyword NULL was not found. For example, the following statement generates this message:

SELECT * FROM EMP WHERE DEPTNO IS NOT; 

The keyword NULL must follow the keywords IS NOT.

Action: Correct the syntax.

ORA-00909 invalid number of arguments

Cause: An Oracle function was referenced with an incorrect number of arguments. All Oracle functions, except for SYSDATE, require at least one argument.

Action: Correct the syntax of the function by entering the required number of arguments.

ORA-00910 specified length too long for its datatype

Cause: No size was specified for a character field or the size was invalid. A maximum length must be specified for each character column. The maximum value for this length varies for each character datatype, such as CHAR or VARCHAR2.

Action: Enter a maximum length for the field.

ORA-00911 invalid character

Cause: Special characters are valid only in certain places. If special characters other than $, _, and # are used in a name and the name is not enclosed in double quotation marks ("), this message will be issued. One exception to this rule is for database names; in this case, double quotes are stripped out and ignored.

Action: Remove the invalid character from the statement or enclose the object name in double quotation marks.

ORA-00913 too many values

Cause: The SQL statement requires two sets of values equal in number. This error occurs when the second set contains more items than the first set. For example, the subquery in a WHERE or HAVING clause may return too many columns, or a VALUES or SELECT clause may return more columns than are listed in the INSERT.

Action: Check the number of items in each set and change the SQL statement to make them equal.

ORA-00914 missing ADD keyword

Cause: The keyword ADD does not precede one of the following:

• The keyword log file in anALTER DATABASE statement
• A column element or table constraint in an ALTER TABLE statement
• The keyword DATAFILE in an ALTER TABLESPACE statement

Action: Specify the keyword ADD in the ALTER statement.

ORA-00915 network access of dictionary table not currently allowed

Cause: This is an internal error message not usually issued.

Action: Contact Oracle Support Services.

ORA-00917 missing comma

Cause: A required comma has been omitted from a list of columns or values in an INSERT statement or a list of the form ((C,D),(E,F), ...).

Action: Correct the syntax.

ORA-00918 column ambiguously defined

Cause: A column name used in a join exists in more than one table and is thus referenced ambiguously. In a join, any column name that occurs in more than one of the tables must be prefixed by its table name when referenced. The column should be referenced as TABLE.COLUMN or TABLE_ALIAS.COLUMN. For example, if tables EMP and DEPT are being joined and both contain the column DEPTNO, then all references to DEPTNO should be prefixed with the table name, as in EMP.DEPTNO or E.DEPTNO.

Action: Prefix references to column names that exist in multiple tables with either the table name or a table alias and a period (.), as in the examples above.

ORA-00919 invalid function

Cause: An entry was formatted like a function call, but it is not recognizable as an Oracle function.

Action: Correct the syntax.

ORA-00920 invalid relational operator

Cause: A search condition was entered with an invalid or missing relational operator.

Action: Include a valid relational operator such as =, !=, ^=, <>, >, <, >=, <=, ALL, ANY, [NOT] BETWEEN, EXISTS, [NOT] IN, IS [NOT] NULL, or [NOT] LIKE in the condition.

ORA-00921 unexpected end of SQL command

Cause: The SQL command was not complete. Part of a valid command was entered, but at least one major component was omitted.

Action: Correct the syntax.

ORA-00922 missing or invalid option

Cause: An invalid option was specified in defining a column or storage clause. The valid option in specifying a column is NOT NULL to specify that the column cannot contain any NULL values. Only constraints may follow the datatype. Specifying a maximum length on a DATE or LONG datatype also causes this error.

Action: Correct the syntax. Remove the erroneous option or length specification from the column or storage specification.

ORA-00923 FROM keyword not found where expected

Cause: In a SELECT or REVOKE statement, the keyword FROM was either missing, misplaced, or misspelled. The keyword FROM must follow the last selected item in a SELECT statement or the privileges in a REVOKE statement.

Action: Correct the syntax. Insert the keyword FROM where appropriate. The SELECT list itself also may be in error. If quotation marks were used in an alias, check that double quotation marks enclose the alias. Also, check to see if a reserved word was used as an alias.

ORA-00924 missing BY keyword

Cause: The keyword BY was omitted in a GROUP BY, ORDER BY, or CONNECT BY clause. In a GRANT statement, the keyword IDENTIFIED must also be followed by the keyword BY.

Action: Correct the syntax. Insert the keyword BY where required and then retry the statement.

ORA-00925 missing INTO keyword

Cause: An INSERT statement has been entered without the keyword INTO.

Action: Correct the syntax. Insert the keyword INTO where required and then retry the statement.

ORA-00926 missing VALUES keyword

Cause: An INSERT statement has been entered without the keyword VALUES or SELECT. Either a VALUES clause or a SELECT subquery must follow the INSERT INTO clause.

Action: Correct the syntax. Enter either a VALUES clause or a subquery after the INSERT INTO clause.

ORA-00927 missing equal sign

Cause: An equal sign has been omitted in one of the following places:

• In the SET clause of an UPDATE statement
• Following "!" in a search condition to signify not equal

Action: Correct the syntax. Insert the equal sign where required and retry the statement.

ORA-00928 missing SELECT keyword

Cause: A SELECT subquery must be included in a CREATE VIEW statement.

Action: Correct the syntax. Insert the required SELECT clause after the CREATE VIEW clause and then retry the statement.

ORA-00929 missing period

Cause: This is an internal error message not usually issued.

Action: Contact Oracle Support Services.

ORA-00930 missing asterisk

Cause: This is an internal error message not usually issued.

Action: Contact Oracle Support Services.

ORA-00931 missing identifier

Cause: The specified string does not contain an identifier.

Action: Correct the string argument.

ORA-00932 inconsistent datatypes: expected string gotstring

Cause: One of the following:

• An attempt was made to perform an operation on incompatible datatypes. For example, adding a character field to a date field (dates may only be added to numeric fields) or concatenating a character field with a long field.
• An attempt was made to perform an operation on a database object (such as a table or view) that is not intended for normal use. For example, system tables cannot be modified by a user. Note that on rare occasions this error occurs because a misspelled object name matched a restricted object's name.
• An attempt was made to use an undocumented view.

Action: If the cause is

• different datatypes, then use consistent datatypes. For example, convert the character field to a numeric field with the TO_NUMBER function before adding it to the date field. Functions may not be used with long fields.
• an object not intended for normal use, then do not access the restricted object.

ORA-00933 SQL command not properly ended

Cause: The SQL statement ends with an inappropriate clause. For example, an ORDER BY clause may have been included in a CREATE VIEW or INSERT statement. ORDER BY cannot be used to create an ordered view or to insert in a certain order.

Action: Correct the syntax by removing the inappropriate clauses. It may be possible to duplicate the removed clause with another SQL statement. For example, to order the rows of a view, do so when querying the view and not when creating it. This error can also occur in SQL*Forms applications if a continuation line is indented. Check for indented lines and delete these spaces.

ORA-00934 group function is not allowed here

Cause: One of the group functions, such as AVG, COUNT, MAX, MIN, SUM, STDDEV, or VARIANCE, was used in a WHERE or GROUP BY clause.

Action: Remove the group function from the WHERE or GROUP BY clause. The desired result may be achieved by including the function in a subquery or HAVING clause.

ORA-00935 group function is nested too deeply

Cause: This is an internal error message not usually issued.

Action: Contact Oracle Support Services.

ORA-00936 missing expression

Cause: A required part of a clause or expression has been omitted. For example, a SELECT statement may have been entered without a list of columns or expressions or with an incomplete expression. This message is also issued in cases where a reserved word is misused, as in SELECT TABLE.

Action: Check the statement syntax and specify the missing component.

ORA-00937 not a single-group group function

Cause: A SELECT list cannot include both a group function, such as AVG, COUNT, MAX, MIN, SUM, STDDEV, or VARIANCE, and an individual column expression, unless the individual column expression is included in a GROUP BY clause.

Action: Drop either the group function or the individual column expression from the SELECT list or add a GROUP BY clause that includes all individual column expressions listed.

ORA-00938 not enough arguments for function

Cause: The function was referenced with too few arguments.

Action: Check the function syntax and specify the required number of arguments.

ORA-00939 too many arguments for function

Cause: The function was referenced with too many arguments.

Action: Check the function syntax and specify only the required number of arguments.

ORA-00940 invalid ALTER command

Cause: An invalid ALTER option was specified.

Action: Correct the syntax.

ORA-00941 missing cluster name

Cause: The cluster name was either missing or invalid.

Action: Specify a valid cluster name. A valid cluster name must start with a letter, be less than or equal to 30 characters, and contain only alphanumeric characters or the special characters $, _, and #. It may not be a reserved word. The name must be specified immediately following the keywords CREATE CLUSTER.

ORA-00942 table or view does not exist

Cause: The table or view entered does not exist, a synonym that is not allowed here was used, or a view was referenced where a table is required. Existing user tables and views can be listed by querying the data dictionary. Certain privileges may be required to access the table. If an application returned this message, the table the application tried to access does not exist in the database, or the application does not have access to it.

Action: Check each of the following:

• the spelling of the table or view name.
• that a view is not specified where a table is required.
• that an existing table or view name exists.

Contact the database administrator if the table needs to be created or if user or application privileges are required to access the table.

Also, if attempting to access a table or view in another schema, make certain the correct schema is referenced and that access to the object is granted.

ORA-00943 cluster does not exist

Cause: The current user owns no cluster by the specified name.

Action: Specify a valid cluster name following the keyword CLUSTER, then retry the statement.

ORA-00944 insufficient number of clustered columns

Cause: An attempt was made to create a table with fewer cluster columns than were specified in the CREATE CLUSTER statement. The CLUSTER clause of a CREATE TABLE statement must specify all cluster columns that were defined when the cluster was created.

Action: Specify all cluster columns in the CREATE TABLE statement, then retry it.

ORA-00945 specified clustered column does not exist

Cause: A column specified in the cluster clause of a CREATE TABLE statement is not a column in this table.

Action: Re-execute the statement, using the names of columns defined for the table.

ORA-00946 missing TO keyword

Cause: A GRANT statement was specified without the keyword TO, or an invalid form of the GRANT command was entered.

Action: Check the syntax for the GRANT command, insert the keyword TO where required, and retry the statement.

ORA-00947 not enough values

Cause: This error occurs when a SQL statement requires two sets of values equal in number, but the second set contains fewer items than the first set. This can occur in a WHERE or HAVING clause in which a nested SELECT returns too few columns as in:

WHERE (A,B) IN (SELECT C FROM ...) 

Another common cause of this error is an INSERT statement in which the VALUES or SELECT clause does not contain enough values needed for the INSERT, as in

INSERT INTO EMP(EMPNO,ENAME) VALUES('JONES') 

Action: Check the number of items in each set and change the SQL statement to make them equal.

ORA-00948 ALTER CLUSTER statement no longer supported

Cause: The ALTER CLUSTER statement has been withdrawn.

Action: To add data to a cluster from an existing table, use the following series of SQL statements:

CREATE TABLE newtable SELECT * FROM oldtable CLUSTER clustername;DROP oldtable;RENAME TABLE newtable oldtable; 

ORA-00949 illegal reference to remote database

Cause: This is an internal error message not usually issued.

Action: Contact Oracle Support Services.

ORA-00950 invalid DROP option

Cause: A DROP command was not followed by a valid DROP option, such as CLUSTER, DATABASE LINK, INDEX, ROLLBACK SEGMENT, SEQUENCE, SYNONYM, TABLE, TABLESPACE, or VIEW.

Action: Check the command syntax, specify a valid DROP option, then retry the statement.

ORA-00951 cluster not empty

Cause: A DROP CLUSTER statement specified a cluster that is not empty. A cluster may not be dropped if it contains any tables, unless the optional INCLUDING TABLES clause is specified. Tables may also be removed from a cluster by using the DROP TABLE command.

Action: Either specify the INCLUDING TABLES clause in the DROP CLUSTER statement or remove all tables from the cluster with the DROP TABLE command before issuing the DROP CLUSTER command.

ORA-00952 missing GROUP keyword

Cause: Groups are not currently implemented.

Action: No user action required.

ORA-00953 missing or invalid index name

Cause: In a CREATE INDEX, DROP INDEX, or VALIDATE INDEX statement, the index name was missing or invalid.

Action: Specify a valid index name after the keyword INDEX. To drop or validate an existing index, check the name by querying the data dictionary. To create a new index, check the syntax before retrying.

ORA-00954 missing IDENTIFIED keyword

Cause: A GRANT CONNECT statement was issued without the keyword IDENTIFIED.

Action: Check the syntax and insert the keyword IDENTIFIED after the last username. The format is

GRANT CONNECT TO user-list IDENTIFIED BY password-list; 

ORA-00955 name is already used by an existing object

Cause: An attempt was made to create a database object (such as a table, view, cluster, index, or synonym) that already exists. A user's database objects must have distinct names.

Action: Enter a unique name for the database object or modify or drop the existing object so it can be reused.

ORA-00956 missing or invalid auditing option

Cause: An AUDIT or NOAUDIT command was not followed by a valid option or the keyword ALL. For example, when AUDITing tables an option such as ALTER, AUDIT, COMMENT, DELETE, GRANT, INDEX, INSERT, LOCK, RENAME, SELECT, or UPDATE must be specified.

Action: Correct the syntax.

ORA-00957 duplicate column name

Cause: A column name was specified twice in a CREATE or INSERT statement. Column names must be unique within a table, view, or cluster.

Action: In a CREATE statement, change one of the column names to a new, unique column name. In an INSERT statement, remove one of the duplicate names.

ORA-00958 missing CHECK keyword

Cause: The keyword CHECK should follow the keyword WITH in the WITH OPTION clause of the CREATE VIEW statement.

Action: Check the statement syntax and insert the keyword CHECK where required. Then retry the statement.

ORA-00959 tablespace 'string' does not exist

Cause: A statement specified the name of a tablespace that does not exist.

Action: Enter the name of an existing tablespace. For a list of tablespace names, query the data dictionary.

ORA-00960 ambiguous column naming in select list

Cause: A column name in the order-by list matches more than one select list columns.

Action: Remove duplicate column naming in select list.

ORA-00961 bad datetime/interval value

ORA-00962 too many group-by / order-by expressions

Cause: The group-by or order-by column list contain more than 1000 expressions.

Action: Use no more than 1000 expressions in the group-by or order-by list.

ORA-00963 unsupported interval type

Cause: An unsupported interval type was encountered.

Action: Use a valid interval type.

ORA-00964 table name not in FROM list

Cause: A table specified in a query's SELECT list is not named in the FROM clause list.

Action: Check spelling of the table names, check that each table name in the SELECT list matches a table name in the FROM list, and then retry the statement.

ORA-00965 column aliases not allowed for '*'

Cause: An alias was used with the return-all-columns function (*) in the SELECT list. For example:

SELECT * COL_ALIAS FROM EMP; 

Action: Either specify individual columns or do not specify an alias with a "*".

ORA-00966 missing TABLE keyword

Cause: A LOCK statement was specified and the keyword TABLE was missing, misspelled, or misplaced. A LOCK statement must begin with LOCK TABLEtablename.

Action: Correct the syntax.

ORA-00967 missing WHERE keyword

Cause: The keyword WHERE in a SELECT statement was missing, misspelled, or misplaced.

Action: Correct the syntax.

ORA-00968 missing INDEX keyword

Cause: The keyword INDEX in a CREATE UNIQUE INDEX or VALIDATE INDEX statement was missing, misspelled, or misplaced.

Action: Correct the syntax.

ORA-00969 missing ON keyword

Cause: The keyword ON in a GRANT, REVOKE, or CREATE INDEX statement was missing, misspelled, or misplaced.

Action: Check syntax and spelling, and use the keyword ON where required.

ORA-00970 missing WITH keyword

Cause: The keyword START was specified without the keyword WITH. Both keywords are necessary if a START WITH clause is desired in a tree-structured query.

Action: Change the keyword START to the keywords START WITH. Then retry the statement.

ORA-00971 missing SET keyword

Cause: The keyword SET in an UPDATE statement is missing, misspelled, or misplaced.

Action: Check syntax and spelling, and use the keyword SET after the name of the table to be updated.

ORA-00972 identifier is too long

Cause: The name of a schema object exceeds 30 characters. Schema objects are tables, clusters, views, indexes, synonyms, tablespaces, and usernames.

Action: Shorten the name to 30 characters or less.

ORA-00973 invalid row count estimate

ORA-00974 invalid PCTFREE value (percentage)

Cause: The percentage of free space specified in a CREATE INDEX statement is not between 0 and 100. A PCTFREE value of 0 means the entire block is available. The value 100 is not useful because it means that no data may be inserted. The default is 10.

Action: Specify a PCTFREE value between 0 and 100. Then retry the statement.

ORA-00975 date + date not allowed

Cause: An attempt was made to add two date fields together. Dates may be added only to numeric fields, not to other dates.

Action: Use the Oracle function TO_NUMBER to convert one of the date fields to a numeric field before adding it to the other date field.

ORA-00976 LEVEL, PRIOR, or ROWNUM not allowed here

Cause: The use of the PRIOR clause, the pseudo-column LEVEL, or ROWNUM is incorrect in this context.

Action: Check the syntax for the SQL statement. Then remove or relocate the keyword PRIOR, LEVEL, or ROWNUM.

ORA-00977 duplicate auditing option

Cause: An AUDIT or NOAUDIT statement specified the same option more than once.

Action: Either specify ALL without other auditing options or remove the duplicate auditing specifications.

ORA-00978 nested group function without GROUP BY

Cause: A group function, such as AVG, COUNT, MAX, MIN, SUM, STDDEV, or VARIANCE, was used within another group function, as in MAX(COUNT(*)), without a corresponding GROUP BY clause.

Action: Either add a GROUP BY clause or remove the extra level of nesting.

ORA-00979 not a GROUP BY expression

Cause: The GROUP BY clause does not contain all the expressions in the SELECT clause. SELECT expressions that are not included in a group function, such as AVG, COUNT, MAX, MIN, SUM, STDDEV, or VARIANCE, must be listed in the GROUP BY clause.

Action: Include in the GROUP BY clause all SELECT expressions that are not group function arguments.

ORA-00980 synonym translation is no longer valid

Cause: The synonym used is based on a table, view, or synonym that no longer exists.

Action: Replace the synonym with the name of the object it references or re-create the synonym so that it refers to a valid table, view, or synonym.

ORA-00981 cannot mix table and system auditing options

Cause: Both table-wide and system-wide options were specified within a single AUDIT statement.

Action: Check the AUDIT command syntax. Then retry one or more AUDIT statements.

ORA-00982 missing plus sign

Cause: A left parenthesis appeared in a join condition, but a plus sign (+) did not follow. A left parenthesis in a join condition usually signals an outer-join specification and so a plus sign is expected to follow. To specify an outer join on a column in a join operation, follow the column reference in the join condition with a plus sign (+) enclosed in parentheses.

Action: Correct the SQL syntax and retry the statement.

ORA-00984 column not allowed here

Cause: A column name was used in an expression where it is not permitted, such as in the VALUES clause of an INSERT statement.

Action: Check the syntax of the statement and use column names only where appropriate.

ORA-00985 invalid program name

Cause: Probably a syntax error.

Action: Correct syntax.

ORA-00986 missing or invalid group name(s)

Cause: Probably a syntax error.

Action: Correct syntax.

ORA-00987 missing or invalid username(s)

Cause: No username was specified in a GRANT statement or one of the specified usernames is invalid. Valid usernames must be specified following the keyword TO in a GRANT statement to define a user. A username must begin with a letter, consist only of alphanumeric characters and the special characters $, _, and #, and be less than or equal to 30 characters. If it contains other characters, it must be enclosed in double quotation marks. It may not be a reserved word.

Action: Specify a valid username, or list of usernames, following the keyword TO in the GRANT statement.

ORA-00988 missing or invalid password(s)

Cause: More usernames than passwords were specified in a GRANT statement. A valid password must be specified for each username listed in the GRANT statement.

Action: Enter a valid password for each username.

ORA-00989 too many passwords for usernames given

Cause: More passwords than usernames were specified in a GRANT statement. Only one password may be entered for each username listed in the GRANT statement.

Action: Enter an equal number of usernames and passwords.

ORA-00990 missing or invalid privilege

Cause: No privileges were specified in a GRANT privilege statement, or one of the specified privileges is invalid.

Action: Enter one or more valid privileges such as SELECT, INSERT, DELETE, UPDATE, ALTER, INDEX, REFERENCES, or ALL. More than one privilege may be granted by entering the privileges in a list separated by commas (,) or by specifying the keyword ALL to grant all privileges.

ORA-00991 only MAC privileges may be granted to procedures

Cause: Object privileges or non-MAC system privileges were granted to the procedure.

Action: Only grant MAC privileges using the PROCEDURE clause.

ORA-00992 invalid format for REVOKE command

Cause: An invalid form of the REVOKE command was entered. There are two forms of the REVOKE command. The first form is used to revoke a user's database access privileges. The second form is used to revoke a user's object privileges.

Action: Check the command syntax and retry the statement.

ORA-00993 missing GRANT keyword

Cause: The keyword WITH was specified at the end of a GRANT statement without the keyword GRANT. To grant privileges to a user and the permission to grant those privileges to another user, you must specify the keywords WITH GRANT OPTION at the end of the GRANT statement.

Action: Change the keyword WITH to the keywords WITH GRANT OPTION, then retry the statement.

ORA-00994 missing OPTION keyword

Cause: The keywords WITH GRANT were specified at the end of a GRANT statement without the keyword OPTION.

Action: Change the keywords WITH GRANT to the keywords WITH GRANT OPTION. Then retry the statement.

ORA-00995 missing or invalid synonym identifier

Cause: In a CREATE or DROP SYNONYM statement, the synonym name was either missing or invalid.

Action: Check syntax and spelling. A valid synonym name must be specified immediately following the keyword SYNONYM in both statements. Valid synonym names must begin with a letter, consist of alphanumeric characters and the special characters $, _, and #, and be less than or equal to 30 characters. They may not be reserved words.

ORA-00996 the concatenate operator is ||, not |

Cause: A single bar (|) was interpreted as an attempt to specify concatenation, but the concatenation operator is a double bar (||).

Action: Enter a double bar (||) for concatenation or remove the single bar (|) if concatenation was not intended.

ORA-00997 illegal use of LONG datatype

Cause: A value of datatype LONG was used in a function or in a DISTINCT, WHERE, CONNECT BY, GROUP BY, or ORDER BY clause. A LONG value can only be used in a SELECT clause.

Action: Remove the LONG value from the function or clause.

ORA-00998 must name this expression with a column alias

Cause: An expression or function was used in a CREATE VIEW statement, but no corresponding column name was specified. When expressions or functions are used in a view, all column names for the view must be explicitly specified in the CREATE VIEW statement.

Action: Enter a column name for each column in the view in parentheses after the view name.

ORA-00999 invalid view name

Cause: In a CREATE VIEW statement, the view name was missing or invalid.

Action: Enter a valid view name following CREATE VIEW. Valid view names must begin with a letter, consist of only alphanumeric characters and the special characters $, _, and #, be less than or equal to 30 characters, and may not be reserved words. If the view name contains other characters, it must be enclosed in double quotation marks.

ORA-01000 maximum open cursors exceeded

Cause: A host language program attempted to open too many cursors. The initialization parameter OPEN_CURSORS determines the maximum number of cursors per user.

Action: Modify the program to use fewer cursors. If this error occurs often, shut down Oracle, increase the value of OPEN_CURSORS, and then restart Oracle.

ORA-01001 invalid cursor

Cause: Either a host language program call specified an invalid cursor or the value of the MAXOPENCURSORS option in the precompiler command were too small. All cursors must be opened using the OOPEN call before being referenced in any of the following calls: SQL, DESCRIBE, NAME, DEFINE, BIND, EXEC, FETCH, and CLOSE. The Logon Data Area (LDA) must be defined by using OLON or OLOGON. If the LDA is not defined, this message is issued for the following calls: OPEN, COM, CON, ROL, and LOGOFF.

Action: Check the erroneous call statement. Specify a correct LDA area or open the cursor as required. If there is no problem with the cursor, it may be necessary to increase the MAXOPENCURSORS option value before precompiling.

ORA-01002 fetch out of sequence

Cause: In a host language program, a FETCH call was issued out of sequence. A successful parse-and-execute call must be issued before a fetch. This can occur if an attempt was made to FETCH from an active set after all records have been fetched. This may be caused by fetching from a SELECT FOR UPDATE cursor after a commit. A PL/SQL cursor loop implicitly does fetches and may also cause this error.

Action: Parse and execute a SQL statement before attempting to fetch the data.

ORA-01003 no statement parsed

Cause: A host language program call referenced a cursor with no associated parsed SQL statement. A SQL call (for example, OSQL3) must be used to pass a SQL statement to Oracle and to associate the statement with an open cursor. A cursor must already have an associated SQL statement if referenced in any of the following calls: DESCRIBE, NAME, DEFINE, BIND, EXECUTE, and FETCH.

Action: Do the SQL call, for example, OSQL, to pass the required SQL statement before referencing the cursor.

ORA-01004 default username feature not supported; logon denied

Cause: An attempt was made to use automatic logon on a system not supporting this feature.

Action: Provide the complete username and password to log on to Oracle.

ORA-01005 null password given; logon denied

Cause: An invalid password was given when logging on.

Action: Provide a valid password.

ORA-01006 bind variable does not exist

Cause: A program issued a BIND call for a variable not listed in the associated SQL statement. Only those variables prefixed by either a colon (:) or ampersand (&) in the SQL statement may be referenced in a BIND call, OBIND or OBINDN. This error may also be caused by a mismatch between a Precompiler program and the related library, SQLLIB.

Action: Modify the BIND call to reference one of the substitute variables specified in the associated SQL statement.

ORA-01007 variable not in select list

Cause: A reference was made to a variable not listed in the SELECT clause. In OCI, this can occur if the number passed for the position parameter is less than one or greater than the number of variables in the SELECT clause in any of the following calls: DESCRIBE, NAME, or DEFINE. In SQL*Forms or SQL*Report, specifying more variables in an INTO clause than in the SELECT clause also causes this error.

Action: Determine which of the problems listed caused the problem and take appropriate action.

ORA-01008 not all variables bound

Cause: A SQL statement containing substitution variables was executed without all variables bound. All substitution variables must have a substituted value before the SQL statement is executed.

Action: In OCI, use an OBIND or OBINDN call to substitute the required values.

ORA-01009 missing mandatory parameter

Cause: A host language program call did not pass all required parameters.

Action: Check the syntax for the call and enter all required parameters.

ORA-01010 invalid OCI operation

Cause: One of the following:

• You attempted an invalid OCI operation.
• You are using an Oracle client application linked with release 7.1 (or higher) libraries, the environment variable ORA_ENCRYPT_LOGIN is set to TRUE, and you attempted to connect to a release 7.0 (or lower) Oracle database server.
• You are connected to a release 7.1 (or higher) Oracle database server, theDBLINK_ENCRYPT_LOGIN initialization parameter is set to TRUE, and you attempted to use a database link pointing to a release 7.0 (or lower) Oracle database server.
• You are connected to a release 9.0.2(or higher) Oracle database server and you attempted to use a database link pointing to a release 9.0.1 (or lower) Oracle database server for distributed autonomous transactions.

Action: For the above causes:

• Do not use the invalid OCI operation.
• If you do not wish to use encrypted connect passwords in your distributed database, then set ORA_ENCRYPT_LOGIN to FALSE. If you wish to use encrypted connect passwords, then you must upgrade all Oracle database servers to release 7.1 (or higher).
• If you do not wish to use encrypted database links in your distributed database, then setDBLINK_ENCRYPT_LOGIN to FALSE. If you wish to use encrypted database links, then you must upgrade all Oracle database servers to release 7.1 (or higher).
• Do not attempt distributed autonomous transactions on release 9.0.1 (or lower) Oracle database servers.

ORA-01011 cannot use v7 compatibility mode when talking to v6 server

Cause: An attempt was made to use Oracle7 compatibility mode when accessing Oracle version 6.

Action: Use V6 SQL language type. You may need to use the SET COMPATIBILITY V6 command.

ORA-01012 not logged on

Cause: A host language program issued an Oracle call, other than OLON or OLOGON, without being logged on to Oracle. This can occur when a user process attempts to access the database after the instance it is connected to terminates, forcing the process to disconnect.

Action: Log on to Oracle, by calling OLON or OLOGON, before issuing any Oracle calls. When the instance has been restarted, retry the action.

ORA-01013 user requested cancel of current operation

Cause: The user interrupted an Oracle operation by entering CTRL-C, Control-C, or another canceling operation. This forces the current operation to end. This is an informational message only.

Action: Continue with the next operation.

ORA-01014 ORACLE shutdown in progress

Cause: A user tried to log on to Oracle while an instance shutdown was in progress. Oracle logons are disabled while Oracle is being shut down.

Action: Wait until Oracle is brought back up before attempting to log on.

ORA-01015 logon called recursively

Cause: This is an internal error message not usually issued.

Action: Contact Oracle Support Services.

ORA-01016 This function can be called only after a fetch

Cause: The cursor is in an invalid state.

Action: Ensure the appropriate OCI/UPI function is called after the fetch and before the offending function.

ORA-01017 invalid username/password; logon denied

Cause: An invalid username or password was entered in an attempt to log on to Oracle. The username and password must be the same as was specified in a GRANT CONNECT statement. If the username and password are entered together, the format is: username/password.

Action: Enter a valid username and password combination in the correct format.

ORA-01018 column does not have a LONG datatype

Cause: An attempt was made to fetch data using the LONG fetch option, but the specified column was not LONG.

Action: Re-execute the fetch without the LONG fetch option or create the table with a LONG column.

ORA-01019 unable to allocate memory in the user side

Cause: The user side memory allocator returned an error.

Action: Increase the size of the process heap or switch to the old set of calls.

ORA-01020 unknown context state

Cause: This is an internal error message not usually issued.

Action: Contact Oracle Support Services.

ORA-01021 invalid context size specified

Cause: This is an internal error message not usually issued.

Action: Contact Oracle Support Services.

ORA-01022 database operation not supported in this configuration

Cause: The attempted database operation does not conform to the user programming interface (UPI) for the two communicating Oracle servers.

Action: You may need to upgrade one or more of your Oracle servers or re-link your user side application with new libraries. Report the problem to Oracle Support Services.

ORA-01023 Cursor context not found (Invalid cursor number)

Cause: The cursor number is not a valid open cursor.

Action: Make sure that the cursor is open.

ORA-01024 invalid datatype in OCI call

Cause: An OCI program call specified an invalid datatype. In OCI calls, Oracle datatypes are specified as numbers between 1 and 7.

Action: Check the datatype description and enter the correct number for the datatype.

ORA-01025 UPI parameter out of range

Cause: An integer parameter to a UPI function is out of range.

Action: This usually indicates an error in a tool built on top of the Oracle DBMS. Report the error to Oracle Support Services.

ORA-01026 multiple buffers of size > 4000 in the bind list

Cause: More than one long buffer in the bind list.

Action: Change the buffer size to be less than 4000 for the bind variable bound to a normal column.

ORA-01027 bind variables not allowed for data definition operations

Cause: An attempt was made to use a bind variable in a SQL data definition operation.

Action: Such bind variables are not allowed.

ORA-01028 internal two task error

Cause: Received send long message but do not have the cursor context.

Action: Contact Oracle Support Services.

ORA-01029 internal two task error

Cause: Received a request to send the long again when there is no long

Action: Contact Oracle Support Services.

ORA-01030 SELECT ... INTO variable does not exist

Cause: The SELECT... INTO specified in the bind call does not correspond to a variable in the SQL statement.

Action: If it is not possible to correct the statement, then contact Oracle Support Services.

ORA-01031 insufficient privileges

Cause: An attempt was made to change the current username or password without the appropriate privilege. This error also occurs if attempting to install a database without the necessary operating system privileges.

Action: Ask the database administrator to perform the operation or grant the required privileges.

ORA-01032 no such userid

Cause: This is an internal error message related to Export/Import.

Action: Contact Oracle Support Services.

ORA-01033 ORACLE initialization or shutdown in progress

Cause: An attempt was made to log on while Oracle is being started or shut down.

Action: Wait a few minutes. Then retry the operation.

ORA-01034 ORACLE not available

Cause: Oracle was not started. Possible causes include the following:

• The SGA requires more space than was allocated for it.
• The operating-system variable pointing to the instance is improperly defined.

Action: Refer to accompanying messages for possible causes and correct the problem mentioned in the other messages. If Oracle has been initialized, then on some operating systems, verify that Oracle was linked correctly. See the platform-specific Oracle documentation.

ORA-01035 ORACLE only available to users with RESTRICTED SESSION privilege

Cause: Logins are disallowed because an instance started in restricted mode. Only users with RESTRICTED SESSION system privilege can log on.

Action: Request that Oracle be restarted without the restricted option or obtain the RESTRICTED SESSION system privilege.

ORA-01036 illegal variable name/number

Cause: Unable to find bind context on user side.

Action: Make sure that the variable being bound is in the SQL statement.

ORA-01037 maximum cursor memory exceeded

Cause: An attempt was made to process a complex SQL statement which consumed all available memory of the cursor.

Action: Simplify the complex SQL statement. Alternatively, you can use theNO_EXPAND hint which prevents the cost-based optimizer from consideringOR-expansion for queries having OR conditions or INLISTS in the WHERE clause. Usually, the optimizer considers usingOR expansion and uses this method if it decides the cost is lower than not using it. Refer to theOracle9i Database Performance Tuning Guide and Reference for information about using hints.

ORA-01038 cannot write database file version string with ORACLE versionstring

Cause: An attempt was made to write datafile headers in an old format. The new format cannot be used until after the database has been verified as being compatible with this software version.

Action: Open the database to advance to the new file formats, then repeat the operation. If the operation is required before the database can be opened, then use the previous software release to do the operation.

ORA-01039 insufficient privileges on underlying objects of the view

Cause: An attempt was made to explain plan on other people's view without the necessary privileges on the underlying objects of the view.

Action: Get necessary privileges or do not perform the offending operation.

ORA-01040 invalid character in password; logon denied

Cause: There are multibyte characters in the password or some characters in the password are not in US7ASCII range.

Action: Resubmit the password with valid characters.

ORA-01041 internal error. hostdef extension doesn't exist

Cause: Pointer to HSTDEF extension in HSTDEF is null.

Action: Contact Oracle Support Services.

ORA-01042 detaching a session with open cursors not allowed

Cause: An attempt was made to detach a session which had open cursors.

Action: Close all the cursors before detaching the session.

ORA-01043 user side memory corruption [string], [string], [string], [string]

Cause: The application code corrupted some of the user memory used by Oracle.

Action: Make sure that the application code is not overwriting memory.

ORA-01044 size string of buffer bound to variable exceeds maximumstring

Cause: An attempt was made to bind a buffer whose total size would exceed the maximum size allowed. Total array size for arrays is calculated as:

(element_size)*(number of elements)

Action: Reduce the buffer size.

ORA-01045 user string lacks CREATE SESSION privilege; logon denied

Cause: A connect was attempted to a userid which does not have create session privilege.

Action: Grant the user CREATE SESSION privilege.

ORA-01046 cannot acquire space to extend context area

Cause: Oracle could not extend the current area any further because the operating system would not supply any more space. A system-specific message should appear following this message.

Action: Close some cursors and try again or check operating system quotas to use more virtual memory. See your operating system-specific Oracle documentation.

ORA-01047 The above error occurred in schema=string, package=string, procedure=string

Cause: This message is displayed after a previous message to provide more specific information.

Action: See the cause and action for the previous message.

ORA-01048 Couldn't find the specified procedure in the given context

Cause: The procedure user specified in deferred RPC does not exist.

Action: Check to make sure that the procedure exists and is visible to the replication process.

ORA-01049 Bind by name is not supportted in streamed RPC

Cause: This error occurs when a newer server version requests from an older server version an operation that is not supported.

Action: You may need to upgrade one or more of your Oracle servers or relink your user application with new libraries.

ORA-01050 cannot acquire space to open context area

Cause: Oracle could not open a new context area because the operating system would not supply any more space. A system-specific message should appear following this message.

Action: Close some cursors and try again or check operating system quotas to use more virtual memory. See your operating system-specific Oracle documentation.

ORA-01051 deferred rpc buffer format invalid

Cause: The deferred RPC data in SYS.DEF$_CALL is corrupted.

Action: Contact Oracle Support Services.

ORA-01052 required destination LOG_ARCHIVE_DUPLEX_DEST is not specified

Cause: A valid destination for parameter LOG_ARCHIVE_DUPLEX_DEST was not specified when parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was set to 2.

Action: Either specify a value for parameter LOG_ARCHIVE_DUPLEX_DEST, or reduce the value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST to 1.

ORA-01053 user storage address cannot be read

Cause: A bind variable or other user area could not be read by Oracle.

Action: Check that binds are done correctly on valid user buffers, then retry the operation.

ORA-01054 user storage address cannot be written

Cause: A define, FETCH... INTO or SELECT... INTO, variable or other user area could not be written to by Oracle.

Action: Check that INTO variables and indicators are correctly specified. Then retry the operation.

ORA-01057 invalid or ambiguous block.field reference in user exit

Cause: The reference to a block.field identifier in a user exit is incorrect or ambiguous, probably because it is misspelled or incomplete.

Action: Check syntax and identifier spelling. Then correct the reference.

ORA-01058 internal New Upi interface error

Cause: Attempt to delete non-existent HSTDEF extension.

Action: Contact Oracle Support Services.

ORA-01059 parse expected before a bind or execute

Cause: The client application attempted to bind a variable or execute a cursor opened in a PL/SQL block before the statement was parsed.

Action: Ensure the statement is parsed before a bind or execute.

ORA-01060 array binds or executes not allowed

Cause: The client application attempted to bind an array of cursors or attempted to repeatedly execute against a PL/SQL block with a bind variable of type cursor.

Action: Bind a single cursor or execute the PL/SQL block once.

ORA-01061 cannot start up a V8 server using a V7 client application

Cause: You are using an Oracle client application linked with version 7 (or lower) libraries and you attempted to start up a V8 (or higher) server.

Action: Use a client application linked with V8 (or higher) libraries.

ORA-01062 unable to allocate memory for define buffer

Cause: Exceeded the maximum buffer size for current platform.

Action: Use piecewise fetch with a smaller buffer size.

ORA-01070 Using an old version of Oracle for the server

Cause: An attempt was made to run an older, obsolete Oracle Server.

Action: Upgrade the server.

ORA-01071 cannot perform operation without starting up ORACLE

Cause: An attempt was made to perform an operation before Oracle was started.

Action: Start Oracle. Then retry the operation.

ORA-01072 cannot stop ORACLE; ORACLE not running

Cause: An attempt was made to stop Oracle, but Oracle was not running.

Action: No action required.

ORA-01073 fatal connection error: unrecognized call type

Cause: An illegal internal operation was attempted.

Action: Contact Oracle Support Services.

ORA-01074 cannot shut down ORACLE; inside a login session - log off first

Cause: An attempt was made to shut down Oracle inside a logon session.

Action: Log off before shutting down Oracle.

ORA-01075 you are currently logged on

Cause: An attempt was made to log on while already logged on.

Action: No action required.

ORA-01076 multiple logons per process not yet supported

Cause: Oracle does not support multiple logons per process.

Action: No action required.

ORA-01077 background process initialization failure

Cause: A failure occurred during initialization of the background processes.

Action: Refer to the diagnostic information in the accompanying message stack or in the trace file and take appropriate action.

ORA-01078 failure in processing system parameters

Cause: Failure during processing of initialization parameters during system startup.

Action: Further diagnostic information should be in the error stack.

ORA-01079 ORACLE database was not properly created, operation aborted

Cause: There was an error when the database or control file was created.

Action: Check what error was signaled when the database was first created or when the control file was re-created. Take appropriate actions to re-create the database or a new control file.

ORA-01080 error in shutting down ORACLE

Cause: A failure occurred during system shutdown.

Action: Refer to the diagnostic information in the accompanying message stack and take appropriate action.

ORA-01081 cannot start already-running ORACLE - shut it down first

Cause: An attempt was made to start Oracle while it was already running.

Action: Shut down Oracle first, if you want to restart it.

ORA-01082 'row_locking = always' requires the transaction processing option

Cause: "row_locking = always" is specified in the INIT.ORA file. This feature is not supported by ORACLE without the transaction processing option.

Action: Remove it from INIT.ORA file or set it to "default" or "intent".

ORA-01083 value of parameter "string" is inconsistent with that of other instances

Cause: The value of the given initialization parameter is required to be the same for all instances in the cluster database configuration.

Action: Change the value of the initialization parameter in the initialization parameter file to match that of other cluster database instances.

ORA-01084 invalid argument in OCI call

Cause: The failing OCI call contains an argument with an invalid value.

Action: Use valid argument values. For more information, see theOracle Call Interface Programmer's Guide and the appropriate programming language supplement.

ORA-01085 preceding errors in deferred rpc to "string.string.string"

Cause: Errors were encountered when the named procedure was executed as a deferred remote procedure call.

Action: Correct the cause of the preceding errors.

ORA-01086 savepoint 'string' never established

Cause: An attempt was made to roll back to a savepoint that was never established.

Action: No action is required.

ORA-01087 cannot start up ORACLE - currently logged on

Cause: An attempt was made to start up Oracle by a user who is currently logged on.

Action: Log off. Then issue the STARTUP command.

ORA-01088 cannot shut down ORACLE while active processes exist

Cause: Users are still logged into the instance.

Action: Either wait for all users to logoff or use SHUTDOWN IMMEDIATE.

ORA-01089 immediate shutdown in progress - no operations are permitted

Cause: The SHUTDOWN IMMEDIATE command was used to shut down a running Oracle instance, terminating any active operations.

Action: Wait for the instance to be restarted or contact the database administrator.

ORA-01090 shutdown in progress - connection is not permitted

Cause: The SHUTDOWN command was used to shut down a running Oracle instance, disallowing any connects to Oracle.

Action: Wait for the instance to restart or contact the database administrator.

ORA-01091 failure during startup force

Cause: Unable to destroy the old SGA.

Action: Manually remove the old SGA. See your operating system-specific Oracle documentation for instructions. Then retry the STARTUP command.

ORA-01092 ORACLE instance terminated. Disconnection forced

Cause: The instance connected to was terminated abnormally, probably due to aSHUTDOWN ABORT. The current process was forced to disconnect from the instance.

Action: Examine the alert log for more details. Contact the database administrator to determine when the instance is restarted. Attempt to reconnect after the instance is running again.

ORA-01093 ALTER DATABASE CLOSE only permitted with no sessions connected

Cause: There is at least one more session, other than the current one, logged in to the instance.ALTER DATABASE CLOSE is not permitted when other sessions are active.

Action: Find the other sessions and disconnect them. Then reissue theALTER DATABASE CLOSE statement. Also, issue the SHUTDOWN IMMEDIATE command to force users off the system, or issue theSHUTDOWN ABORT command to shut down the database without waiting for users to be forced off.

ORA-01094 ALTER DATABASE CLOSE in progress. Connections not permitted

Cause: An attempt was made to connect while the database is being closed with theALTER DATABASE CLOSE statement.

Action: Attempt to connect again when the database is open. Contact the database administrator to find out when the database will be open.

ORA-01095 DML statement processed zero rows

Cause: A DML cursor from the OTEX() call processed 0 rows when executed.

Action: Caller can either do a rollback or ignore the message and execute the rest of the cursors in the cursor array.

ORA-01096 program version (string) incompatible with instance (string)

Cause: The program was linked with a different version of the server than the instance to which it is attempting to connect.

Action: Relink the program against the same version of Oracle as the instance or restart (startup force) the database using the program's version of the SERVER.

ORA-01097 cannot shutdown while in a transaction - commit or rollback first

Cause: An attempt was made to shut down the database while a transaction was in progress.

Action: Either commit or rollback the current transaction and then attempt to shut down the database.

ORA-01098 program Interface error during Long Insert

Cause: The application program interface could not insert or update a LONG column because of an internal error when a TTCGETV call fails. For example, a network read error or one of the parameters passed to the call is invalid.

Action: Retry the insert or update.

ORA-01099 cannot mount database in SHARED mode if started in single process mode

Cause: An attempt was made to mount a database in parallel mode with the initialization parameter SINGLE_PROCESS set to TRUE.

Action: Either mount the database in EXCLUSIVE mode or set the initialization parameter SINGLE_PROCESS to FALSE before starting the instance in parallel (shared) mode.

ORA-01100 database already mounted

Cause: An attempt was made to mount a database with the name of a currently mounted database.

Action: No action is required.

ORA-01101 database being created currently mounted by some other instance

Cause: Some other instance has the database of same name currently mounted and you are trying to create it.

Action: Either change the database name or shut down the other instance.

ORA-01102 cannot mount database in EXCLUSIVE mode

Cause: Some other instance has the database mounted exclusive or shared.

Action: Shut down the other instance or mount in a compatible mode.

ORA-01103 database name 'string' in controlfile is not 'string'

Cause: The database name in the control file does not match your database name.

Action: Either find the correct control file or change your database name.

ORA-01104 number of controlfiles (string) does not equalstring

Cause: The number of control files used by this instance disagrees with the number of control files in an existing instance.

Action: Check to make sure that all control files are listed.

ORA-01105 mount is incompatible with mounts by other instances

Cause: An attempt to mount the database discovered that another instance mounted a database by the same name, but the mount is not compatible. Additional errors are reported explaining why.

Action: See accompanying errors.

ORA-01106 database must be closed before dismounting

Cause: An attempt was made to dismount a database before it was closed.

Action: Close the database, then retry the operation.

ORA-01107 database must be mounted for media recovery

Cause: An attempt to perform media recovery was made but the database is not mounted.

Action: Mount the database.

ORA-01108 file string is in backup or media recovery"

Cause: Either media recovery is actively being applied to the file, or it is being backed up while the database is in NOARCHIVELOG mode. It cannot be used for normal database access or crash recovery.

Action: Complete or cancel the media recovery session or backup.

ORA-01109 database not open

Cause: A command was attempted that requires the database to be open.

Action: Open the database and try the command again.

ORA-01110 data file string: 'string'

Cause: This message reports the file name involved with other messages.

Action: See the associated messages for a description of the problem.

ORA-01111 name for data file string is unknown - rename to correct file

Cause: The datafile was missing from a CREATE CONTROLFILE command or BACKUP CONTROLFILE RECOVERY was done with a control file that was saved before the file was created.

Action: Rename the MISSING file to the name of the real file.

ORA-01112 media recovery not started

Cause: An attempt to continue media recovery is being made but media recovery was not started.

Action: No action is required.

ORA-01113 file string needs media recovery

Cause: An attempt was made to open a datafile that is in need of media recovery.

Action: First apply media recovery to the datafile identified in the message, then retry the operation.

ORA-01114 IO error writing block to file string (block #string)

Cause: The device on which the file resides is probably offline. If the file is a temporary file, then it is also possible that the device has run out of space. This could happen because disk space of temporary files is not necessarily allocated at file creation time.

Action: Restore access to the device or remove unnecessary files to free up space.

ORA-01115 IO error reading block from file string (block #string)

Cause: The device on which the file resides is probably off line.

Action: Restore access to the device, then retry the operation.

ORA-01116 error in opening database file string

Cause: Usually the file is not accessible.

Action: Make sure the datafile is in the expected location and can be accessed properly, then retry the operation.

ORA-01117 adding file 'string' with illegal block size:string; limit is string

Cause: An attempt was made to add a datafile with a block size that is greater than the maximum block size allowed.

Action: Retry the operation with a smaller block size.

ORA-01118 cannot add any more database files: limit of string exceeded

Cause: An attempt to add a datafile failed because the limit for such files had already been reached.

Action: If more database space is required, export the database and re-create it with a higher limit for datafiles and perhaps increased file size.

ORA-01119 error in creating database file 'string'

Cause: Insufficient space on device.

Action: Decrease the size of the requested file or allocate a file on another device with more available space. If a file size was not specified in the statement, then specify a file size smaller than the available space on the device.

ORA-01120 cannot remove online database file string

Cause: An attempt was made to drop a datafile when it is online.

Action: Take file offline before dropping.

ORA-01121 cannot rename database file string - file is in use or recovery

Cause: An attempt was made to use ALTER DATABASE RENAME to rename a datafile that is online in an open instance or is being recovered.

Action: Close database in all instances and end all recovery sessions.

ORA-01122 database file string failed verification check

Cause: The information in this file is inconsistent with information from the control file. See accompanying message for reason.

Action: Make certain that the database files and control files are the correct files for this database.

ORA-01123 cannot start online backup; media recovery not enabled

Cause: An attempt to start backup of an online tablespace failed because media recovery is not enabled.

Action: Enable media recovery and retry this operation.

ORA-01124 cannot recover data file string - file is in use or recovery

Cause: An attempt to do media recovery found that the file was not available for recovery. Either it is online and the database is open in some instance, or another process is currently doing media recovery on the file.

Action: Do not do media recovery.

ORA-01125 cannot disable media recovery - file string has online backup set

Cause: An attempt to disable media recovery found that an online backup is still in progress.

Action: End the backup of the offending tablespace and retry this command.

ORA-01126 database must be mounted EXCLUSIVE and not open for this operation

Cause: An operation failed because the database was not mounted in exclusive mode.

Action: Shut down Oracle and mount the database in exclusive mode.

ORA-01127 database name 'string' exceeds size limit ofstring characters

Cause: The specified database name is too long.

Action: Shorten the database name to eight characters or fewer, then retry the operation.

ORA-01128 cannot start online backup - file string is offline

Cause: An attempt to start an online backup found that one of the files is offline.

Action: Bring the offending files online and retry this command or do a cold backup.

ORA-01129 user's default or temporary tablespace does not exist

Cause: The user's default or temporary tablespace was dropped.

Action: Reassign the default or temporary tablespace.

ORA-01130 database file version string incompatible with ORACLE versionstring

Cause: The named datafile was created under an incompatible version of Oracle, or the file is invalid or non-existent.

Action: Shut down and restart the correct version of Oracle or check the references to the datafile and make sure it exists.

ORA-01131 DB_FILES system parameter value string exceeds limit ofstring

Cause: The specified value of the initialization parameter DB_FILES is too large.

Action: Reduce the value of the DB_FILES parameter and retry the operation.

ORA-01132 length of database file name 'string' exceeds limit ofstring characters

Cause: The specified datafile name is too long.

Action: Shorten the file name and retry the operation.

ORA-01133 length of log file name 'string' exceeds limit ofstring characters

Cause: The specified redo log file name is too long.

Action: Shorten the file name and retry the operation.

ORA-01134 database mounted exclusive by another instance

Cause: An attempt to access a database failed because it is mounted in exclusive mode by another instance.

Action: Either shut down the other instance or wait for the other instance to either close the database or mount it in parallel mode, before retrying the operation.

ORA-01135 file string accessed for DML/query is offline

Cause: An attempt was made to access a datafile that is offline.

Action: Bring the datafile back online.

ORA-01136 specified size of file string (string blocks) is less than original size ofstring blocks

Cause: A file size was specified in the AS clause of theALTER DATABASE CREATE DATAFILE statement, and the size was smaller than the size needed.

Action: Create the file with a larger size.

ORA-01137 data file string is still in the middle of going offline

Cause: It was not possible to get the lock for a file that is offline when attempting to bring it online. The most likely cause is that the lock is still held by the instance that is took it offline.

Action: Wait for the other instance to release the lock on the file.

ORA-01138 database must either be open in this instance or not at all

Cause: The requested operation cannot be done when the database is mounted but not open in this instance, and another instance has the database open.

Action: Execute the operation in an open instance, open the database in this instance, or close the database in the other instances.

ORA-01139 RESETLOGS option only valid after an incomplete database recovery

Cause: The RESETLOGS option was given in ALTER DATABASE OPEN, but there has been no incomplete recovery session.

Action: Reissue the ALTER DATABASE OPEN statement without specifying'.

ORA-01140 cannot end online backup - all files are offline

Cause: All the files were found to be offline when attempting to end an online backup.

Action: No action required. Online backup does not need to be ended for this tablespace.

ORA-01141 error renaming data file string - new file 'string' not found

Cause: An attempt to change a datafile's name in the control file failed because no file was found with the new name.

Action: Make sure that the datafile has been properly renamed by the operating system and retry.

ORA-01142 cannot end online backup - none of the files are in backup

Cause: None of the files were found to be in online backup when attempting to end an online backup.

Action: No action required. Online backup does not need to be ended for this tablespace.

ORA-01143 cannot disable media recovery - file string needs media recovery

Cause: An attempt to disable media recovery found a file that needs media recovery, thus media recovery cannot be disabled.

Action: Recover the offending file or drop the tablespace it belongs to and retry this command.

ORA-01144 File size (string blocks) exceeds maximum ofstring blocks

Cause: Specified file size is larger than maximum allowable size value.

Action: Specify a smaller size.

ORA-01145 offline immediate disallowed unless media recovery enabled

Cause: ALTER TABLESPACE ... OFFLINE IMMEDIATE orALTER DATABASE DATAFILE ... OFFLINE is only allowed if the database is inARCHIVELOG mode.

Action: Take the tablespace offline as usual or do a shutdown abort before attempting the required operation. It is worthwhile reconsidering the backup strategy for the database. The attempted operationscan be done if ARCHIVEREDO LOG mode is enabled.

ORA-01146 cannot start online backup - file string is already in backup

Cause: An attempt was made to start an online backup, but an online backup was already started for one of the datafiles.

Action: End the first backup before beginning another.

ORA-01147 SYSTEM tablespace file string is offline

Cause: A file belonging to the SYSTEM tablespace has been marked offline by the database administrator. The database cannot be started until all SYSTEM tablespace files are online and can be opened.

Action: Bring the file online.

ORA-01148 can not mount database PARALLEL without a lock manager installed

Cause: An attempt was made to mount the database PARALLEL without the existence of a Lock Manager.

Action: Mount the database in EXCLUSIVE mode.

ORA-01149 cannot shutdown - file string has online backup set

Cause: An attempt to shut down normally found that an online backup is still in progress.

Action: End the backup of the offending tablespace and retry this command.

ORA-01150 cannot prevent writes - file string has online backup set

Cause: Tablespace cannot be taken offline or made read-only when online backup is running. Ending the backup entails writing the file header, which this operation, were it permitted, would prevent.

Action: End the online backup and then take the tablespace offline or make it read-only.

ORA-01151 use media recovery to recover block, restore backup if needed

Cause: Crash recovery or instance recovery could not apply a change to a block because it was not the next change. This can happen if the block was corrupted and then repaired during recovery. This message is usually accompanied by ORA-01172.

Action: There is additional information for ORA-01172. Perform a RECOVER datafile for the file containing the block. If this does not resolve the problem, restore the file from a backup and recover it again.

ORA-01152 file string was not restored from a sufficiently old backup

Cause: An incomplete recovery session was started, but an insufficient number of redo logs were applied to make the database consistent. This file is still in the future of the last redo log applied. The most likely cause of this message is forgetting to restore the file from backup before doing incomplete recovery.

Action: Apply additional redo log files until the database is consistent or restore the datafiles from an older backup and repeat recovery.

ORA-01153 an incompatible media recovery is active

Cause: Attempted to start an incompatible media recovery or open resetlogs during media recovery or RMAN backup . Media recovery sessions are incompatible if they attempt to recover the same data file. Incomplete media recovery or open resetlogs is incompatible with any media recovery. Backup or restore by RMAN is incompatible with open resetlogs.

Action: Complete or cancel the other media recovery session or RMAN backup.

ORA-01154 database busy. Open, close, mount, and dismount not allowed now

Cause: Some operation is in progress that expects the state of the instance to remain open or mounted.

Action: Wait for the operation to complete and try again. If attempting a normal database shutdown, trySHUTDOWN ABORT.

ORA-01155 the database is being opened, closed, mounted or dismounted

Cause: The attempted operation will not succeed while the instance is in one of the states mentioned in the message.

Action: Wait for the open, close, mount, or dismount to complete and try again. If attempting a normal database shutdown, trySHUTDOWN ABORT.

ORA-01156 recovery in progress may need access to files

Cause: Either media or instance recovery is in progress. The recovery may need access to the files that the attempted operation tried to use.

Action: Wait for the recovery to complete and try again.

ORA-01157 cannot identify/lock data file string - see DBWR trace file

Cause: The background process was either unable to find one of the data files or failed to lock it because the file was already in use. The database will prohibit access to this file but other files will be unaffected. However, the first instance to open the database will need to access all online data files. The accompanying error from the operating system describes why the file could not be identified.

Action: At the operating system level, make the file available to the database. Then either open the database or do an ALTER SYSTEM CHECK DATAFILES.

ORA-01158 database string already mounted

Cause: Another instance has a database by this name mounted.

Action: Find which instance is still running. Perhaps you have not lost the control files after all.

ORA-01159 file is not from same database as previous files - wrong database id

Cause: Not all of the files specified in CREATE CONTROLFILE are from the same database. The database ID of this file does not match that from the first file specified.

Action: Check the list of files provided to the CREATE.

ORA-01160 file is not a string

Cause: The named file in the DATAFILE or LOGFILE section of the CREATE CONTROLFILE command does not appear to be as stated.

Action: Check the mentioned file.

ORA-01161 database name string in file header does not match given name ofstring

Cause: The database name given at the command line does not match the database name found in the file header.

Action: Chance are good that the database name specified at the command line is incorrect. Resolve the discrepancy, and resubmit the command. If you are attempting to change the database name, be sure to use the SET DATABASE option.

ORA-01162 block size string in file header does not match configured block sizes

Cause: CREATE CONTROLFILE discovered that the block size for this file is incompatible with any of the configured cache blocksizes in the initialization parameter file.

Action: Configure the appropriate cache for this block size using one of the (DB_2K_cache_size, DB_4K_cache_size, DB_8K_cache_size, DB_16K_cache_size, DB_32K_cache_size) parameters.

ORA-01163 SIZE clause indicates string (blocks), but should match headerstring

Cause: The size specified in bytes in the SIZE clause of the CREATE CONTROLFILE statement does not equate to the number of blocks recorded in the header.

Action: Specify the correct file name and size (in bytes).

ORA-01164 MAXLOGFILES may not exceed string

Cause: MAXLOGFILES specified on the command line too large.

Action: Resubmit the command with a smaller value for MAXLOGFILES.

ORA-01165 MAXDATAFILES may not exceed string

Cause: MAXDATAFILES specified on the command line too large.

Action: Resubmit the command with a smaller value for MAXDATAFILES.

ORA-01166 file number string is larger than string (string)

Cause: File mentioned in CREATE CONTROLFILE has a file number which is larger than that specified for MAXDATAFILES or MAXLOGFILES.

Action: Increase the maximum specified on the command line.

ORA-01167 two files are the same file/group number or the same file

Cause: There is an overlap of file numbers in the files specified on the command line or the same file is specified twice. If they are not the exact same file then one is likely to be a backup of the other. If they are two members of the same log they must be specified together in a group file specification. This message will also appear if the same control file appears more than once in the CONTROL_FILES parameter in the INIT.ORA file. If this happens, check for additional error messages.

Action: Confirm that the file mentioned is not a repeat of a file already mentioned in the command. If they are different files then omit the earlier backup. If they are members of the same log, insure they are in the same group file specification. If this message appears because of a duplicate control file, check the CONTROL_FILES parameter in the INIT.ORA file and see if a file is specified more than once. If all files names appear to be unique, check to make sure that the actual control files themselves are unique. For example, in UNIX check for a symbolic or a hard link to another control file in the list.

ORA-01168 physical block size string does not match sizestring of other members

Cause: The file is located on a device with a different physical block size than the other members in the group.

Action: Use a physical device with matching block size.

ORA-01169 DATAFILE number 1 not found. Must be present

Cause: Datafile number 1 was not specified in a CREATE CONTROLFILE command.

Action: Locate datafile number 1 and resubmit the CREATE CONTROLFILE command.

ORA-01170 file not found 'string'

Cause: A file specified in the CREATE CONTROLFILE statement was not found. All datafiles and all redo log files, if NORESETLOGS was used, must be accessible by the process that issues the CREATE CONTROLFILE statement.

Action: Check the statement for a typing mistake in the file name and check for the existence of all files. Then issue the statement again after correcting the file names.

ORA-01171 datafile string going offline due to error advancing checkpoint

Cause: The checkpoint in the file header could not be advanced. See accompanying errors for the reason. The datafile will be taken offline the same as for a write error of a data block.

Action: See accompanying errors for details. Restore access to the file, do media recovery, and bring it back online.

ORA-01172 recovery of thread string stuck at blockstring of file string

Cause: Crash recovery or instance recovery could not apply a change to a block because it was not the next change. This can happen if the block was corrupted and then repaired during recovery.

Action: Do a RECOVER DATAFILE for the file containing the block. If this does not resolve the problem, then restore the file from a backup and recover it.

ORA-01173 data dictionary indicates missing data file from system tablespace

Cause: One of the following:

• The database is recovered to a point in time in the future of the control file.
• A datafile from the system tablespace is omitted from the issued CREATE CONTROLFILE statement.

Action: One of the following:

• Recover the database from a more recent control file.
• Re-create the control file, ensuring all datafiles are included for the system tablespace in the command line.

ORA-01174 DB_FILES is string buts needs to be string to be compatible

Cause: The maximum number of database files supported by this instance is not the same as for the other instances. All instances must be able to open all the files any instance can open.

Action: Change the value of the DB_FILES parameter to be compatible.

ORA-01175 data dictionary has more than the string files allowed by the instance

Cause: The data dictionary is found to have more files than that which can be supported by this instance.

Action: Shut down the instance and restart with a larger value for DB_FILES.

ORA-01176 data dictionary has more than the string files allowed by the controlfie

Cause: After a CREATE CONTROLFILE, the data dictionary was found to have more datafiles than that supported by the control file.

Action: Re-create the control file with a larger value for MAXDATAFILES.

ORA-01177 data file does not match dictionary - probably old incarnation

Cause: When comparing the control file with the data dictionary after a CREATE CONTROLFILE or OPEN RESETLOGS, it was noted that this datafile was inconsistent with the dictionary. Most likely the file is a backup of a file that was dropped from the database, and the same file number was reused for a new file. It may also be that an incomplete recovery stopped at a time when this file number was used for another datafile.

Action: Do a CREATE CONTROLFILE with the correct file or none at all.

ORA-01178 file string created before last CREATE CONTROLFILE, cannot recreate

Cause: An attempt was made to use ALTER DATABASE CREATE DATAFILE to re-create a datafile that existed at the lastCREATE CONTROL file command. The information needed to re-create the file was lost with the control file that existed when the file was added to the database.

Action: Find a backup of the file, and recover it. Do incomplete recovery to time before file was originally created.

ORA-01179 file string does not exist

Cause: During datafile recovery, a file was listed that was not part of the database.

Action: Recheck the file name. Remember to use single quotation marks at the SQL*DBA command line. Remember also that the file name is translated in the operating environment of SQL*DBA.

ORA-01180 can not create datafile 1

Cause: An attempt was made to create datafile 1 using ALTER DATABASE CREATE DATAFILE.

Action: Recover file from a backup or re-create the database.

ORA-01181 file string created before last RESETLOGS, cannot recreate

Cause: An attempt was made to use ALTER DATABASE CREATE DATAFILE to re-create a datafile that existed at the lastRESETLOGS database open.

Action: Find a backup of the file, and recover it. Do incomplete recovery to time before file was originally created.

ORA-01182 cannot create database file string - file is in use or recovery

Cause: An attempt was made to use ALTER DATABASE CREATE DATAFILE to re-create a datafile that is online in an open instance or is being recovered.

Action: Close database in all instances and end all recovery sessions.

ORA-01183 cannot mount database in SHARED mode

Cause: Some other instance has the database mounted exclusive.

Action: Shut down the other instance and then mount shared.

ORA-01184 logfile group string already exists

Cause: An ALTER DATABASE ADD LOGFILE statement specified a log number for the new log which is already in use.

Action: Specify a different log file number, or let the database choose an unused value.

ORA-01185 logfile group number string is invalid

Cause: An ALTER DATABASE ADD LOGFILE statement specified a log number for the new log which is too large.

Action: Specify a correct log file number.

ORA-01186 file string failed verification tests

Cause: The datafile did not pass the checks to insure it is part of the database. See the accompanying error messages for the reason the verification failed.

Action: Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES.

ORA-01187 cannot read from file string because it failed verification tests

Cause: The datafile did not pass the checks to insure it is part of the database. Reads are not allowed until it is verified.

Action: Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES.

ORA-01188 Block size string in header does not match physical block sizestring

Cause: A log file member given to CREATE CONTROLFILE is on a physical device that has a different block size than the device originally used to create the log.

Action: Move the file to a device with the correct block size or use the RESETLOGS option to CREATE CONTROLFILE.

ORA-01189 file is from a different RESETLOGS than previous files

Cause: In a CREATE CONTROLFILE command, either this file or all previous files were backups from before the last RESETLOGS. This may also occur if this is a file that is offline and has been offline since before the last RESETLOGS.

Action: If the file was taken offline normal before the last RESETLOGS, and is still offline, omit it from the CREATE CONTROLFILE command. Rename and online the file after the database is open. Otherwise find the version of the mentioned file consistent with the rest of the datafiles and resubmit the command.

ORA-01190 controlfile or data file string is from before the last RESETLOGS

Cause: An attempt was made to use a datafile when the log reset information in the file does not match the control file. Either the datafile or the control file is a backup that was made before the most recentALTER DATABASE OPEN RESETLOGS.

Action: Restore file from a more recent backup.

ORA-01191 file string is already offline - cannot do a normal offline

Cause: When attempting to do a normal tablespace offline, it was discovered that one of the files in the tablespace was already offline.

Action: Either bring the datafile online first, or use another tablespace offline option.

ORA-01192 must have at least one enabled thread

Cause: At least two redo log files from at least one thread must be specified in the CREATE CONTROLFILE command line.

Action: Find the missing redo log files and retry the command with the newly found redo log files included in the command line.

ORA-01193 file string is not the same file seen at start of recovery

Cause: A different copy of the file was accessed the last time media recovery looked at the file header. A backup of the file was restored or the meaning of the file name changed during recovery.

Action: Ensure the correct file is available, and then retry recovery.

ORA-01194 file string needs more recovery to be consistent

Cause: An incomplete recovery session was started, but an insufficient number of logs were applied to make the file consistent. The reported file was not closed cleanly when it was last opened by the database. It must be recovered to a time when it was not being updated. The most likely cause of this error is forgetting to restore the file from a backup before doing incomplete recovery.

Action: Either apply more logs until the file is consistent or restore the file from an older backup and repeat recovery.

ORA-01195 online backup of file string needs more recovery to be consistent

Cause: An incomplete recovery session was started, but an insufficient number of logs were applied to make the file consistent. The reported file is an online backup which must be recovered to the time the backup ended.

Action: Either apply more logs until the file is consistent or restore the database files from an older backup and repeat recovery.

ORA-01196 file string is inconsistent due to a failed media recovery session

Cause: The file was being recovered but the recovery did not terminate normally. This left the file in an inconsistent state. No more recovery was successfully completed on this file.

Action: Either apply more logs until the file is consistent or restore the backup again and repeat recovery.

ORA-01197 thread string only contains one log

Cause: During CREATE CONTROLFILE all threads represented in the logs must be represented by at least two logs. A "last log" and a second log. The named thread does not contain two such logs.

Action: Either find more logs from the named thread. Or use the RESETLOGS option to CREATE CONTROLFILE.

ORA-01198 must specify size for log file if RESETLOGS

Cause: File sizes must be given for all log files if doing a CREATE CONTROLFILE with the RESETLOGS option.

Action: Resubmit the command with the appropriate log file size.

ORA-01199 file string is not in online backup mode

Cause: An attempt was made to end an online backup for a file that is not in online backup.

Action: Do not enter command since it is not needed.

ORA-01200 actual file size of string is smaller than correct size ofstring blocks

Cause: The size of the file as returned by the operating system is smaller than the size of the file as indicated in the file header and the control file. Somehow the file has been truncated. Maybe it is the result of a half completed copy.

Action: Restore a good copy of the datafile and do recovery as needed.

ORA-01201 file string header failed to write correctly

Cause: An I/O error was reported for the file header. The error was trapped and a second attempt will be made.

Action: The file probably will require recovery. Further error messages will indicate what is needed.

ORA-01202 wrong incarnation of this file - wrong creation time

Cause: The creation time in the file header is not the same as the creation time in the control file. This is probably a copy of a file that was dropped.

Action: Restore a current copy of the datafile and do recovery as needed.

ORA-01203 wrong incarnation of this file - wrong creation SCN

Cause: The creation SCN in the file header is not the same as the creation SCN in the control file. This is probably a copy of a file that was dropped.

Action: Restore a current copy of the datafile and do recovery as needed.

ORA-01204 file number is string rather than string - wrong file

Cause: The file number in the file header is not correct. This is probably a restored backup of the wrong file, but from the same database.

Action: Restore a copy of the correct datafile and do recovery as needed.

ORA-01205 not a data file - type number in header is string

Cause: The file type in the header is not correct for a datafile. This is probably a log file or control file. If the type is not a small non-zero positive number then the header is corrupted.

Action: Restore a copy of the correct datafile and do recovery as needed.

ORA-01206 file is not part of this database - wrong database id

Cause: The database ID in the file header does not match the database ID in the control file. The file may be from a different database, or it may not be a database file at all. If the database was rebuilt, this may be a file from before the rebuild. Note that if you see this error when the file is supposed to be plugged in from another database via the Transportable Tablespace feature, it means the database ID in the file header does not match the one expected.

Action: Restore a copy of the correct datafile and do recovery as needed.

ORA-01207 file is more recent than controlfile - old controlfile

Cause: The control file change sequence number in the datafile is greater than the number in the control file. This implies that the wrong control file is being used. Note that repeatedly causing this error can make it stop happening without correcting the real problem. Every attempt to open the database will advance the control file change sequence number until it is great enough.

Action: Use the current control file or do BACKUP CONTROLFILE RECOVERY to make the control file current. Be sure to follow all restrictions on doing a BACKUP CONTROLFILE RECOVERY.

ORA-01208 data file is an old version - not accessing current version

Cause: The checkpoint in the file header is less recent than in the control file. If opening a database that is already open by another instance, or if another instance just brought this file online, the file accessed by this instance is probably a different version. Otherwise, a backup of the file probably was restored while the file was in use.

Action: Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES.

ORA-01209 data file is from before the last RESETLOGS

Cause: The reset log data in the file header does not match the control file. If the database is closed or the file is offline, the backup is old because it was taken before the lastALTER DATABASE OPEN RESETLOGS statement. If opening a database that is open already by another instance, or if another instance just brought this file online, the file accessed by this instance is probably a different version. Otherwise, a backup of the file probably was restored while the file was in use.

Action: Make the correct file available to the database. Then, either open the database or execute ALTER SYSTEM CHECK DATAFILES.

ORA-01210 data file header is media corrupt

Cause: The file header block is internally inconsistent. The beginning of the block has a header with a checksum and other data for insuring the consistency of the block. It is possible that the last disk write did not operate correctly. The most likely problem is that this is not a datafile for any database.

Action: Have operating system make correct file available to database. If the trace file dump indicates that only the checksum is wrong, restore from a backup and do media recovery.

ORA-01211 Oracle7 data file is not from migration to Oracle8

Cause: The file is not a copy of the file LAST used under Oracle7. This datafile is either a backup taken from before the migration, or the database was opened by Oracle7 after the migration utility was run. When converting a database from Oracle7 to Oracle8, the migration program MUST be the LAST utility to access the database under Oracle7. Only the datafiles that were current when the migration was done may be accessed by Oracle8.

Action: Have operating system make correct datafile available to database, or repeat the Oracle7 to Oracle8 migration. Make sure that database is NOT opened after migration utility is run.

ORA-01212 MAXLOGMEMBERS may not exceed string

Cause: MAXLOGMEMBERS specified on the command line too large.

Action: Resubmit the command with a smaller value for MAXLOGMEMBERS.

ORA-01213 MAXINSTANCES may not exceed string

Cause: MAXINSTANCES specified on the command line too large.

Action: Resubmit the command with a smaller value for MAXINSTANCES.

ORA-01214 MAXLOGHISTORY may not exceed string

Cause: MAXLOGHISTORY specified on the command line too large.

Action: Resubmit the command with a smaller value for MAXLOGHISTORY.

ORA-01215 enabled thread string is missing after CREATE CONTROLFILE

Cause: A CREATE CONTROLFILE statement was given which did not list all the enabled threads for the database.

Action: Reissue the CREATE CONTROLFILE statement, including all enabled threads.

ORA-01216 thread string is expected to be disabled after CREATE CONTROLFILE

Cause: A thread that was given during CREATE CONTROLFILE is enabled, but the datafiles indicate that it should be disabled. This is probably because the logs supplied to the CREATE CONTROLFILE are old (from before the disabling of the thread).

Action: This thread is not required to run the database. The CREATE CONTROLFILE statement can be reissued without the problem thread, and, if desired, the thread can be re-created after the database is open.

ORA-01217 logfile member belongs to a different logfile group

Cause: A member of a multiple-member log file group specified in a CREATE CONTROLFILE is not part of the same group as previous members.

Action: Group together the correct members for the CREATE CONTROLFILE command.

ORA-01218 logfile member is not from the same point-in-time

Cause: A member of a multiple-member log file group is from a different point in time. One of the members specified may be an older (backup) copy of the log.

Action: Find the correct version of the log, or leave it out of the CREATE CONTROLFILE command.

ORA-01219 database not open: queries allowed on fixed tables/views only

Cause: A query was issued against an object not recognized as a fixed table or fixed view before the database has been opened.

Action: Re-phrase the query to include only fixed objects, or open the database.

ORA-01220 file based sort illegal before database is open

Cause: A query issued against a fixed table or view required a temporary segment for sorting before the database was open. Only in-memory sorts are supported before the database is open.

Action: Re-phrase the query to avoid a large sort, increase the values of the SORT_AREA_SIZE and/or SORT_AREA_RETAINED_SIZE initialization parameters to enable the sort to be done in memory.

ORA-01221 data file string is not the same file to a background process

Cause: When the database writer opens the datafile, it is accessing a different physical file than the foreground doing the recovery. The timestamp set in the file header by the foreground was not found by the background. It may be that the background process could not read the file at all.

Action: Look in the DBWR trace file for the error it received when attempting to read the file header. Reconfigure the operating system as needed to have the file name successfully access the same file when opened by a background process.

ORA-01222 MAXINSTANCES of string requires MAXLOGFILES be at leaststring, not string

Cause: An attempt was made to create a database or control file that does not have room for at least two logs per thread of redo. A thread of redo must have two online logs in order to be enabled. It does not make sense to allow more redo threads than can be supported by the logs.

Action: Either reduce the MAXINSTANCES argument or increase the value of MAXLOGFILES.

ORA-01223 RESETLOGS must be specified to set a new database name

Cause: The SET database name option was specified to CREATE CONTROLFILE, but RESETLOGS was not specified. The database name can only be changed when opening the database with RESETLOGS.

Action: Either add the RESETLOGS option or drop the SET option to CREATE CONTROLFILE.

ORA-01224 group number in header string does not match GROUPstring

Cause: Group number specified at CREATE CONTROLFILE does not match the group number stored in the header. Most likely the specification is wrong.

Action: Omit the GROUP option or give the correct one.

ORA-01225 thread number string is greater than MAXINSTANCESstring

Cause: The log is for a thread greater than the MAXINSTANCES argument.

Action: Increase the value for MAXINSTANCES and resubmit the command.

ORA-01226 file header of log member is inconsistent with other members

Cause: The log file member in the accompanying error is for the same group as the previous members, but other fields in the header are different. Either a file header is corrupted, or some file is a member of a deleted log.

Action: Find the correct log member or omit this member from the command.

ORA-01227 log string is inconsistent with other logs

Cause: The log file in the accompanying error is inconsistent with the contents of other logs given in the CREATE CONTROLFILE command. Either a file header is corrupted, or some file is an old copy rather than the current version. The problem may not be with the log listed since all that can be detected is that there is an inconsistency. All log files listed in the command must be the current versions of the online logs.

Action: Find the correct online logs or use the RESETLOGS option.

ORA-01228 SET DATABASE option required to install seed database

Cause: The SET DATABASE option was not included in the CREATE CONTROLFILE command when installing a seed database. The database does not have a database ID because it is intended to be installed at multiple sites, and each site needs to be a different database with its own database id. Both the SET DATABASE and RESETLOGS options must be specified to create the control file for this database.

Action: Resubmit command with the SET DATABASE and RESETLOGS options.

ORA-01229 data file string is inconsistent with logs

Cause: The datafile in the accompanying error is inconsistent with the contents of the logs given in the CREATE CONTROLFILE command. The most likely cause is that one or more of the online logs was missing from the command. It is also possible that one or more of the logs is an old copy rather than the current version. All online log files must be listed in the command and must be the current versions of the online logs.

Action: Find the correct online logs or use the RESETLOGS option.

ORA-01230 cannot make read only - file string is offline

Cause: An attempt to make a tablespace read only found that one of its files is offline.

Action: Bring the file online and retry this command.

ORA-01231 cannot make read write - file string is offline

Cause: An attempt to make a tablespace read write found that one of its files is offline.

Action: Bring the file online and retry this command.

ORA-01232 cannot start online backup - file string is read only

Cause: An attempt to start an online backup found that one of the files is marked read only. Read-only files do not need to be set into online backup mode.

Action: Make the backup without the begin backup command.

ORA-01233 file string is read only - cannot recover using backup controlfile

Cause: An attempt to do media recovery using a backup control file found that one of the files is marked read only. Read-only files do not normally need to be recovered, but recovery with a backup control file must recover all online files.

Action: If the file really is read only, take it offline before the recovery, and bring the read-only tablespace online after the database is open. If the file does need recovery use a control file from the time the file was read-write. If the correct control file is not available, use CREATE CONTROLFILE to make one.

ORA-01234 cannot end backup of file string - file is in use or recovery

Cause: An attempt was made to end an online backup of file when the file is busy. Some operation such as recovery or rename may be active, or there may still be some instance that has the database open with this file online.

Action: If there is an instance with the database open then the backup can be ended there by using the ALTER TABLESPACE command. Otherwise wait for the completion of the other operation.

ORA-01235 END BACKUP failed for string file(s) and succeeded forstring

Cause: One or more of the files in an end backup command failed. Some other files given in the same command may have succeeded.

Action: See the accompanying error messages for the reason the backups could not be ended. Any files not listed in the error messages were successful.

ORA-01236 Error string occurred during initialization of file header access

Cause: The indicated error occurred while doing initialization processing of file headers.

Action: The error indicated should be corrected. An attempt is made to recover from this error by using a slower access algorithm.

ORA-01237 cannot extend datafile string

Cause: An operating system error occurred during the resize.

Action: Fix the cause of the operating system error and retry the command.

ORA-01238 cannot shrink datafile string

Cause: An operating system error occurred during the resize.

Action: The error is ignored, operation continues normally.

ORA-01239 database must be in ARCHIVELOG mode to use external cache

Cause: An online file uses an external cache, but the database is in NOARCHIVELOG mode. Since an external cache may require media recovery this cannot be allowed.

Action: Change database to be in ARCHIVELOG mode or do not use an external cache.

ORA-01240 too many data files to add in one command

Cause: The command specifies adding more datafiles than can be done in one command. It is necessary to fit all the file names into one log entry, but that would make the entry too large.

Action: If this is a CREATE TABLESPACE command, create with fewer files then add the other files later. If this is an ADD DATAFILE command, break it up into multiple commands.

ORA-01241 an external cache has died

Cause: The external cache may have been restarted.

Action: Take the file mentioned in the error stack offline, perform media recovery, bring the file online, and retry the attempted operation. You may also restart all instances to make sure they access all datafiles through consistent external caches.

ORA-01242 data file suffered media failure: database in NOARCHIVELOG mode

Cause: The database is in NOARCHIVELOG mode and a database file was detected as inaccessible due to media failure.

Action: Restore accessibility to the file mentioned in the error stack and restart the instance.

ORA-01243 system tablespace file suffered media failure

Cause: A system tablespace file was detected as inaccessible due to media failure.

Action: Restore accessibility to the file mentioned in the error stack and restart the instance.

ORA-01244 unnamed datafile(s) added to controlfile by media recovery

Cause: Media recovery with a backup control file or a control file that was rebuilt, encountered the creation of a datafile that was not in the control file. An entry has been added to the control file for the new datafiles, but with the file name UNNAMEDnnnn, where nnnn is the file number. Attached errors describe the file names that were originally used to create the files.

Action: Rename the files to valid file names and resume recovery. If necessary theALTER DATABASE CREATE DATAFILE statement may be used to create a file suitable for recovery and do the rename. If the file is not going to be recovered then take it offline with the FOR DROP option.

ORA-01245 offline file string will be lost if RESETLOGS is done

Cause: An attempt was made to do an OPEN RESETLOGS with a file that will be lost because it is offline. The file was not taken offline with the FOR DROP option.

Action: Either bring the file online and recover it, or take it offline with the FOR DROP option.

ORA-01246 recovering files through TSPITR of tablespace string

Cause: The files named in the accompanying errors are backups that were made before a tablespace point in time recovery of this tablespace. They cannot be recovered to a time after the point in time recovery.

Action: Restore more recent backups and recover them.

ORA-01247 database recovery through TSPITR of tablespace string

Cause: Recovery of the whole database encountered redo indicating there was a point in time recovery of the tablespace. The new version of the files in the tablespace should be included in the recovery, but that was not done.

Action: If the tablespace should not be recovered, take its file offline for drop. If it should be recovered, then restore or rename as needed and restart the recovery.

ORA-01248 file string was created in the future of incomplete recovery

Cause: An attempt was made to do a RESETLOGS open with a file entry in the control file that was originally created after the UNTIL time of the incomplete recovery. Allowing such an entry may hide the version of the file that is needed at this time. The file number may be in use for a different file which would be lost if the RESETLOGS was allowed.

Action: If more recovery is desired then apply redo until the creation time of the file is reached. If the file is not wanted and the same file number is not in use at the stop time of the recovery, then the file can be taken offline with the FOR DROP option. Otherwise a different control file is needed to allow the RESETLOGS. Another backup can be restored and recovered, or a control file can be created via CREATE CONTROLFILE.

ORA-01249 archiving not allowed in a clone database

Cause: An attempt was made to archive an online redo log or enable archiving for a clone database.

Action: Do not attempt to archive from a clone. The archive log destination could easily be the same as the primary database destroying its archived logs. If archiving is needed, then re-create the database not as a clone.

ORA-01250 Error string occurred during termination of file header access

Cause: The indicated error occurred while terminating the processing of file headers. The error was other than a write error.

Action: The indicated error should be corrected.

ORA-01251 Unknown File Header Version read for file number string

Cause: Read of the file header returned a record but its version cannot be identified. Either the header has been corrupted, or the file is not a valid database file.

Action: Have the operating system make the correct file available to the database, or recover the file.

ORA-01252 cannot prevent writes - file string in recovery manager backup

Cause: An attempt to make a tablespace read only or offline normal found that a recovery manager proxy backup is in progress. If the file is made offline or read only, then the file header cannot be updated when the backup is complete.

Action: Wait for the Recovery Manager backup to complete and retry this command.

ORA-01253 cannot start online backup - file string in recovery manager backup

Cause: The specified file is being backed up by Recovery Manager.

Action: Wait for the Recovery Manager proxy backup to complete before starting another backup.

ORA-01254 cannot end online backup - file string in recovery manager backup

Cause: The specified file is being backed up by Recovery Manager.

Action: Wait for the Recovery Manager proxy backup to complete. Recovery Manager backup mode cannot be initiated or terminated manually.

ORA-01255 cannot shutdown - file string in recovery manager backup

Cause: An attempt to shut down normally found that a Recovery Manager backup is still in progress.

Action: Wait for the Recovery Manager proxy backup to complete and retry this command.

ORA-01256 error in locking database file string

Cause: The file is in use by another database instance.

Action: Determine which database instance legitimately owns the file.

ORA-01257 cannot reuse database file string, unknown file size

Cause: The size of the raw partion cannot be determined.

Action: Add the datafile/logfile by specifying the size parameter.

ORA-01258 unable to delete temporary file string

Cause: A DROP TABLESPACE INCLUDING CONTENTS AND DATAFILES or ALTER DATABASE TEMPFILE DROP INCLUDING DATAFILES operation was not able to delete a temporary file in the database.

Action: Subsequent errors describe the operating system error that prevented the file deletion. Fix the problem, if possible, and manually purge the file.

ORA-01259 unable to delete datafile string

Cause: A DROP TABLESPACE INCLUDING CONTENTS AND DATAFILES operation was not able to delete a datafile in the tablespace.

Action: Subsequent errors describe the operating system error that prevented the file deletion. Fix the problem, if possible, and manually purge the file.

ORA-01260 may not issue ALTER DATABASE END BACKUP when database is open

Cause: ALTER DATABASE END BACKUP was issued while the database was open.

Action: Either use ALTER DATABASE DATAFILE <filename> END BACKUP to end backup for specific files, or ALTER TABLESPACE <name> END BACKUP if backup is complete for all files in a tablespace.

ORA-01261 Parameter string destination string cannot be translated

Cause: The value for the specified parameter contained a destination string that could not be translated.

Action: Use a valid destination string in the specified parameter.

ORA-01262 Stat failed on a file destination directory

Cause: Unable to get information about an Oracle Managed Files destination directory.

Action: Check the permissions on the directory or use a different directory name.

ORA-01263 Name given for file destination directory is invalid

Cause: The name given for an Oracle Managed Files destination does not correspond to a directory.

Action: Use a different name.

ORA-01264 Unable to create string file name

Cause: Unable to create an Oracle Managed Files name for a datafile, logfile or control file.

Action: Check previous error messages for the reason Oracle was unable to create the file name. Take corrective action, if possible, and retry the command.

ORA-01265 Unable to delete file string

Cause: An error prevented the file from being deleted.

Action: Subsequent errors describe the operating system error that prevented the file deletion. Fix the problem, if possible, and manually purge the file.

ORA-01266 Unable to create unique file name

Cause: Unable to create a unique file name for an Oracle Managed Files datafile, logfile, or control file. Oracle tried several names but each file name was already in use in the default destination directory for the file type.

Action: Retry the operation. If that fails, it may be necessary to change the default destination directory for the file type and then retry.

ORA-01267 Failure getting date/time

Cause: Could not get date/time when trying to create unique file name.

Action: Internal error - contact Oracle Support Services.

ORA-01268 invalid TEMPFILE clause for alter of permanent TABLESPACE

Cause: A TEMPFILE clause was specified for an ALTER TABLESPACE for a permanent tablespace.

Action: Retry with a DATAFILE clause.

ORA-01269 Destination parameter string is too long

Cause: The value for DB_CREATE_FILE_DEST or DB_CREATE_ONLINE_LOG_DEST_n parameter is too long.

Action: Replace the destination value for the specified parameter with a shorter character string.

ORA-01270 string operation is not allowed if STANDBY_PRESERVES_NAMES is true

Cause: An operation that renames or adds/drops a file was attempted at a standby database and STANDBY_PRESERVES_NAMES is true.

Action: Set STANDBY_PRESERVES_NAMES to false if the operation must be performed.

ORA-01271 Unable to create new file name for file string

Cause: During standby database recovery an error occurred when trying to create a new file name for the indicated file.

Action: Use the ALTER DATABASE CREATE DATAFILE command with a new unique name and then resume the standby database recovery.

ORA-01272 REUSE only allowed when a file name is provided

Cause: The REUSE parameter was specified in a command without a file name.

Action: Either supply a file name or remove the REUSE parameter.

ORA-01273 STANDBY_FILE_MANAGEMENT = AUTO needs COMPATIBLE = string or higher

Cause: The COMPATIBLE initialization parameter was not set to the correct value for settingSTANDBY_FILE_MANAGEMENT to AUTO.

Action: Restart the instance with COMPATIBLE set to the correct release.

ORA-01274 cannot add datafile 'string' - file could not be created

Cause: Automated standby file management was enabled but an added file could not automatically be created on the standby. The error from the creation attempt is displayed in another message. The controlfile file entry for the file will be 'UNNAMEDnnnnn'.

Action: Temporarily set STANDBY_FILE_MANAGEMENT toMANUAL and use the ALTER DATABASE CREATE DATAFILE statement to create the file. Then setSTANDBY_FILE_MANAGEMENT to AUTO and restart standby recovery.

ORA-01275 Operation string is not allowed if standby file management is automatic.

Cause: An operation that renames, adds, or drops a file was attempted at a standby database andSTANDBY_FILE_MANAGEMENT was set to AUTO.

Action: Set STANDBY_FILE_MANAGEMENT to MANUAL if the operation must be performed.

ORA-01276 Cannot add file string. File has an Oracle Managed Files file name.

Cause: An attempt was made to add to the database a datafile, log file, or control file with an Oracle Managed Files file name.

Action: Retry the operation with a new file name.

ORA-01277 file 'string' already exists

Cause: An ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS 'filename' statement specified a file name which is already in use.

Action: Either specify a different file name or add the REUSE parameter to the statement to overwrite the existing file.

ORA-01278 error creating file 'string'

Cause: An operating system error occurred while attempting to create a trace file specified in theALTER DATABASE BACKUP CONTROLFILE TO TRACE AS 'filename' statement.

Action: Check the error stack for more detailed information.

ORA-01279 DB_FILES too large

Cause: DB_FILES has been set too high to be supported by the system.

Action: Decrease the value of DB_FILES.

ORA-01280 Fatal LogMiner Error.

Cause: On of the following:

• One or more input parameters in the DBMS_LOGMNR.START_LOGMNR() procedure may be invalid.
• The start or the end SCN may not be available in the log files selected.
• The dictionary file specified may be from a different database than the one that generated the log files.
• LogMiner may have encountered an internal error from which it cannot recover.

Action: Check to see whether the input parameters are valid. The V$LOGMNR_LOGS view can be queried to see the SCN ranges that are valid for the set of log files specified, and the DB_ID of the database that generated the log files.

ORA-01281 SCN range specified in dbms_logmnr.start_logmnr() is invalid

Cause: StartSCN may be greater than EndSCN, or the SCN specified may be invalid.

Action: Specify a valid SCN range.

ORA-01282 date range specified in dbms_logmnr.start_logmnr() is invalid

Cause: The specified Date value is invalid for the log file.

Action: Specify a valid date range.

ORA-01283 Options specified is invalid

Cause: The specified Options is invalid for the procedure.

Action: Specify valid Options.

ORA-01284 file string cannot be opened

Cause: The specified file cannot be opened.

Action: Check to make sure the file or directory exists and is accessible.

ORA-01285 error reading file string

Cause: The file or directory may not exist or is inaccessible.

Action: Specify valid file or directory. Make sure that file and directory are accessible.

ORA-01286 cannot add file string due to DB_ID mismatch

Cause: The log file is produced by a different database than other log files already added to the list.

Action: Specify a log file produced by the same database.

ORA-01287 file string is from a different database incarnation

Cause: The logfile was produced by a different incarnation of the database.

Action: Add a logfile that is produced by the same incarnation.

ORA-01288 file string is from a different database incarnation

Cause: The logfile is produced by a different incarnation of the database.

Action: Add a logfile that is produced by the same incarnation.

ORA-01289 cannot add duplicate logfile string

Cause: The log file specified has already been added to the list of log files.

Action: Specify a different log file.

ORA-01290 cannot remove unlisted logfile string

Cause: The user attempted to remove a log file that is not present in the list.

Action: Specify a valid logfile.

ORA-01291 missing logfile

Cause: Not all logfiles corresponding to the data or scn range specified have been added to the list.

Action: Check the v$logmnr_logs view to determine the missing scn range, and add the relevant logfiles.

ORA-01292 no log file has been specified for the current LogMiner session

Cause: No log file has been specified for the LogMiner session.

Action: Specify at least one log file.

ORA-01293 time or SCN range not fully contained in the listed logfiles

Cause: The input date/SCN range is not fully contained within the log files specified for the session.

Action: Select out of V$LOGMNR_LOGS view to check the date or SCN range covered by the log files specified for the LogMiner session, and reissue the procedure with appropriate date or SCN range.

ORA-01294 error occurred while processing information in dictionary file string, possible corruption

Cause: The dictionary file is corrupt.

Action: Get a new dictionary file.

ORA-01295 DB_ID mismatch between dictionary string and logfiles

Cause: The dictionary file is produced by a database that is different from that produced the log files.

Action: Specify a compatible dictionary file.

ORA-01296 character set mismatch between dictionary string and logfiles

Cause: The character set of the database that produced the dictionary file is different from the character set of the database that produced the log files.

Action: Specify a dictionary file with the same character set.

ORA-01297 redo version mismatch between dictionary string and logfiles

Cause: The redo version of the database generating the dictionary is different from the one generating the logfiles.

ORA-01298 dictionary string and the earliest logfile are not SCN-compatible

Cause: The dictionary materialized view was taken at a SCN that does not correspond to the creation SCN of the earliest logfile.

Action: Get a correct dictionary materialized view.

ORA-01299 dictionary string corresponds to a different database incarnation

Cause: The dictionary file was extracted from a different incarnation of the database.

Action: Specify a dictionary file extracted from the correct database incarnation.

ORA-01300 enabled thread bit vector mismatch between dictionary string and the earliest logfile

ORA-01301 dbms_logmnr.USE_COLMAP can only be used with a valid dictionary

Cause: DBMS_LOGMNR.USE_COLMAP can only be used with a valid dictionary.

Action: Specify the dictionary file in DBMS_LOGMNR.START_LOGMNR().

ORA-01302 syntax error in logmnr.opt file

Cause: A syntax error was detected in the logmnr.opt file.

Action: Use correct syntax.

ORA-01303 schema string, specified in logmnr.opt file, does not exist

Cause: The schema specified does not exist.

Action: Specify a correct schema or a compatible dictionary file.

ORA-01304 table string, schema string, specified in logmnr.opt file, does not exist

Cause: The table specified in the logmnr.opt file does not exist in the dictionary provided to LogMiner.

Action: Make sure that the table specified is valid.

ORA-01305 column string, specified in logmnr.opt file, does not exist in tablestring, schema string

Cause: The column specified in the logmnr.opt file does not exist for the table definition in the dictionary provided for LogMiner.

Action: Make sure that the column specified is valid.

ORA-01306 dbms_logmnr.start_logmnr() must be invoked before selecting from v$logmnr_contents

Cause: A select was issued from V$LOGMNR_CONTENTS without first invoking the DBMS_LOGMNR.START_LOGMNR() procedure.

Action: Invoke the DBMS_LOGMNR.START_LOGMNR() procedure before issuing a select from the V$LOGMNR_CONTENTS view.

ORA-01307 no LogMiner session is currently active

Cause: A select was issued from V$LOGMNR_CONTENTS without first invoking the DBMS_LOGMNR.START_LOGMNR() procedure. Otherwise, DBMS_LOGMNR.END_LOGMNR() was called without a prior call to DBMS_LOGMNR.START_LOGMNR() or DBMS_LOGMNR.ADD_LOGFILE()

Action: Invoke the DBMS_LOGMNR.START_LOGMNR() procedure before issuing a select from the V$LOGMNR_CONTENTS view.

ORA-01308 initialization parameter utl_file_dir is not set

Cause: UTL_FILE_DIR is not set in the initialization parameter file.

Action: Set UTL_FILE_DIR to the appropriate directory.

ORA-01309 invalid session

Cause: The specified Logminer session ID or session handle is invalid.

Action: Use a valid Logminer session ID or session handle.

ORA-01310 requested return type not supported by the lcr_mine function

Cause: The return type requested by the user is not supported by LCR_MINE.

Action: Pick a return type supported by the LCR_MINE function.

ORA-01311 Illegal invocation of the mine_value function

Cause: An attempt was made to use the MINE_VALUE function on a column other than redo_value or undo_value columns of SYS.V$LOGMNR_CONTENTS fixed table/view.

Action: Rewrite the SQL statement with a legal invocation of MINE_VALUE.

ORA-01312 Specified table/column does not exist

Cause: The table/column specified in the LCR_MINE call does not exist at the the specified SCN. The table/column definition has to exist at the start SCN specified for lcr_mine to be able to identify the table/column correctly.

Action: Create a LogMiner session at a start SCN at which the table definition is available.

ORA-01313 LogMiner dictionary column type different from specified type

Cause: The return type specified for the column in the LCR_MINE call is different from the actual type of the column.

Action: Rewrite the LCR_MINE invocation with the right return type.

ORA-01314 Name of the column to be mined should be a string literal

Cause: The fully qualified name of the column to be mined by the LogMiner functions should be string literal.

Action: If the fully qualified name of the column to be mined is a.b.c.d, enclose the column name in quotes as in 'a.b.c.d'.

ORA-01315 Log file has been added or removed during select

Cause: A redo log file has been added or removed while selecting on the v$logmnr_logs fixed view.

Action: Re-issue the SQL select statement on the v$logmnr_logs view.

ORA-01316 Already attached to a Logminer session

Cause: A Logminer attach session was issued while already attached to a Logminer session.

Action: Detach from the current Logminer session and attach to the requested session.

ORA-01317 Not attached to a Logminer session

Cause: A command or procedure was issued which requires an attached Logminer session.

Action: Attach to a Logminer session before issuing the command or procedure.

ORA-01318 Logminer session not started

Cause: Logminer activate session was called before prepare session.

ORA-01319 Invalid Logminer session attribute

Cause: A session attribute was supplied which is invalid.

Action: Re-issue with a valid session attribute.

ORA-01320 Invalid Logminer dictionary attribute

Cause: A Logminer dictionary attribute was supplied which is invalid.

Action: Re-issue with a valid dictionary attribute.

ORA-01321 SCN range not fully contained in the listed logfiles

Cause: The input date/SCN range is not fully contained within the logfiles specified for the session.

Action: select out of v$logmnr_logs view to check the date or SCN range covered by the logfiles specified for the LogMiner session , and reissue the procedure with appropriate date or SCN range.

ORA-01322 No such table

Cause: An non-existent table was supplied to Logminer include_src_tbl() or exclude_src_table().

Action: Re-issue with a valid table name.

ORA-01323 Invalid state

Cause: A Logminer routine was called from the wrong state.

ORA-01324 cannot add file due to DB_ID mismatch

Cause: The logfile was produced by a different database than other logfiles already added to the list.

Action: Specify a logfile produced by the same database.

ORA-01325 archive log mode must be enabled to build into the logstream

Cause: The database does not have archivelog mode enabled.

Action: Ensure that initialization parameters enabling archivelog mode are set. For example:

log_archive_start=truelog_archive_dest="ORACLE_HOME/dbs"log_archive_format="archstring.log"

Mount the database and issue commands to enable archivelog mode.

startup pfile=initsid.ora mountALTER DATABASE ARCHIVELOGALTER DATABASE OPEN

ORA-01326 compatibility of 9.0.0 or greater required to build into the logstream

Cause: The COMPATIBLE initialization parameter is set to some value less than 9.0.0.

Action: Ensure that the COMPATIBLE initialization parameter is set to 9.0.0 or higher. For example:

COMPATIBLE = 9.0.0.0.0

ORA-01327 failed to exclusively lock system dictionary as required by build

Cause: Other users are performing DDL operations.

ORA-01328 only one build operation may occur at one time

Cause: Another process is simultaneously attempting to run build().

Action: Wait until the other process completes.

ORA-01329 unable to truncate required build table

Cause: The table may be missing or locked by another user.

Action: This error should not occur. If it does occur and there is reason to believe that required tables are missing, then as a last resort the package dbmslmd.sql may be reinstalled. Doing so will delete all existing Logminer Dictionary data.

ORA-01332 internal Logminer Dictionary error

Cause: Unexpected error condition.

Action: Check the trace file.

ORA-01333 failed to establish Logminer Dictionary

Cause: No previously established Logminer Dictionary is available and a complete gather of a source system data dictionary was not found in the logstream. build() may not have been run to force the gathering of a source system data dictionary, or add_log_file() may not have been called to add all log files which contain the complete gathered system data dictionary.

Action: If build() was not employed prior to this mining session, the Logminer Ad Hoc user may elect to employ an alternate dictionary such as the current system catalog or a previously built flat file dictionary. Other Logminer clients must run build() prior to mining. If build() has been run, ensure that all logfiles which comprise the gathered system dictionary have been added. The following query, run on the system which build() was run, can be helpful in identifying the required files.

select DICTIONARY_BEGIN, DICTIONARY_END, name from v$archived_log;

Minimally a set of files starting with one which has DICTIONARY_BEGIN = 'YES' and all subsequent log files through one which has DICTIONARY_END = \qYESmustbeadded.'

ORA-01336 specified dictionary file cannot be opened

Cause: The dictionary file or directory does not exist or is inaccessible.

Action: Make sure that the dictionary file and directory exist and are accessible.

ORA-01337 log file has a different compatibility version

Cause: The logfile has a different compatibility version than the rest of the logfiles in the session.

Action: Make sure that all logfiles in the session have the same compatibility version.

ORA-01338 Other process is attached to LogMiner session

Cause: Can not do this when other process is attached to LogMiner session.

ORA-01339 logfile is too old

Cause: An attempt was made to add an already processed logfile.

ORA-01340 NLS error

Cause: Could not load NLS package.

ORA-01341 LogMiner out-of-memory

Cause: The logfiles to be analyzed in the current LogMiner session require more system resources than what is currently available.

Action: Reduce the number of logfiles to be analyzed for a given LogMiner session and try again.

ORA-01342 LogMiner can not resume session due to inability of staging checkpointed data

Cause: Logminer can not resume session because there is not enough SGA memory available to read in checkpointed data. Logminer periodically checkpoints data to enable faster crash recovery.

Action: Specify a bigger max_sga for the given LogMiner session and try again.

ORA-01344 LogMiner coordinator already attached

Cause: A coordinator process is already attached to the specified logminer context.

Action: Detach from the active coordinator session and retry the attach.

ORA-01345 Supplemental log data must be enabled to build into the logstream

Cause: Supplemental log data must be enabled on this database instance.

Action: Enable supplemental log data.

ORA-01346 Dependent LogMiner sessions relying on supplementally logged data exist

Cause: LogMiner sessions exist on this database instance which rely on the existence of supplemental log data.

Action: Destroy all LogMiner sessions on this instance which are mining log files from this same instance. Then reissue the command.

ORA-01347 Supplemental log data no longer found

Cause: The source database instance producing log files for this LogMiner session was altered to no longer log supplemental data.

Action: Destroy this Logminer session. Re-enable supplemental log data on the source system and create a new LogMiner session.

ORA-01350 must specify a tablespace name

Cause: Invocation failed to specify either a dictionary tablespace or a spill tablespace.

Action: Reformat invocation of DBMS_LOGMNR_D.SET_TABLESPACE to include the name of one or more tablespaces.

• NEW_TABLESPACE - A string naming an existing tablespace.

  Supply only this parameter to recreate all Logminer tables to employ this tablespace.

• DICTIONARY_TABLESPACE - A string naming an existing tablespace.

  Supply this parameter when it is desired to place Logminer Dictionary data in a tablespace different from that where Logminer spill data is to be written. This parameter overrides thenew_tablespace parameter with respect to Logminer Dictionary tables.

• SPILL_TABLESPACE - a string naming an existing tablespace.

  Supply this parameter when it is desired to place Logminer spill data in a tablespace different from that where Logminer Dictionary data is to be written. This parameter overrides thenew_tablespace parameter with respect to Logminer spill tables.

ORA-01351 tablespace given for Logminer dictionary does not exist

Cause: The tablespace name given as either the NEW_TABLESPACE or theDICTIONARY_TABLESPACE parameter to DBMS_LOGMNR_D.SET_TABLESPACE does not exist.

Action: Check the spelling of the tablespace name. If the spelling is correct, then verify that the named tablespace has already been created.DBMS_LOGMNR_D.SET_TABLESPACE will not create a tablespace.

ORA-01352 tablespace given for Logminer spill does not exist

Cause: The tablespace name given as either the NEW_TABLESPACE or theSPILL_TABLESPACE parameter to DBMS_LOGMNR_D.SET_TABLESPACE does not exist.

Action: Check the spelling of the tablespace name. If the spelling is correct, then verify that the named tablespace has already been created.DBMS_LOGMNR_D.SET_TABLESPACE will not create a tablespace.

ORA-01353 existing Logminer session

Cause: An attempt was made to execute DBMS_LOGMNR_D.SET_TABLESPACE while Logminer sessions existed. In generalDBMS_LOGMNR_D.SET_TABLESPACE should be run before any Logminer activity has begun. If this error occurs, then this procedure has not been followed.

Action: First cause all Logminer sessions to be destroyed. A Logminer session can exist as a result of executingDBMS_LOGMNR.START_LOGMNR or as the result of running a product such as Logical Standby or Streams which uses Logminer. Next, executeDBMS_LOGMNR_D.SET_TABLESPACE.

ORA-01370 Specified restart SCN is too old

Cause: The specified restart scn is too old and Logminer could not find a proper checkpoint.

Action: Specify a bigger restart SCN to try again.

ORA-01371 Complete LogMiner dictionary not found

Cause: One or more log files containing the LogMiner dictionary was not found.

Action: Add into LogMiner all log files containing the dictionary.

ORA-01372 Insufficient processes for specified LogMiner operation

Cause: The number of processes requested by the caller can not be allocated.

Action: Increase the number of parallel servers allocated to the instance.

ORA-01373 insufficient memory for staging persistent LogMiner session

Cause: The maximum number of concurrent persistent LogMiner sessions allowed is limited by theLOGMNR_MAX_PERSISTENT_SESSIONS parameter. Not enough memory has been set aside at instance startup to allocate the new LogMiner session.

Action: Increase LOGMNR_MAX_PERSISTENT_SESSIONS and restart the instance.

ORA-01374 LOG_PARALLELISM greater than 1 not supported in this release

Cause: LogMiner does not mine redo records generated with LOG_PARALLELISM set to a value greater than 1.

ORA-01400 cannot insert NULL into (string)

Cause: An attempt was made to insert a NULL into the column "USER"."TABLE"."COLUMN".

For example, if you enter:

connect scott/tiger create table a (a1 number not null); insert into a values (null); 

Oracle returns:

ORA-01400 cannot insert NULL into ("SCOTT"."A"."A1") :  which means you cannot insert NULL into "SCOTT"."A"."A1".

Action: Retry the operation with a value other than NULL.

ORA-01401 inserted value too large for column

Cause: The value entered is larger than the maximum width defined for the column.

Action: Enter a value smaller than the column width or use the MODIFY option with ALTER TABLE to expand the column width.

ORA-01402 view WITH CHECK OPTION where-clause violation

Cause: An INSERT or UPDATE statement was attempted on a view created with the CHECK OPTION. This would have resulted in the creation of a row that would not satisfy the view's WHERE clause.

Action: Examine the view's WHERE clause in the dictionary table VIEWS. If the current view does not have the CHECK OPTION, then its FROM clause must reference a second view that is defined using the CHECK OPTION. The second view's WHERE clause must also be satisfied by any INSERT or UPDATE statements. To insert the row, it may be necessary to insert it directly into the underlying table, rather than through the view.

ORA-01403 no data found

Cause: In a host language program, all records have been fetched. The return code from the fetch was +4, indicating that all records have been returned from the SQL query.

Action: Terminate processing for the SELECT statement.

ORA-01404 ALTER COLUMN will make an index too large

Cause: Increasing the length of a column would cause the combined length of the columns specified in a previous CREATE INDEX statement to exceed the maximum index length (255). The total index length is computed as the sum of the width of all indexed columns plus the number of indexed columns. Date fields are calculated as a length of 7, character fields are calculated at their defined width, and numeric fields are length 22.

Action: The only way to alter the column is to drop the affected index. The index cannot be re-created if to do so would exceed the maximum index width.

ORA-01405 fetched column value is NULL

Cause: The INTO clause of a FETCH operation contained a NULL value, and no indicator was used. The column buffer in the program remained unchanged, and the cursor return code was +2. This is an error unless you are running Oracle with DBMS=6, emulating version 6, in which case it is only a warning.

Action: You may do any of the following:

• Use the NVL function to convert the retrieved NULL to another value, such as zero or blank. This is the simplest solution.
• Use an indicator to record the presence of the NULL. You probably should use this option when you want a specific action to be taken when a NULL arises.
• Revise the cursor definition so that no columns possibly containing NULL values are retrieved.

ORA-01406 fetched column value was truncated

Cause: In a host language program, a FETCH operation was forced to truncate a character string. The program buffer area for this column was not large enough to contain the entire string. The cursor return code from the fetch was +3.

Action: Increase the column buffer area to hold the largest column value or perform other appropriate processing.

ORA-01407 cannot update (string) to NULL

Cause: An attempt was made to update a table column "USER"."TABLE"."COLUMN" with a NULL value.

For example, if you enter:

connect scott/tiger update table a (a1 number not null); insert into a values (null); 

Oracle returns:

ORA-01407 cannot update ("SCOTT"."A"."A1") to NULL

which means you cannot update the column "SCOTT"."A"."A1" to NULL.

Action: Retry the operation with a value other than NULL.

ORA-01408 such column list already indexed

Cause: A CREATE INDEX statement specified a column that is already indexed. A single column may be indexed only once. Additional indexes may be created on the column if it is used as a portion of a concatenated index, that is, if the index consists of multiple columns.

Action: Do not attempt to re-index the column, as it is unnecessary. To create a concatenated key, specify one or more additional columns in the CREATE INDEX statement.

ORA-01409 NOSORT option may not be used; rows are not in ascending order

Cause: Creation of index with NOSORT option when rows were not ascending. The NOSORT option may only be used for indexes on groups of rows that already are in ascending order.

For non-unique indexes the ROWID is considered part of the index key. This means that two rows that appear to be stored in ascending order may not be. If you create an index NOSORT, and two of the rows in the table have the same index values, but get split across two extents, the data block address of the first block in the second extent can be less than the data block address of the last block in the first extent. If these addresses are not in ascending order, the ROWIDs are not either. Since these ROWIDs are considered part of the index key, the index key is not in ascending order, and the create index NOSORT fails.

Action: Create the index without the NOSORT option or ensure that the table is stored in one extent.

ORA-01410 invalid ROWID

Cause: A ROWID was entered incorrectly. ROWIDs must be entered as formatted hexadecimal strings using only numbers and the characters A through F. A typical ROWID format is '000001F8.0001.0006'.

Action: Check the format, then enter the ROWID using the correct format. ROWID format: block ID, row in block, file ID.

ORA-01411 cannot store the length of column in the indicator

Cause: An attempt was made to fetch a column of size more than 64K and could not store the length of the column in the given indicator of size 2 bytes.

Action: Use the new bind type with call backs to fetch the long column.

ORA-01412 zero length not allowed for this datatype

Cause: The length for type 97 is 0.

Action: Specify the correct length.

ORA-01413 illegal value in packed decimal number buffer

Cause: The user buffer bound by the user as packed decimal number contained an illegal value.

Action: Use a legal value.

ORA-01414 invalid array length when trying to bind array

Cause: An attempt was made to bind an array without either a current array length pointer or a zero maximum array length.

Action: Specify a valid length.

ORA-01415 too many distinct aggregate functions

Cause: The query contains more distinct aggregates than can be processed. The current limit is 255.

Action: Reduce the number of distinct aggregate functions in the query.

ORA-01416 two tables cannot be outer-joined to each other

Cause: Two tables in a join operation specified an outer join with respect to each other. If an outer join is specified on one of the tables in a join condition, it may not be specified on the other table.

Action: Remove the outer join specification (+) from one of the tables, then retry the operation.

ORA-01417 a table may be outer joined to at most one other table

Cause: a.b (+) = b.b and a.c (+) = c.c is not allowed.

Action: Check that this is really what you want, then join b and c first in a view.

ORA-01418 specified index does not exist

Cause: An ALTER INDEX, DROP INDEX, or VALIDATE INDEX statement specified the name of an index that does not exist. Only existing indexes can be altered, dropped, or validated. Existing indexes may be listed by querying the data dictionary.

Action: Specify the name of an existing index in the ALTER INDEX, DROP INDEX, or VALIDATE INDEX statement.

ORA-01419 datdts: illegal format code

Cause: An attempt was made to use an incorrect format.

Action: Inspect the format, correct it if necessary, then retry the operation.

ORA-01420 datstd: illegal format code

Cause: An attempt was made to use an invalid format.

Action: Inspect the format, correct it if necessary, then retry the operation.

ORA-01421 datrnd/dattrn: illegal precision specifier

Cause: An attempt was made to use an invalid precision specifier.

Action: Inspect the precision specifier, correct it if necessary, then retry the operation.

ORA-01422 exact fetch returns more than requested number of rows

Cause: The number specified in exact fetch is less than the rows returned.

Action: Rewrite the query or change number of rows requested.

ORA-01423 error encountered while checking for extra rows in exact fetch

Cause: An error was encountered during the execution of an exact fetch. This message will be followed by more descriptive messages.

Action: See the accompanying messages and take appropriate action.

ORA-01424 missing or illegal character following the escape character

Cause: The character following the escape character in LIKE pattern is missing or not one of the escape character, '%', or '_'.

Action: Remove the escape character or specify the missing character.

ORA-01425 escape character must be character string of length 1

Cause: Given escape character for LIKE is not a character string of length 1.

Action: Change it to a character string of length 1.

ORA-01426 numeric overflow

Cause: Evaluation of an value expression causes an overflow/underflow.

Action: Reduce the operands.

ORA-01427 single-row subquery returns more than one row

Cause: The outer query must use one of the keywords ANY, ALL, IN, or NOT IN to specify values to compare because the subquery returned more than one row.

Action: Use ANY, ALL, IN, or NOT IN to specify which values to compare or reword the query so only one row is retrieved.

ORA-01428 argument 'string' is out of range

Cause: An illegal value for a mathematical function argument was specified. For example

SELECT SQRT(-1) "Square Root" FROM DUAL; 

Action: See the Oracle9i SQL Reference for valid input and ranges of the mathematical functions.

ORA-01429 Index-Organized Table: no data segment to store overflow row-pieces

Cause: No overflow segment defined.

Action: Add overflow segment.

ORA-01430 column being added already exists in table

Cause: An ALTER TABLE ADD statement specified the name of a column that is already in the table. All column names must be unique within a table.

Action: Specify a unique name for the new column, then re-execute the statement.

ORA-01431 internal inconsistency in GRANT command

Cause: An internal error occurred while attempting to execute a GRANT statement.

Action: Contact Oracle Support Services.

ORA-01432 public synonym to be dropped does not exist

Cause: The synonym specified in DROP PUBLIC SYNONYM is not a valid public synonym. It may be a private synonym.

Action: Correct the synonym name or use DROP SYNONYM if the synonym is not public.

ORA-01433 synonym to be created is already defined

Cause: A CREATE SYNONYM statement specified a synonym name that is the same as an existing synonym, table, view, or cluster. Synonyms may not have the same name as any other synonym, table, view, or cluster available to the user creating the synonym.

Action: Specify a unique name for the synonym, then re-execute the statement.

ORA-01434 private synonym to be dropped does not exist

Cause: A DROP SYNONYM statement specified a synonym that does not exist. Existing synonym names may be listed by querying the data dictionary.

Action: Specify the name of an existing synonym in the DROP SYNONYM statement.

ORA-01435 user does not exist

Cause: This message is caused by any reference to a non-existent user. For example, it occurs if a SELECT, GRANT, or REVOKE statement specifies a username that does not exist. Only a GRANT CONNECT statement may specify a new username. All other GRANT and REVOKE statements must specify existing usernames. If specified in a SELECT statement, usernames must already exist.

Action: Specify only existing usernames in the SELECT, GRANT, or REVOKE statement or ask the database administrator to define the new username.

ORA-01436 CONNECT BY loop in user data

Cause: The condition specified in a CONNECT BY clause caused a loop in the query, where the next record to be selected is a descendent of itself. When this happens, there can be no end to the query.

Action: Check the CONNECT BY clause and remove the circular reference.

ORA-01437 cannot have join with CONNECT BY

Cause: A join operation was specified with a CONNECT BY clause. If a CONNECT BY clause is used in a SELECT statement for a tree-structured query, only one table may be referenced in the query.

Action: Remove either the CONNECT BY clause or the join operation from the SQL statement.

ORA-01438 value larger than specified precision allows for this column

Cause: When inserting or updating records, a numeric value was entered that exceeded the precision defined for the column.

Action: Enter a value that complies with the numeric column's precision, or use the MODIFY option with the ALTER TABLE command to expand the precision.

ORA-01439 column to be modified must be empty to change datatype

Cause: An ALTER TABLE MODIFY statement attempted to change the datatype of a column containing data. A column whose datatype is to be altered must contain only NULL values.

Action: To alter the datatype, first set all values in the column to NULL.

ORA-01440 column to be modified must be empty to decrease precision or scale

Cause: An ALTER TABLE MODIFY statement attempted to decrease the scale or precision of a numeric column containing data. In order to decrease either of these values, the column must contain only NULL values. An attempt to increase the scale without also increasing the precision will also cause this message.

Action: Set all values in the column to NULL before decreasing the numeric precision or scale. If attempting to increase the scale, increase the precision in accordance with the scale or set all values in the column to NULL first.

ORA-01441 cannot decrease column length because some value is too big

Cause: An ALTER TABLE MODIFY statement attempted to decrease the size of a character field containing data. A column whose maximum size is to be decreased must contain only NULL values.

Action: Set all values in column to NULL before decreasing the maximum size.

ORA-01442 column to be modified to NOT NULL is already NOT NULL

Cause: An ALTER TABLE MODIFY statement attempted to change a column specification unnecessarily, from NOT NULL to NOT NULL.

Action: No action required.

ORA-01443 internal inconsistency; illegal datatype in resultant view column

Cause: An internal error occurred in referencing a view.

Action: Contact Oracle Support Services.

ORA-01444 internal inconsistency; internal datatype maps to invalid external type

Cause: This is an internal error message not normally issued.

Action: Contact Oracle Support Services.

ORA-01445 cannot select ROWID from a join view without a key-preserved table

Cause: A SELECT statement attempted to select ROWIDs from a view derived from a join operation. Because the rows selected in the view do not correspond to underlying physical records, no ROWIDs can be returned.

Action: Remove ROWID from the view selection clause, then re-execute the statement.

ORA-01446 cannot select ROWID from view with DISTINCT, GROUP BY, etc.

Cause: A SELECT statement attempted to select ROWIDs from a view containing columns derived from functions or expressions. Because the rows selected in the view do not correspond to underlying physical records, no ROWIDs can be returned.

Action: Remove ROWID from the view selection clause, then re-execute the statement.

ORA-01447 ALTER TABLE does not operate on clustered columns

Cause: An ALTER TABLE MODIFY statement specified a column used to cluster the table. Clustered columns may not be altered.

Action: To alter the column, first re-create the table in non-clustered form. The column's size can be increased at the same time.

ORA-01448 index must be dropped before changing to desired type

Cause: An ALTER TABLE MODIFY statement attempted to change an indexed character column to a LONG column. Columns with the datatype LONG may not be indexed, so the index must be dropped before the modification.

Action: Drop all indexes referencing the column before changing its datatype to LONG.

ORA-01449 column contains NULL values; cannot alter to NOT NULL

Cause: An ALTER TABLE MODIFY statement attempted to change the definition of a column containing NULL values to NOT NULL. The column may not currently contain any NULL values if it is to be altered to NOT NULL.

Action: Set all NULL values in the column to values other than NULL before ALTERING the column to NOT NULL.

ORA-01450 maximum key length (string) exceeded

Cause: The combined length of all the columns specified in a CREATE INDEX statement exceeded the maximum index length. The maximum index length varies by operating system. The total index length is computed as the sum of the width of all indexed columns plus the number of indexed columns. Date fields have a length of 7, character fields have their defined length, and numeric fields have a length of 22. Numeric length = (precision/2) + 1. If negative, add +1.

Action: Select columns to be indexed so the total index length does not exceed the maximum index length for the operating system. See also your operating system-specific Oracle documentation.

ORA-01451 column to be modified to NULL cannot be modified to NULL

Cause: The column may already allow NULL values, the NOT NULL constraint is part of a primary key or check constraint, or an ALTER TABLE MODIFY statement attempted to change a column specification unnecessarily, from NULL to NULL.

Action: If a primary key or check constraint is enforcing the NOT NULL constraint, then drop that constraint.

ORA-01452 cannot CREATE UNIQUE INDEX; duplicate keys found

Cause: A CREATE UNIQUE INDEX statement specified one or more columns that currently contain duplicate values. All values in the indexed columns must be unique by row to create a UNIQUE INDEX.

Action: If the entries need not be unique, remove the keyword UNIQUE from the CREATE INDEX statement, then re-execute the statement. If the entries must be unique, as in a primary key, then remove duplicate values before creating the UNIQUE index.

ORA-01453 SET TRANSACTION must be first statement of transaction

Cause: A transaction was not processed properly because the SET TRANSACTION statement was not the first statement.

Action: Commit or roll back the current transaction before using the statement SET TRANSACTION.

ORA-01454 cannot convert column into numeric datatype

Cause: A non-numeric value could not be converted into a number value.

Action: Check the value to make sure it contains only numbers, a sign, a decimal point, and the character "E" or "e", then retry the operation.

ORA-01455 converting column overflows integer datatype

Cause: The converted form of the specified expression was too large for the specified datatype.

Action: Define a larger datatype or correct the data.

ORA-01456 may not perform insert/delete/update operation inside a READ ONLY transaction

Cause: A non-DDL insert/delete/update or select for update operation was attempted.

Action: Commit (or roll back) the transaction, and then re-execute.

ORA-01457 converting column overflows decimal datatype

Cause: The converted form of the specified expression was too large for the specified type. The problem also occurs in COBOL programs when using COMP-3 in the picture clause, which is acceptable to the Pro*COBOL Precompiler and to COBOL but results in this error.

Action: Define a larger datatype or correct the data.

ORA-01458 invalid length inside variable character string

Cause: An attempt was made to bind or define a variable character string with a buffer length less than the minimum requirement.

Action: Increase the buffer size or use a different type.

ORA-01459 invalid length for variable character string

Cause: The buffer length was less than the minimum required or greater than its length at bind time minus two bytes.

Action: Make sure the string size is long enough to hold the buffer.

ORA-01460 unimplemented or unreasonable conversion requested

Cause: The requested format conversion is not supported.

Action: Remove the requested conversion from the SQL statement. Check the syntax for the TO_CHAR, TO_DATE, and TO_NUMBER functions to see which conversions are supported.

ORA-01461 can bind a LONG value only for insert into a LONG column

Cause: An attempt was made to insert a value from a LONG datatype into another datatype. This is not allowed.

Action: Do not try to insert LONG datatypes into other types of columns.

ORA-01462 cannot insert string literals longer than 2000 characters

Cause: The longest literal supported by Oracle consists of 2000 characters.

Action: Reduce the number of characters in the literal to 2000 characters or fewer or use the VARCHAR2 or LONG datatype to insert strings exceeding 2000 characters.

ORA-01463 cannot modify column datatype with current constraint(s)

Cause: An attempt was made to modify the datatype of column which has referential constraints; or has check constraints which only allows changing the datatype from CHAR to VARCHAR or vise versa.

Action: Remove the constraint(s) or do not perform the offending operation.

ORA-01464 circular grant (granting to grant ancestor) of table or view

Cause: The user in the TO clause of the GRANT statement has already been GRANTed privileges on this table.

Action: Do not GRANT privileges on a table to the user who originally GRANTed privileges on that table. The statement in error is probably unnecessary.

ORA-01465 invalid hex number

Cause: In an UPDATE statement following a SELECT FOR UPDATE, part of the ROWID contains invalid characters. ROWID must be expressed in the proper and expected format for ROWID and within quotes.

Action: Enter the ROWID just as it was returned in the SELECT FOR UPDATE.

ORA-01466 unable to read data - table definition has changed

Cause: This is a time-based read consistency error for a database object, such as a table or index. Either of the following may have happened:

• The query was parsed and executed with a materialized view older than the time the object was changed.
• The creation time-stamp of the object is greater than the current system time. This happens, for example, when the system time is set to a time earlier than the creation time of the object.

Action: If the cause is:

• an old snapshot, then commit or rollback the transaction and resume work.
• a creation time-stamp in the future, ensure the system time is set correctly.

If the object creation time-stamp is still greater than the system time, then export the object's data, drop the object, re-create the object so it has a new creation time-stamp, import the object's data, and resume work.

ORA-01467 sort key too long

Cause: A DISTINCT, GROUP BY, ORDER BY, or SET operation requires a sort key longer than that supported by Oracle. Either too many columns or too many group functions were specified in the SELECT statement.

Action: Reduce the number of columns or group functions involved in the operation.

ORA-01468 a predicate may reference only one outer-joined table

Cause: A predicate in the WHERE clause has two columns from different tables with "(+)".

Action: Change the WHERE clause so that each predicate has a maximum of one outer-join table.

ORA-01469 PRIOR can only be followed by a column name

Cause: An invalid column name was specified after the PRIOR keyword.

Action: Check syntax, spelling, use a valid column name, and try again.

ORA-01470 In-list iteration does not support mixed operators

Cause: Constants of different types are specified in an in-list.

Action: Use constants of same type for in-lists.

ORA-01471 cannot create a synonym with same name as object

Cause: An attempt was made to create a private synonym with the same name as the object to which it refers. This error typically occurs when a user attempts to create a private synonym with the same name as one of their objects.

Action: Choose a different synonym name or create the synonym under a different username.

ORA-01472 cannot use CONNECT BY on view with DISTINCT, GROUP BY, etc.

Cause: CONNECT BY cannot be used on a view where there is not a correspondence between output rows and rows of the underlying table.

Action: Remove the DISTINCT or GROUP BY from the view or move the CONNECT BY clause into the view.

ORA-01473 cannot have subqueries in CONNECT BY clause

Cause: Subqueries cannot be used in a CONNECT BY clause.

Action: Remove the subquery or move it to the WHERE clause.

ORA-01474 cannot have START WITH or PRIOR without CONNECT BY

Cause: START WITH and PRIOR are meaningful only in connection with CONNECT BY.

Action: Check the syntax for the SQL statement and add a CONNECT BY clause, if necessary.

ORA-01475 must reparse cursor to change bind variable datatype

Cause: After executing a statement, an attempt was made to rebind a bind variable with a datatype different from that of the original bind.

Action: Re-parse the cursor before rebinding with a different datatype.

ORA-01476 divisor is equal to zero

Cause: An expression attempted to divide by zero.

Action: Correct the expression, then retry the operation.

ORA-01477 user data area descriptor is too large

Cause: This is an internal error message not normally issued.

Action: Contact Oracle Support Services.

ORA-01478 array bind may not include any LONG columns

Cause: User is performing an array bind with a bind variable whose maximum size is greater than 2000 bytes.

Action: Such bind variables cannot participate in array binds. Use an ordinary bind operation instead.

ORA-01479 last character in the buffer is not Null

Cause: A bind variable of type 97 does not contain null at the last position.

Action: Make the last character null.

ORA-01480 trailing null missing from STR bind value

Cause: A bind variable of type 5 (null-terminated string) does not contain the terminating null in its buffer.

Action: Terminate the string with a null character.

ORA-01481 invalid number format model

Cause: An invalid format parameter was used with the TO_CHAR or TO_NUMBER function.

Action: Correct the syntax, then retry the operation.

ORA-01482 unsupported character set

Cause: The character set used to perform the operation, such as the CONVERT function, is not a supported character set.

Action: Use one of the supported character sets.

kkORA-01484 arrays can only be bound to PL/SQL statements

Cause: At attempt was made to bind an array to a non-PL/SQL statement.

Action: Rewrite the offending code being careful to bind arrays only to PL/SQL statements.

ORA-01485 compile bind length different from execute bind length

Cause: You bound a buffer of type DTYVCS (VARCHAR with the two byte length in front) and at execute time the length in the first two bytes is more than the maximum buffer length, given in the bind call. The number of elements in the array and the current number of elements in the array cannot be more than the maximum size of the array.

Action: Ensure that the buffer size is sufficiently large to contain the array plus two bytes for the buffer length.

ORA-01486 size of array element is too large

Cause: An attempt was made to bind a data value that was either too large for the datatype, for example, NUMBER, or was greater than 2000 bytes, for example, VARCHAR or LONG.

Action: Find a way to convert or truncate the data value so that its length is acceptable.

ORA-01487 packed decimal number too large for supplied buffer

Cause: A conversion request cannot be performed because the buffer is too small to hold the result.

Action: Increase the size of the buffer.

ORA-01488 invalid nibble or byte in the input data

Cause: A conversion request cannot be performed because a digit was invalid.

Action: Fix the number and retry.

ORA-01489 result of string concatenation is too long

Cause: String concatenation result is more than the maximum size.

Action: Make sure that the result is less than the maximum size.

ORA-01490 invalid ANALYZE command

Cause: The syntax of the ANALYZE command was incorrect.

Action: Check the syntax and enter the command using the correct syntax.

ORA-01491 CASCADE option not valid

Cause: The CASCADE option should be used only for tables or clusters.

Action: Do not use the CASCADE option in this manner. Check the syntax of the statement and then retry.

ORA-01492 LIST option not valid

Cause: The LIST option can be used only for tables or clusters.

Action: Do not use the LIST option in this manner. Check the syntax of the statement and then retry.

ORA-01493 invalid SAMPLE size specified

Cause: The specified SAMPLE size is out of range

Action: Specify a value within the proper range.

ORA-01494 invalid SIZE specified

Cause: The specified histogram SIZE value was out of range.

Action: Specify a value within the proper range.

ORA-01495 specified chain row table not found

Cause: The specified table either does not exist or user does not have the proper privileges.

Action: Specify the correct table to use.

ORA-01496 specified chain row table form incorrect

Cause: The specified table does not have the proper field definitions.

Action: Specify the correct table to use.

ORA-01497 illegal option for ANALYZE CLUSTER

Cause: The FOR COLUMNS column_list clause cannot be used with ANALYZE CLUSTER.

Action: Retry with a legal syntax.

For more information about ANALYZE CLUSTER, see the Oracle9i SQL Reference.

ORA-01498 block check failure - see trace file

Cause: An error occurred while checking a block with the ANALYZE command.

Action: Check the trace file for more descriptive messages about the problem. Correct these errors. The name of the trace file is operating system-specific, for example, ORAxxxx.TRC. It is found in the directory specified by the initialization parameter USER_DUMP_DEST. If USER_DUMP_DEST is not set, trace files are not created. It may be necessary to re-create the object. See also your operating system-specific Oracle documentation.

ORA-01499 table/index cross reference failure - see trace file

Cause: An error occurred when validating an index or a table using the ANALYZE command. One or more entries does not point to the appropriate cross-reference.

Action: Check the trace file for more descriptive messages about the problem. Correct these errors. The name of the trace file is operating system-specific, for example, ORAxxxx.TRC. It is found in the directory specified by theUSER_DUMP_DEST initialization parameter. If USER_DUMP_DEST is not set, trace files are not created. It may be necessary to re-create the object. See also your operating system-specific Oracle documentation.

---

Copyright © 1996, 2002 Oracle Corporation.
All Rights Reserved.
Home
Book List
Contents
Index
Master Index
Feedback

Skip Headers

Oracle9i Database Error Messages
Release 2 (9.2)
Part Number A96525-01
Home
Book List
Contents
Index
Master Index
Feedback

---

 

4
ORA-01500 to ORA-02099

ORA-01500 failure in getting date/time

Cause: During CREATE DATABASE or ALTER TABLESPACE, there was a failure in getting the date and time.

Action: Contact Oracle Support Services.

ORA-01501 CREATE DATABASE failed

Cause: An error occurred during CREATE DATABASE.

Action: See accompanying errors.

ORA-01502 index 'string.string' or partition of such index is in unusable state

Cause: An attempt has been made to access an index or index partition that has been marked unusable by a direct load or by a DDL operation.

Action: DROP the specified index, or REBUILD the specified index, or REBUILD the unusable index partition.

ORA-01503 CREATE CONTROLFILE failed

Cause: An error occurred during CREATE CONTROLFILE.

Action: See accompanying errors.

ORA-01504 database name 'string' does not match parameter db_name 'string'

Cause: The name in a database create or mount does not match the name given in the initialization parameter DB_NAME.

Action: Correct or omit one of the two names.

ORA-01505 error in adding log files

Cause: During CREATE or ALTER DATABASE, error(s) occurred when adding new log files.

Action: Check error stack for detailed error information.

ORA-01506 missing or illegal database name

Cause: No database name was specified in the CREATE/ALTER DATABASE statement, and no DB_NAME initialization parameter was specified.

Action: Either the database name must be given in the statement or in the DB_NAME initialization parameter. Note that the SVRMGR or SQL*PLUS STARTUP command issues an ALTER DATABASE statement using the database name specified as part of STARTUP (if any).

ORA-01507 database not mounted

Cause: A command was attempted that requires the database to be mounted.

Action: If you are using the ALTER DATABASE statement via the SVRMGR or SQL*PLUS STARTUP command, specify the MOUNT option to restart; else if you are directly doing an ALTER DATABASE DISMOUNT, do nothing; else specify the MOUNT option to ALTER DATABASE. If you are doing a backup or copy, you must first mount the desired database.

ORA-01508 cannot create database; error in file 'string' at linestring

Cause: CREATE DATABASE was unable to process the specified file.

Action: Check the offending line in the specified file.

ORA-01509 specified name 'string' does not match actual 'string'

Cause: The database name specified in ALTER DATABASE does not match the name of the currently mounted database.

Action: Correct the database name spelling or DISMOUNT the mounted database.

ORA-01510 error in deleting log files

Cause: During ALTER DATABASE, an error occurred while dropping log files.

Action: Check the error stack for detailed error information.

ORA-01511 error in renaming log/data files

Cause: During ALTER DATABASE, an error occurred while renaming log or datafiles.

Action: Check the error stack for detailed error information.

ORA-01512 error renaming log file string - new filestring not found

Cause: An attempt to change a log file's name in the control file failed because no file was found with the new name.

Action: Make sure that the log file has been properly renamed by the operating system and retry.

ORA-01513 invalid current time returned by operating system

Cause: The operating system returned a time that was not between 1988 and 2121.

Action: Correct the time kept by the operating system.

ORA-01514 error in log specification: no such log

Cause: A log file name, or list of member names, did not correspond to an existing log.

Action: Specify an existing log file.

ORA-01515 error dropping log group string: no such log

Cause: ALTER DATABASE is attempting to drop a log file which is not known to the database control file.

Action: Specify the name of an existing log file.

ORA-01516 nonexistent log file, datafile, or tempfile "string"

Cause: An attempt was made to use ALTER DATABASE to rename a log file, datafile, or tempfile; or to change attributes of a datafile or tempfile (for example, such as resize, autoextend, online/offline, and so on); or to re-create a datafile. The attempt failed because the specified file is not known to the database's control file or is not of a type supported by the request.

Action: Specify the name or number of an existing file of the correct type, as appropriate. Check the relevantV$ table for a list of possible files.

ORA-01517 log member: 'string'

Cause: This message indicates the filename involved with other messages.

Action: See the accompanying messages and take appropriate action.

ORA-01518 CREATE DATABASE must specify more than one log file

Cause: Only one log file was specified in the CREATE DATABASE statement.

Action: Specify at least two log files.

ORA-01519 error while processing file 'string' near linestring

Cause: CREATE DATABASE encountered a problem while processing specified file. The specified file is bad.

Action: Retry your system installation procedure or contact Oracle Support Services.

ORA-01520 number of data files to add (string) exceeds limit ofstring

Cause: CREATE TABLESPACE statement specifies more files than is permitted for this database.

Action: Use fewer files or re-create the control file with a larger value of MAXDATAFILES.

ORA-01521 error in adding data files

Cause: During CREATE or ALTER TABLESPACE, an error was detected while adding datafiles.

Action: Check the error stack for detailed error information.

ORA-01522 file 'string' to be renamed does not exist

Cause: During ALTER TABLESPACE RENAME, a file to be renamed was not found in the database control file.

Action: Specify the correct file name.

ORA-01523 cannot rename data file to 'string' - file already part of database

Cause: During ALTER DATABASE RENAME or ALTER TABLESPACE RENAME, the new name of a file is already present in the control file.

Action: Rename the file to a name not already being used as part of the database.

ORA-01524 cannot create data file as 'string' - file already part of database

Cause: During ALTER DATABASE CREATE DATAFILE, the new name of a file is already present in the control file.

Action: Create the file as a name not already being used as part of the database.

ORA-01525 error in renaming data files

Cause: An error occurred when renaming files as part of ALTER TABLESPACE.

Action: Check the error stack for detailed information. All files are renamed except for those mentioned in the error stack.

ORA-01526 error in opening file 'string'

Cause: CREATE DATABASE was not able to open the specified file. This is probably due to a system installation error.

Action: Retry your system installation procedure or contact Oracle Support Services.

ORA-01527 error while reading file

Cause: CREATE DATABASE was not able to read the specified file. This is probably due to a system installation error.

Action: Retry your system installation procedure or contact Oracle Support Services.

ORA-01528 EOF while processing SQL statement

Cause: CREATE DATABASE unexpectedly hit EOF while reading the specified file. The SQL.BSQ file is bad.

Action: Retry your system installation procedure or contact Oracle Support Services.

ORA-01529 error closing file 'string'

Cause: CREATE DATABASE was not able to close the specified file.

Action: Retry your system installation procedure or contact Oracle Support Services.

ORA-01530 a database already mounted by the instance

Cause: During ALTER DATABASE MOUNT, an attempt is being made to mount a database on an instance in which a database is or has previously been mounted.

Action: If you wish to mount the database, shut down and then restart the instance and retry the operation.

ORA-01531 a database already open by the instance

Cause: During ALTER DATABASE, an attempt was made to open a database on an instance for which there is already an open database.

Action: If you wish to open a new database on the instance, first shut down and then restart the instance and retry the operation.

ORA-01532 cannot create database; instance being started elsewhere

Cause: During CREATE DATABASE, another user appears to be simultaneously altering the instance.

Action: Make sure no one else is simultaneously altering the instance. If no one is, contact Oracle Support Services; otherwise, retry the operation.

ORA-01533 cannot rename file 'string'; file does not belong to tablespace

Cause: During ALTER TABLESPACE RENAME, a file to be renamed was not found in the argument tablespace.

Action: Specify the correct file name or the correct tablespace name.

ORA-01534 rollback segment 'string' doesn't exist

Cause: During ALTER or DROP ROLLBACK SEGMENT, the specified rollback segment name is unknown.

Action: Use the correct rollback segment name.

ORA-01535 rollback segment 'string' already exists

Cause: Specified rollback segment already exists.

Action: Use a different name.

ORA-01536 space quota exceeded for tablespace 'string'

Cause: The space quota for the segment owner in the tablespace has been exhausted and the operation attempted the creation of a new segment extent in the tablespace.

Action: Either drop unnecessary objects in the tablespace to reclaim space or have a privileged user increase the quota on this tablespace for the segment owner.

ORA-01537 cannot add data file 'string' - file already part of database

Cause: During CREATE or ALTER TABLESPACE, a file being added is already part of the database.

Action: Use a different file name.

ORA-01538 failed to acquire any rollback segment

Cause: Failed to acquire any rollback segment during startup in shared mode.

Action: Restart in exclusive mode to create one more public segment or specify available private segments in the initialization parameter. ROLLBACK_SEGMENTS_REQUIRED, then start in shared mode

ORA-01539 tablespace 'string' is not online

Cause: Failed to either make a tablespace read only or offline because it is not online. A tablespace must be online before it can become read only or offline normal.

Action: Check the status of the tablespace. Use IMMEDIATE or TEMPORARY options to force all files offline. Bring the tablespace online before making it read only.

ORA-01540 tablespace 'string' is not offline

Cause: Failed to bring a tablespace online because it is not offline.

Action: Check the status of the tablespace.

ORA-01541 system tablespace cannot be brought offline; shut down if necessary

Cause: An attempt was made to bring system tablespace offline.

Action: Shut down if necessary to do recovery.

ORA-01542 tablespace 'string' is offline, cannot allocate space in it

Cause: An attempt was made to allocate space in an offline tablespace.

Action: Bring the tablespace online or create the object in other tablespace.

ORA-01543 tablespace 'string' already exists

Cause: An attempt was made to create a tablespace which already exists.

Action: Use a different name for the new tablespace.

ORA-01544 cannot drop system rollback segment

Cause: An attempt was made to drop system rollback segment.

Action: No action required.

ORA-01545 rollback segment 'string' specified not available

Cause: One of the following:

1. An attempt was made to bring a rollback segment online that is unavailable during startup; for example, the rollback segment is in an offline tablespace.
2. An attempt was made to bring a rollback segment online that is already online. This is because the rollback segment is specified twice in the ROLLBACK_SEGMENTS parameter in the initialization parameter file or the rollback segment is already online by another instance.
3. An attempt was made to drop a rollback segment that is currently online.
4. An attempt was made to alter a rollback segment that is currently online to use unlimited extents.
5. An attempt was made to online a rollback segment that is corrupted. This is because the rollback is specified in _corrupted_rollback_segments parameter in initialization parameter file.

Action: One of the following:

1. Make the rollback segment available; for example, bring an offline tablespace online.
2. Remove the name from the ROLLBACK_SEGMENTS parameter if the name is a duplicate or if another instance has already acquired the rollback segment.
3. Bring the rollback segment offline first. This may involve waiting for the active transactions to finish, or, if the rollback segment needs recovery, discover which errors are holding up the rolling back of the transactions and take appropriate actions.
4. Same as 3).
5. Remove the name from the _corrupted_rollback_segments parameter.

ORA-01546 tablespace contains active rollback segment 'string'

Cause: An attempt was made to make a tablespace that contains active rollback segment(s) offline or read only.

Action: Shut down instances that use the active rollback segments in the tablespace and then make the tablespace offline or read only.

ORA-01547 warning: RECOVER succeeded but OPEN RESETLOGS would get error below

Cause: Media recovery with one of the incomplete recovery options ended without error. However, if the ALTER DATABASE OPEN RESETLOGS command were attempted now, it would fail with the specified error. The most likely cause of this error is forgetting to restore one or more datafiles from a sufficiently old backup before executing the incomplete recovery.

Action: Rerun the incomplete media recovery using different datafile backups, a different control file, or different stop criteria.

ORA-01548 active rollback segment 'string' found, terminate dropping tablespace

Cause: An attempt was made to drop a tablespace that contains active rollback segment(s).

Action: Shut down instances that use the active rollback segments in the tablespace and then drop the tablespace.

ORA-01549 tablespace not empty, use INCLUDING CONTENTS option

Cause: An attempt was made to drop a non-empty tablespace.

Action: To drop all the objects in the tablespace, use the INCLUDING CONTENTS option.

ORA-01550 cannot drop system tablespace

Cause: An attempt was made to drop system tablespace. This is not allowed.

Action: No action required.

ORA-01551 extended rollback segment, pinned blocks released

Cause: Doing recursive extent of rollback segment, trapped internally by the system.

Action: No action required.

ORA-01552 cannot use system rollback segment for non-system tablespace 'string'

Cause: An attempt was made to use the system rollback segment for operations involving non-system tablespace. If this is a clone database then this will happen when attempting any data modification outside of the system tablespace. Only the system rollback segment can be online in a clone database.

Action: Create one or more private/public segment(s), shut down and restart. May need to modify the initialization parameter ROLLBACK_SEGMENTS to acquire private rollback segment. If this is a clone database being used for tablespace point in time recovery then this operation is not allowed.

ORA-01553 MAXEXTENTS must be no smaller than the string extents currently allocated

Cause: The number of extents allocated is greater than the MAXEXTENTS specified.

Action: Specify a larger MAXEXTENTS value.

ORA-01554 out of transaction slots in transaction tables

Cause: Too many concurrent transactions.

Action: Shut down the system, modify the initialization parameters TRANSACTIONS, ROLLBACK_SEGMENTS or ROLLBACK_SEGMENTS_REQUIRED, and then restart.

ORA-01555 snapshot too old: rollback segment number string with name "string" too small

Cause: Rollback records needed by a reader for consistent read are overwritten by other writers.

Action: If in Automatic Undo Management mode, increase the setting ofUNDO_RETENTION. Otherwise, use larger rollback segments.

ORA-01556 MINEXTENTS for rollback segment must be greater than 1

Cause: Specified MINEXTENTS of less than 2 for rollback segment.

Action: Specify larger MINEXTENTS.

ORA-01557 rollback segment extents must be at least string blocks

Cause: Specified extent of less than minimum size for rollback segment.

Action: Specify larger extents.

ORA-01558 out of transaction ID's in rollback segment string

Cause: All the available transaction IDs have been used.

Action: Shut down the instance and restart using other rollback segment(s), then drop the rollback segment that has no more transaction IDs.

ORA-01559 MAXEXTENTS for rollback segment must be greater than 1

Cause: Specified MAXEXTENTS of less than 2 for rollback segment.

Action: Specify larger MAXEXTENTS.

ORA-01560 LIKE pattern contains partial or illegal character

Cause: Like pattern is not formed correctly.

Action: Make sure like pattern is specified correctly.

ORA-01561 failed to remove all objects in the tablespace specified

Cause: Failed to remove all objects when dropping a tablespace.

Action: Retry the drop tablespace until all objects are dropped.

ORA-01562 failed to extend rollback segment number string

Cause: Failure occurred when trying to extend rollback segment.

Action: This is normally followed by another error message that caused the failure. You may take the rollback segment offline to perform maintenance. Use SELECT SEGMENT_NAME FROM DBA_ROLLBACK_SEGS WHERE SEGMENT_ID=string (where string is the segment number from the message) to determine the rollback segment name. Then use the ALTER ROLLBACK SEGMENT OFFLINE command to take the rollback segment offline.

ORA-01563 rollback segment is PUBLIC, need to use the keyword PUBLIC

Cause: Did not use the keyword PUBLIC to identified public rollback segment.

Action: Use the keyword PUBLIC when identifying public rollback segment.

ORA-01564 rollback segment is not PUBLIC

Cause: The rollback segment identified is not public.

Action: Do not use the keyword PUBLIC when identifying private rollback segment.

ORA-01565 error in identifying file 'string'

Cause: An error occurred while trying to identify a file.

Action: Check the error stack for detailed information.

ORA-01566 file specified more than once in DROP LOGFILE

Cause: The list of files supplied to DROP LOGFILE contains at least one duplicate.

Action: Remove the duplicate file specification and retry.

ORA-01567 dropping log string would leave less than 2 log files in threadstring

Cause: Dropping all the logs specified would leave fewer than the required two log files per enabled thread.

Action: Either drop fewer logs or disable the thread before deleting the logs. It may be possible to clear the log rather than drop it.

ORA-01568 cannot set space quota on PUBLIC

Cause: An attempt was made to set space quota on a tablespace for PUBLIC.

Action: If trying to grant system-wide or tablespace-wide space privileges to all users, use GRANT RESOURCE [ONtablespace] TO PUBLIC.

ORA-01569 data file too small for system dictionary tables

Cause: The datafile specified during creation of the database is too small to hold the system dictionary tables.

Action: Re-create the database by specifying a larger file or more files.

ORA-01570 MINEXTENTS must be no larger than the string extents currently allocated

Cause: The number of extents allocated is smaller than the MINEXTENTS specified.

Action: Specify a smaller MINEXTENTS value.

ORA-01571 redo version string incompatible with ORACLE versionstring

Cause: This software version cannot read the current redo logs, and either crash recovery is required or there are offline database files that need media recovery. If a file name is listed then it needs media recovery.

Action: Shut down and restart using the compatible software. Do any required media recovery, and open the database. Shut down and restart using the current software. If the file is going to be dropped then take it offline with the DROP option to skip this check.

ORA-01572 rollback segment string cannot be brought online,string extents exceeded

Cause: The number of extents in the rollback segment exceeds the hard limit. It cannot be brought online for writing.

Action: Drop and re-create the rollback segment.

ORA-01573 shutting down instance, no further change allowed

Cause: Some process tried to make changes while the database was being shut down.

Action: No action required.

ORA-01574 maximum number of concurrent transactions exceeded

Cause: The limit on the number of concurrent transactions has been hit.

Action: Shut down the system, increase the value of the initialization parameter TRANSACTIONS, and then restart the system.

ORA-01575 timeout waiting for space management resource

Cause: Failed to acquire necessary resource to do space management.

Action: Retry the operation.

ORA-01576 instance locking protocol version string incompatible with ORACLE versionstring

Cause: Current software uses incompatible locking protocol.

Action: Upgrade software used to start instances so that they use compatible locking protocol.

ORA-01577 cannot add log file 'string' - file already part of database

Cause: During CREATE or ALTER DATABASE, a file being added is already part of the database.

Action: Use a different file name.

ORA-01578 ORACLE data block corrupted (file # string, block #string)

Cause: The data block indicated was corrupted, probably due to program errors.

Action: Determine which object was corrupted using a command like the following:

SELECT SEGMENT_TYPE,OWNER||'.'||SEGMENT_NAME FROM DBA_EXTENTSWHERE file = FILE_ID AND block BETWEEN BLOCK_ID AND BLOCK_ID+BLOCKS -1;

where values for file and block are from the message.

Try to restore the segment containing the block indicated. This may involve dropping the segment and re-creating it. If there is a trace file, report the errors in it to Oracle Support Services.

ORA-01579 write error occurred during recovery

Cause: A write error occurred during recovery.

Action: Consult trace files for the nature of the write error, and correct error.

ORA-01580 error creating control backup file string

Cause: An operating system error occurred while attempting to create a control file backup.

Action: Check the error stack for more detailed information.

ORA-01581 attempt to use rollback segment (string) new extent (string) which is being allocated

Cause: Undo generated to extend a rollback segment has run out of current undo block space. Oracle is attempting to write into the new extent which has not been completely allocated.

Action: The rollback segment extending will be rolled back by the system, no more extension will be possible until the next extent is freed up by rolling back or committing other transactions.

ORA-01582 unable to open controlfile for backup

Cause: An operating system error occurred while attempting to open a control file for backup.

Action: Check the error stack for more detailed information.

ORA-01583 unable to get block size of controlfile to be backed up

Cause: An operating system error occurred while attempting to get the block size of a control file for backup.

Action: Check the error stack for more detailed information.

ORA-01584 unable to get file size of controlfile to be backed up

Cause: An operating system error occurred while attempting to get the file size of a control file for backup.

Action: Check the error stack for more detailed information.

ORA-01585 error identifying backup file string

Cause: An operating system error occurred when attempting to identify the file to be used for control file backup.

Action: Check the error stack for more detailed information.

ORA-01586 unable to open destination file string for backup

Cause: An operating system error occurred while attempting to open a control file for backup.

Action: Check the error stack for more detailed information.

ORA-01587 error during controlfile backup file copy

Cause: An operating system error occurred while attempting to copy a control file for backup.

Action: Check the accompanying message stack for detailed information and then take appropriate action.

ORA-01588 must use RESETLOGS option for database open

Cause: An earlier attempt to open the database with the RESETLOGS option did not complete, or recovery was done with a control file backup.

Action: Use the RESETLOGS option when opening the database.

ORA-01589 must use RESETLOGS or NORESETLOGS option for database open

Cause: Either incomplete or backup control file recovery has been performed. After these types of recovery you must specify either the RESETLOGS option or the NORESETLOGS option to open your database.

Action: Specify the appropriate option.

ORA-01590 number of segment free list (string) exceeds maximum ofstring

Cause: The value of the storage parameter FREELIST GROUPS is too large.

Action: Reduce the value of the storage parameter FREELIST GROUPS.

ORA-01591 lock held by in-doubt distributed transaction string

Cause: An attempt was made to access resource that is locked by a dead two-phase commit transaction that is in prepared state.

Action: The database administrator should query the PENDING_TRANS$ and related tables, and attempt to repair network connection(s) to coordinator and commit point. If timely repair is not possible, the database administrator should contact the database administrator at the commit point if known or the end user for correct outcome, or use heuristic default if given to issue a heuristic COMMIT or ABORT command to finalize the local portion of the distributed transaction.

ORA-01592 error converting Version 7 rollback segment (string) to Oracle 8 format

Cause: Look at the accompanying internal error; Version 7 database may not have shut down cleanly.

Action: Investigate the internal error; may have to reload the Version 7 database (from backup) and shut down the database cleanly.

ORA-01593 rollback segment optimal size (string blks) is smaller than the computed initial size (string blks)

Cause: Specified OPTIMAL size is smaller than the cumulative size of the initial extents during create rollback segment.

Action: Specify a larger OPTIMAL size.

ORA-01594 attempt to wrap into rollback segment (string) extent (string) which is being freed

Cause: Undo generated to free a rollback segment extent is attempting to write into the same extent due to small extents and/or there are too many extents to free.

Action: The rollback segment shrinking will be rolled back by the system; increase the optimal size of the rollback segment.

ORA-01595 error freeing extent (string) of rollback segment (string))

Cause: Some error occurred while freeing inactive rollback segment extents.

Action: Investigate the accompanying error.

ORA-01596 cannot specify system in string parameter

Cause: The system rollback segment is specified in the initialization parameter referred to in the error message.

Action: Change the value of the initialization parameter.

ORA-01597 cannot alter system rollback segment online or offline

Cause: An attempt was made to online or offline the system rollback segment.

Action: No action required.

ORA-01598 rollback segment 'string' is not online

Cause: Could have been taken offline before by the database administrator or cleaned up by SMON.

Action: Check the status of rollback segment in UNDO$ or DBA_ROLLBACK_SEGS to make sure the rollback segment is actually online.

ORA-01599 failed to acquire rollback segment (string), cache space is full

Cause: The amount statically allocated is not enough based on the value of the MAX_ROLLBACK_SEGMENTS parameter.

Action: For now, take another rollback segment offline or increase the value of the parameter MAX_ROLLBACK_SEGMENTS.

ORA-01600 at most one "string" in clause "string" ofstring

Cause: The initialization parameter was incorrectly specified.

Action: Correct the initialization parameter and restart the instance.

ORA-01601 illegal bucket size in clause "string" ofstring

Cause: The bucket size was invalid for this parameter.

Action: Correct the initialization parameter and restart the instance.

ORA-01603 illegal grouping size in clause "string" ofstring

Cause: The grouping size was invalid for this parameter.

Action: Correct the initialization parameter and restart the instance.

ORA-01604 illegal number range in clause "string" ofstring

Cause: The number range was invalid for this parameter.

Action: Correct the initialization parameter and restart the instance.

ORA-01605 missing numbers in clause "string" of string

Cause: The numbers were missing for this parameter.

Action: Correct the initialization parameter and restart the instance.

ORA-01606 gc_files_to_locks not identical to that of another mounted instance

Cause: The GC_FILES_TO_LOCKS parameters were different on two instances.

Action: Modify the initialization parameter GC_FILES_TO_LOCKS and restart.

ORA-01607 gc_lck_procs (string) is not the same as other instances (string)

Cause: The GC_LCK_PROCS initialization parameter is not the same as in other instances that already have the database open.

Action: Modify the GC_LCK_PROCS parameter and restart the instance.

ORA-01608 cannot bring rollback segment 'string' online, its status is (string)

Cause: Could have been brought online before by the database administrator or left as a result of process crash.

Action: Check the status of rollback segment in UNDO$ or DBA_ROLLBACK_SEGS

ORA-01609 log string is the current log for threadstring - cannot drop members

Cause: A member of the current log for a thread cannot be dropped.

Action: If the thread is opened, request a log switch by the instance that is using it. If it is not open, disable the thread, manually archive the log, or clear it.

ORA-01610 recovery using the BACKUP CONTROLFILE option must be done

Cause: Either an earlier database recovery session specified BACKUP CONTROLFILE, or the control file was re-created with the RESETLOGS option, or the control file being used is a backup control file. After that only BACKUP CONTROLFILE recovery is allowed and it must be followed by a log reset at the next database open.

Action: Perform recovery using the BACKUP CONTROFILE option.

ORA-01611 thread number string is invalid - must be between 1 andstring

Cause: A thread number in a command is greater than the number of threads supported by the control file.

Action: Use a thread number that is valid, or resize the thread record and/or checkpoint progress record sections of the control file.

ORA-01612 thread string is already enabled

Cause: An attempt was made to enable a thread that is already enabled.

Action: Either use this thread or enable another thread.

ORA-01613 thread string only has string logs - at least 2 logs required to enable

Cause: The thread cannot be enabled because it only has two online log files associated with it.

Action: Add logs to the thread or pick another thread to enable.

ORA-01614 thread string is busy - cannot enable

Cause: The mount enqueue for the thread could not be acquired when attempting to enable the thread. This probably means that another process has already started enabling this thread.

Action: Wait and try again, or find another thread to enable.

ORA-01615 thread string is mounted - cannot disable

Cause: Some instance, possibly this one, has allocated the thread for its use. The thread may not be disabled while in use.

Action: Shut down cleanly the instance using the thread.

ORA-01616 thread string is open - cannot disable

Cause: The thread is not closed. The last instance to use the thread died leaving the thread open. A thread cannot be disabled until it is closed. It is still required for crash or instance recovery.

Action: If the database is open, instance recovery should close the thread soon; wait a few minutes. Otherwise open the database; crash recovery will close the thread.

ORA-01617 cannot mount: string is not a valid thread number

Cause: The value of the initialization parameter THREAD is not between 1 and the number of threads allowed by the control file.

Action: Shut down the instance, change the value of the initialization parameter and restart, or resize the thread record and/or checkpoint progress record sections of the control file.

ORA-01618 thread string is not enabled - cannot mount

Cause: The value of the initialization parameter THREAD requests a thread that is not enabled. A thread must be enabled before it can be mounted.

Action: Shut down the instance, change the value of the initialization parameter and restart, mounting a different thread. If the database is open in another instance, then the thread may be enabled.

ORA-01619 thread string is mounted by another instance

Cause: The value of the initialization parameter THREAD requests a thread that has been mounted by another instance. Only one instance may use a thread.

Action: Shut down the instance, change the value of the initialization parameter and restart, mounting a different thread.

ORA-01620 no public threads are available for mounting

Cause: The value of the initialization parameter THREAD is zero, its default value. There are no threads which have been publicly enabled, and not mounted.

Action: Shut down the instance, change the value of the initialization parameter to a thread which is privately enabled and not mounted. If the database is open in another instance, then a thread may be publicly enabled.

ORA-01621 cannot rename member of current log if database is open

Cause: This is a rename command for a member of the current log for an open thread. If the database is open anywhere, the log may be in use, so the rename cannot be done.

Action: Wait until the log is not current, or mount the database exclusively.

ORA-01622 thread number must be specified - default not specific

Cause: The thread was not specified when adding a log, and the currently mounted thread was chosen by default at mount time. Since the current thread was not specified explicitly the user cannot know which thread the log will be added to.

Action: Explicitly specify the thread number either in the initialization parameter THREAD, or in the ADD command.

ORA-01623 log string is current log for thread string - cannot drop

Cause: A thread's current log cannot be dropped even if the thread is closed. A disabled thread usually does not have a current log, but a half completed disable may need to be disabled again.

Action: If the database is not open then disable the thread. If the database is open and an instance has the thread open, then the instance can be requested to switch logs. If the database is closed the log can be archived or cleared to force a switch.

ORA-01624 log string needed for crash recovery of threadstring

Cause: A log cannot be dropped or cleared until the thread's checkpoint has advanced out of the log.

Action: If the database is not open then open it. Crash recovery will advance the checkpoint. If the database is open force a global checkpoint. If the log is corrupted so that the database cannot be opened, it may be necessary to do incomplete recovery until cancel at this log.

ORA-01625 rollback segment 'string' does not belong to this instance

Cause: An attempt was made to shrink or take a rollback segment offline that does not belong to this instance.

Action: Take only those rollback segments offline that belong to the current instance. To take the rollback segment offline, connect to the instance containing it.

ORA-01626 rollback segment number 'string' cannot handle more transactions

Cause: Too many transactions in this segment.

Action: Choose a different rollback segment, or reduce the number of concurrent transactions.

ORA-01627 rollback segment number 'string' is not online

Cause: Could have been taken offline before by the database administrator or cleaned up by SMON.

Action: Check the status of rollback segment in UNDO$ or DBA_ROLLBACK_SEGS to make sure the rollback segment is actually online.

ORA-01628 max # extents (string) reached for rollback segmentstring

Cause: An attempt was made to extend a rollback segment that was already at the MAXEXENTS value.

Action: If the value of the MAXEXTENTS storage parameter is less than the maximum allowed by the system, raise this value.

ORA-01629 max # extents (string) reached saving undo for tablespacestring

Cause: Save undo for the offline tablespace at MAXEXTENTS.

Action: Check the storage parameters for the system tablespace. The tablespace needs to be brought back online so the undo can be applied.

ORA-01630 max # extents (string) reached in temp segment in tablespacestring

Cause: A temporary segment tried to extend past MAXEXTENTS.

Action: If MAXEXTENTS for the tablespace is less than the system maximum, you can raise that. Otherwise, raise PCTINCREASE for the tablespace.

ORA-01631 max # extents (string) reached in tablestring.string

Cause: A table tried to extend past MAXEXTENTS.

Action: If MAXEXTENTS is less than the system maximum, raise it. Otherwise, you must re-create with larger initial, next or PCTINCREASE parameters.

ORA-01632 max # extents (string) reached in indexstring.string

Cause: An index tried to extend past MAXEXTENTS.

Action: If the value of MAXEXTENTS in the index storage clause is less than the maximum (based on your block size), raise it. Otherwise, re-create the index with larger extent sizes so that the total number of extents falls below the maximum.

ORA-01633 Real Application Clusters Option needed for this operation

Cause: System does not have Real Application Clusters configured.

Action: Obtain Real Application Clusters option.

ORA-01634 rollback segment number 'string' is about to go offline

Cause: The rollback segment specified was marked to go offline by the database administrator.

Action: Bring the rollback segment online first.

ORA-01635 rollback segment #string specified not available

Cause: One of the following:

• You tried to acquire an offline rollback segment during startup.
• You tried to drop a rollback segment that contains active transactions.

Action: For the above, one of the following:

• Bring the tablespace containing the rollback segment online or do not specify the rollback segment in the initialization parameter file.
• If the rollback segment is in use, shut down the instance using the rollback segment. Otherwise, if the rollback segment needs recovery, determine which errors are holding back the rolling back of the transactions and take appropriate action.

ORA-01636 rollback segment 'string' is already online

Cause: A rollback segment can only be used by one instance and an instance is trying to bring a rollback segment online that is already in use.

Action: Check that the values set in the initialization parameter file for parameters ROLLBACK_SEGMENTS, ROLLBACK_SEGMENT_INITIAL, and ROLLBACK_SEGMENT_COUNT are correctly set for the instance with the problem. Also check that the instance is using the correct initialization parameter file. Make sure you are not confused about the difference between private and public rollback segments. See theOracle9i Database Administrator's Guide for more information about using rollback segments in parallel mode.

ORA-01637 rollback segment 'string' is being used by another instance (#string)

Cause: A rollback segment can only be used by one instance, and an instance is trying to access a rollback segment online that is already in use.

Action: Check that the values set in the initialization parameter file for parameters ROLLBACK_SEGMENTS, ROLLBACK_SEGMENT_INITIAL, and ROLLBACK_SEGMENT_COUNT are correctly set for the instance with the problem. Also check that the instance is using the correct initialization parameter file. Make sure you are not confused about the difference between private and public rollback segments. See theOracle9i Database Administrator's Guide for more information about using rollback segments in parallel mode.

ORA-01638 parameter string does not allow ORACLE versionstring to mount cluster database

Cause: The value of the RECOVERY_COMPATIBLE parameter is set too low to allow this software version to mount in cluster database mode.

Action: Either use an earlier software release or advance the RECOVERY_COMPATIBLE parameter. If this happens when no RECOVERY_COMPATIBLE parameter has been specified then set it to the current software release.

ORA-01640 cannot make tablespace read only with active transactions

Cause: An attempt was made to make a tablespace read only while there are active transactions in the database. All transactions must commit or rollback to insure that there is no undo for a tablespace before it can be made read only. This includes in doubt distributed transactions.

Action: Prevent any more transactions from being started. Putting the database in restricted mode usually helps. If there are any in doubt transactions they must also be resolved.

ORA-01641 tablespace 'string' is not online - cannot add data file

Cause: An attempt was made to add a datafile to a tablespace that has been set to read only or offline.

Action: Make the tablespace online and read write then add the datafile.

ORA-01642 begin backup not needed for read only tablespace 'string'

Cause: An attempt was made to begin or end a backup for a tablespace that has been set to read only.

Action: Take the backup without any BEGIN or END commands. The files are not being modified so the backup will be consistent.

ORA-01643 system tablespace can not be made read only

Cause: An attempt was made to set the system tablespace to read only. The system tablespace must remain read write for database operation.

Action: Leave system tablespace read write.

ORA-01644 tablespace 'string' is already read only

Cause: An attempt was made to make tablespace read only that is already read only.

Action: Leave tablespace read only, or make read write then make read only again.

ORA-01645 previous attempt to make read write is half complete

Cause: A failure while making the tablespace read write left it read only, but the checkpoint was advanced. The tablespace will not be usable after a resetlogs if its files are offline.

Action: Repeat the command to make the tablespace read write.

ORA-01646 tablespace 'string' is not read only - cannot make read write

Cause: An attempt was made to make a tablespace read write that is not read only. It may be either online or offline.

Action: Leave tablespace read write.

ORA-01647 tablespace 'string' is read only, cannot allocate space in it

Cause: An attempt was made to allocate space in a read-only tablespace.

Action: Create the object in another tablespace.

ORA-01648 log string is the current log of disabled threadstring

Cause: An attempt to enable the thread failed after it was half completed. This log was left as the current log even though the thread is still disabled. Since a log switch cannot be done until the thread is enabled, the log cannot be cleared or archived.

Action: Complete the thread enable by issuing the ENABLE command again.

ORA-01649 operation not allowed with a backup controlfile

Cause: An attempt is being made to perform a command that does not make sense when the control file is a restored backup.

Action: Wait until after the database has been opened and try again.

ORA-01650 unable to extend rollback segment string bystring in tablespace string

Cause: Failed to allocate an extent for rollback segment in tablespace.

Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

ORA-01651 unable to extend save undo segment by string for tablespacestring

Cause: Failed to allocate an extent for saving undo entries for the indicated offline tablespace.

Action: Check the storage parameters for the SYSTEM tablespace. The tablespace needs to be brought back online so the undo can be applied.

ORA-01652 unable to extend temp segment by string in tablespacestring

Cause: Failed to allocate an extent for temporary segment in tablespace.

Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

ORA-01653 unable to extend table string.string bystring in tablespace string

Cause: Failed to allocate an extent for table segment in tablespace.

Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

ORA-01654 unable to extend index string.string bystring in tablespace string

Cause: Failed to allocate an extent for index segment in tablespace.

Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

ORA-01655 unable to extend cluster string.string bystring in tablespace string

Cause: Failed to allocate an extent for cluster segment in tablespace.

Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

ORA-01656 max # extents (string) reached in clusterstring.string

Cause: A cluster tried to extend past MAXEXTENTS.

Action: If MAXEXTENTS is less than the system maximum, raise it. Otherwise, you must re-create with larger initial, next or PCTINCREASE parameters.

ORA-01657 invalid SHRINK option value

Cause: The specified value must be an integer.

Action: Choose an appropriate integer value.

ORA-01658 unable to create INITIAL extent for segment in tablespace string

Cause: Failed to find sufficient contiguous space to allocate INITIAL extent for segment being created.

Action: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the tablespace or retry with a smaller value for INITIAL.

ORA-01659 unable to allocate MINEXTENTS beyond string in tablespacestring

Cause: Failed to find sufficient contiguous space to allocate MINEXTENTS for the segment being created.

Action: Use ALTER TABLESPACE ADD DATAFILE to add additional space to the tablespace or retry with smaller value for MINEXTENTS, NEXT or PCTINCREASE.

ORA-01660 tablespace 'string' is already permanent

Cause: An attempt was made to make tablespace permanent that is already permanent.

Action: Leave tablespace permanent.

ORA-01661 tablespace 'string' is already temporary

Cause: An attempt was made to make tablespace temporary that is already temporary.

Action: Leave tablespace permanent.

ORA-01662 tablespace 'string' is non-empty and cannot be made temporary

Cause: An attempt was made to convert a non-empty tablespace to a temporary tablespace

Action: Drop all the objects in the tablespace.

ORA-01663 the contents of tablespace 'string' is constantly changing

Cause: The contents of the tablespace is always changing between PERMANENT and TEMPORARY.

Action: Decide what the tablespace contents should be and stay with it.

ORA-01664 Transaction which has expanded the Sort Segment has aborted

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-01665 controlfile is not a standby controlfile

Cause: An attempt was made to mount, recover or activate a standby database without a standby control file.

Action: Create a standby control file before attempting to use the database as a standby database.

ORA-01666 controlfile is for a standby database

Cause: An attempt was made to mount, recover, or open a standby database without the appropriate command option to designate a standby database.

Action: Use the standby option or appropriate commands, or mount with the primary control file.

ORA-01667 cannot add any more tablespaces: limit of string exceeded

Cause: There is no more room in the control file for adding tablespaces.

Action: Resize the control file or drop other tablespaces.

ORA-01668 standby database requires DROP option for offline of data file

Cause: An attempt was made to take a datafile offline in a standby database without specifying the DROP option. Files that are offline in a standby database are not recovered, and are likely to be unusable if the standby is activated. Note that specifying DROP does not prevent bringing the file online later.

Action: Specify the DROP option or leave the file online.

ORA-01669 standby database controlfile not consistent

Cause: An attempt was made to activate a standby database with a control file that has not been recovered to the same point as the datafiles. Most likely the control file was just copied from the primary database and has not been used for recovery.

Action: Recover the standby database until all the files are consistent.

ORA-01670 new datafile string needed for standby database recovery

Cause: Standby database recovery noticed that a file was added to the primary database, but is not available on the standby.

Action: Either copy the file from the primary database or do an ALTER DATABASE CREATE DATAFILE command on the standby to create a file to recover.

ORA-01671 controlfile is a backup, cannot make a standby controlfile

Cause: The currently mounted control file is a backup control file, and attempting to create a control file for a standby database.

Action: Complete any needed recovery and open the database with the resetlogs option.

ORA-01672 controlfile may be missing files or have extra ones

Cause: An attempt was made to create a standby control file, but the control file was either recently created via CREATE CONTROLFILE or an incomplete recovery has been done. Thus the datafiles in the control file and the ones in the data dictionary may not match.

Action: Open the database, then retry the operation.

ORA-01673 data file string has not been identified

Cause: This datafile was not in the control file after an incomplete recovery or CREATE CONTROLFILE. Since information from its header is needed for standby database recovery, we cannot create a standby control file.

Action: Find the file and bring it online. If desired it may be taken offline again. If you intend to drop this file, then taking it offline with the DROP option will avoid this error.

ORA-01674 data file string is an old incarnation rather than current file

Cause: Recovery encountered redo that indicates this file was dropped from the database and another file was added using the same file number. This implies that a CREATE CONTROLFILE command was given the old file which was dropped rather than the latest file.

Action: Rebuild the control file using CREATE CONTROLFILE, and give the correct file.

ORA-01675 max_commit_propagation_delay inconsistent with other instances

Cause: The MAX_COMMIT_PROPAGATION_DELAY initialization parameter is inconsistent with those in other instances.

Action: Make sure all instances have the same MAX_COMMIT_PROPAGATION_DELAY.

ORA-01676 standby file name convert of 'string' exceeds maximum length ofstring

Cause: When the given file name is converted to the name used for the standby database, the converted name is bigger than the maximum allowed file name.

Action: Change the value of the initialization parameter DB_FILE_STANDBY_NAME_CONVERT or LOG_FILE_STANDBY_NAME_CONVERT to convert to a valid file name.

ORA-01677 standby file name convert parameters differ from other instance

Cause: The DB_FILE_STANDBY_NAME_CONVERT or LOG_FILE_STANDBY_NAME_CONVERT initialization parameters are not the same as in other instances that already have the database mounted.

Action: Change the value of the initialization parameters DB_FILE_STANDBY_NAME_CONVERT and LOG_FILE_STANDBY_NAME_CONVERT to match other instances.

ORA-01678 parameter string must be pairs of pattern and replacement strings

Cause: The initialization parameter does not have an even number of strings for its value. The odd numbered strings are patterns to be found in file names. The even numbered strings are used to replace the corresponding patterns when found in file names.

Action: Specify an even number of strings for the parameter, or omit the parameter.

ORA-01679 database must be mounted EXCLUSIVE and not open to activate

Cause: An attempt to activate a standby database was made when the database was not mounted EXCLUSIVE or was already open.

Action: Mount the database EXCLUSIVE and retry the ACTIVATE command.

ORA-01680 unable to extend LOB segment by string in tablespacestring

Cause: Failed to allocate an extent for a LOB segment in tablespace.

Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

ORA-01681 max # extents (string) reached in LOB segment in tablespacestring

Cause: A LOB segment tried to extend past MAXEXTENTS.

Action: If MAXEXTENTS for the tablespace is less than the system maximum, you can raise that. Otherwise, raise PCTINCREASE for the tablespace.

ORA-01682 read-only DB cannot allocate temporary space in tablespace string

Cause: Temporary space (usually for sorting) could not be allocated in either main storage or a temporary file. An attempt was made to allocate the space from the tablespace named, but the database is opened read only. The database open requires a sort work space.

Action: Either allow sufficient workspace in main storage (SORT_AREA_SIZE initialization parameter), or create a temporary tablespace before making the database read only. Use ALTER TABLESPACE ADD TEMPFILE statement to add temporary files to the temporary tablespace.

ORA-01683 unable to extend index string.string partitionstring by string in tablespace string

Cause: Failed to allocate an extent for index segment in tablespace.

Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

ORA-01684 max # extents (string) reached in tablestring.string partition string

Cause: A table tried to extend past MAXEXTENTS.

Action: If MAXEXTENTS is less than the system maximum, raise it. Otherwise, you must re-create with larger initial, next or PCTINCREASE parameters.

ORA-01685 max # extents (string) reached in indexstring.string partition string

Cause: An index tried to extend past MAXEXTENTS.

Action: If MAXEXTENTS is less than the system max, raise it. Otherwise, you must re-create with larger initial, next or PCTINCREASE parameters.

ORA-01686 max # files (string) reached for the tablespacestring

Cause: The number of files for a given tablespace has reached its maximum value.

Action: Resize existing files in the tablespace, or partition the objects among multiple tablespaces, or move some objects to a different tablespace.

ORA-01687 specified logging attribute for tablespace 'string' is same as the existing

Cause: An attempt was made to change the tablespace default logging attribute (LOGGING or NOLOGGING) to be the same as the existing logging attribute.

Action: Change the specified logging attribute.

ORA-01688 unable to extend table string.string partitionstring by string in tablespace string

Cause: Failed to allocate an extent for table segment in tablespace.

Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

ORA-01689 syntax error in clause "string" of string

Cause: There was a syntax in the initialization parameter.

Action: Fix the syntax error and restart the instance.

ORA-01690 sort area size too small

Cause: The sort area size was too small to fit two records in memory.

Action: Increase the SORT_AREA_SIZE initialization parameter.

ORA-01691 unable to extend lob segment string.string bystring in tablespace string

Cause: Failed to allocate an extent for LOB segment in tablespace.

Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

ORA-01692 unable to extend lob segment string.string partitionstring by string in tablespace string

Cause: Failed to allocate an extent for LOB segment in tablespace.

Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.

ORA-01693 max # extents (string) reached in lob segmentstring.string

Cause: A LOB segment tried to extend past MAXEXTENTS.

Action: If MAXEXTENTS is less than the system max, raise it. Otherwise, you must re-create with larger initial, next or PCTINCREASE parameters.

ORA-01694 max # extents (string) reached in lob segmentstring.string partition string

Cause: A LOB segment tried to extend past MAXEXTENTS.

Action: If MAXEXTENTS is less than the system max, raise it. Otherwise, you must re-create with larger initial, next or PCTINCREASE parameters.

ORA-01695 error converting rollback segment string to version 8.0.2

Cause: Version 8.0.1 database may not have shut down cleanly.

Action: May have to reload the 8.0.1 database and shut down cleanly.

ORA-01696 controlfile is not a clone controlfile

Cause: An attempt was made to mount, a database as a clone when it is already mounted by another instance not as a clone or attempting to use a current control file for a clone.

Action: Mount without the clone option or use a backup control file and shut down the other instances before mounting as a clone.

ORA-01697 controlfile is for a clone database

Cause: An attempt was made to mount a clone database without the appropriate command option to designate a clone database.

Action: Use the clone option or appropriate commands, or mount with the primary control file.

ORA-01698 a clone database may only have SYSTEM rollback segment online

Cause: An attempt was made to online a rollback segment in a clone database.

Action: Do not use this command.

ORA-01699 tablespace 'string' is being imported for point in time recovery

Cause: An attempt was made to online a tablespace or begin another point in time import while a point in time import is already in progress.

Action: Wait until the import completes.

ORA-01700 duplicate username in list

ORA-01701 a cluster is not appropriate here

ORA-01702 a view is not appropriate here

ORA-01703 missing SYNONYM keyword

ORA-01704 string literal too long

Cause: The string literal is longer than 4000 characters.

Action: Use a string literal of at most 4000 characters. Longer values may only be entered using bind variables.

ORA-01705 an outer join cannot be specified on a correlation column

ORA-01706 user function result value was too large

ORA-01707 missing LIST keyword

ORA-01708 ACCESS or SESSION expected

ORA-01709 program does not exist

ORA-01710 missing OF keyword

ORA-01711 duplicate privilege listed

ORA-01712 you cannot grant a privilege which you do not have

ORA-01713 GRANT OPTION does not exist for that privilege

ORA-01714 error in execution of user function

ORA-01715 UNIQUE may not be used with a cluster index

Cause: An attempt was made to create a cluster index with the UNIQUE attribute.

Action: Remove UNIQUE from the CREATE INDEX statement.

ORA-01716 NOSORT may not be used with a cluster index

Cause: An attempt was made to create a cluster index using the NOSORT option.

Action: Remove NOSORT from the CREATE INDEX statement.

ORA-01717 seccta: invalid access mode token passed

ORA-01718 BY ACCESS | SESSION clause not allowed for NOAUDIT

Cause: Attempt to specify BY ACCESS | SESSION in a NOAUDIT statement.

Action: Remove BY ACCESS | SESSION.

ORA-01719 outer join operator (+) not allowed in operand of OR or IN

Cause: An outer join appears in an or clause.

Action: If A and B are predicates, to get the effect of (A(+) or B), try (select where (A(+) and not B)) union all (select where (B)).

ORA-01720 grant option does not exist for 'string.string'

Cause: A grant was being performed on a view and the grant option was not present for an underlying object.

Action: Obtain the grant option on all underlying objects of the view.

ORA-01721 USERENV(COMMITSCN) invoked more than once in a transaction

Cause: The USERENV('COMMITSCN') function can only be used once in a transaction.

Action: Re-write the transaction to use USERENV('COMMITSCN') only once.

ORA-01722 invalid number

Cause: The attempted conversion of a character string to a number failed because the character string was not a valid numeric literal. Only numeric fields or character fields containing numeric data may be used in arithmetic functions or expressions. Only numeric fields may be added to or subtracted from dates.

Action: Check the character strings in the function or expression. Check that they contain only numbers, a sign, a decimal point, and the character "E" or "e" and retry the operation.

ORA-01723 zero-length columns are not allowed

Cause: During CREATE TABLE, a zero-length column was specified, for example, CHAR(0).

Action: Correct the column declaration so that the length is at least 1 and try the operation again.

ORA-01724 floating point precision is out of range (1 to 126)

Cause: Floating point precision is too small or large.

Action: Correct and retry.

ORA-01725 USERENV('COMMITSCN') not allowed here

Cause: The function USERNEV('COMMMITSCN') is only allowed as a top-level expression in the VALUES clause of an INSERT statements, and on the right hand side of an assignment in an UPDATE statement.

Action: Correct the use of the function.

ORA-01726 a table is not appropriate here

Cause: A table name was used in a statement in which tables are not permitted.

Action: Enter a valid table statement or use the current statement on the appropriate object.

ORA-01727 numeric precision specifier is out of range (1 to 38)

Cause: The precision specified for a number column in a CREATE/ALTER TABLE or CREATE CLUSTER statement must be a digit between 1 and 38. If no precision is specified, a default precision of 22 digits is used.

Action: Specify numeric precision between 1 and 38 and retry the statement.

ORA-01728 numeric scale specifier is out of range (-84 to 127)

Cause: The scale specified for a numeric field in a CREATE/ALTER TABLE or CREATE CLUSTER statement is not in the valid range. It should be between -84 and 127.

Action: Specify a numeric scale between -84 and 127. If a number is not specified, the default scale of the column is 0 decimal places.

ORA-01729 database link name expected

Cause: A database link name does not follow the at-sign (@) in a reference to a table in a remote database.

Action: Correct the reference and retry the operation. The correct syntax for denoting a table in a remote database follows:

username.table_name@ database_name 

Spaces before and after the at-sign (@) are optional.

ORA-01730 invalid number of column names specified

Cause: The number of column names specified in a CREATE VIEW statement did not correspond to the number of columns listed in the SELECT clause. If column names are specified in a CREATE VIEW statement, exactly one name must be specified for each column or expression in the SELECT clause.

Action: Specify one view column name for each column in the SELECT clause.

ORA-01731 circular view definition encountered

Cause: Through a series of CREATE and DROP VIEW statements, a view was defined that refers to itself. For example, VIEW1 might include a column from VIEW2 that is defined as a column in VIEW1. View definitions may be seen by querying the data dictionary.

Action: Check the view definitions, remove any circular references, and retry the statements.

ORA-01732 data manipulation operation not legal on this view

Cause: An attempt was made to use an UPDATE, INSERT, or DELETE statement on a view that contains expressions or functions or was derived from more than one table. If a join operation was used to create the view or the view contains virtual columns derived from functions or expressions, then the view may only be queried.

Action: UPDATE, INSERT, or DELETE rows in the base tables instead and restrict the operations on the view to queries.

ORA-01733 virtual column not allowed here

Cause: An attempt was made to use an INSERT, UPDATE, or DELETE statement on an expression in a view.

Action: INSERT, UPDATE, or DELETE data in the base tables, instead of the view.

ORA-01734 illegal parameters - EXTENT MIN higher than EXTENT MAX

Cause: An incorrect value is specified for the parameter.

Action: Correct the parameter and reissue the statement.

ORA-01735 invalid ALTER TABLE option

Cause: An invalid option was specified in an ALTER TABLE statement.

Action: Check the statement syntax, specify a valid option, and retry the statement.

ORA-01736 [NOT] SUCCESSFUL expected

Cause: An AUDIT or NOAUDIT statement contained WHENEVER followed by something other than SUCCESSFUL or NOT SUCCESSFUL.

Action: Correct the WHENEVER clause and retry the statement.

ORA-01737 valid modes: [ROW] SHARE, [[SHARE] ROW] EXCLUSIVE, SHARE UPDATE

Cause: The lock mode entered was not recognized.

Action: Enter one of the following: SHARE, ROW SHARE, EXCLUSIVE, ROW EXCLUSIVE, SHARE ROW EXCLUSIVE, or SHARE UPDATE.

ORA-01738 missing IN keyword

Cause: In a LOCK TABLE statement, the keyword IN was missing.

Action: Place the keyword IN and lock mode directly after the table name in the LOCK TABLE statement and retry the statement.

ORA-01739 missing MODE keyword

Cause: In a LOCK TABLE statement, the keyword MODE was missing. The keyword MODE must directly follow the specified lock mode.

Action: Check the statement syntax, insert the keyword MODE where required, and retry the statement.

ORA-01740 missing double quote in identifier

Cause: An initial double quote (") was found without a closing quote. If an identifier contains a blank or special characters other than $, #, or _, it must be enclosed in double quotes.

Action: Add a closing double quote (") to the end of the identifier.

ORA-01741 illegal zero-length identifier

Cause: An attempt was made to use two double quotes ("") as an identifier. An identifier must be at least one character long.

Action: Insert at least one character between the double quotes in the identifier. If a blank identifier is required, specify a blank space between the double quotes (" ").

ORA-01742 comment not terminated properly

Cause: The indicated comment or hint begun with the /* token did not have the terminating */.

Action: Properly terminate the comment or hint with a */.

ORA-01743 only pure functions can be indexed

Cause: The indexed function uses SYSDATE or the user environment.

Action: PL/SQL functions must be pure (RNDS, RNPS, WNDS, WNPS). SQL expressions must not use SYSDATE, USER, USERENV(), or anything else dependent on the session state. NLS-dependent functions are OK.

ORA-01744 inappropriate INTO

Cause: The INTO clause may not be used in a subquery.

Action: Check the syntax, place the INTO clause in the top-level query, and retry the statement.

ORA-01745 invalid host/bind variable name

Cause: A colon in a bind variable or INTO specification was followed by an inappropriate name, perhaps a reserved word.

Action: Change the variable name and retry the operation.

ORA-01746 indicator variable not permitted here

Cause: An indicator variable is not permitted in this context.

Action: Remove the indicator variable and retry the operation.

ORA-01747 invalid user.table.column, table.column, or column specification

Cause: A column name was specified improperly in the current SQL statement.

Action: Check the statement's syntax, especially references to column names, and retry the statement.

ORA-01748 only simple column names allowed here

Cause: This SQL statement does not allow a qualified column name, such asusername.table.column or table.column.

Action: Remove the qualifications from the column and retry the operation.

ORA-01749 you may not GRANT/REVOKE privileges to/from yourself

Cause: Grantor is not allowed to grant or revoke object or system privileges to self.

Action: Issue the GRANT or REVOKE of system privileges from another database administrator account.

ORA-01750 UPDATE/REFERENCES may only be REVOKEd from the whole table, not by column

Cause: Although it is possible to GRANT update privileges on a column-by-column basis, it is only possible to REVOKE them for an entire table.

Action: Do not identify specific columns. To revoke update privileges for certain columns, use REVOKE for the entire table and GRANT the user privileges for specific columns.

ORA-01751 Invalid dump undo option

Cause: An invalid option is specified in the ALTER DUMP UNDO command.

Action: Correct and reissue the command.

ORA-01752 cannot delete from view without exactly one key-preserved table

Cause: The deleted table either had no key preserved tables, had more than one key-preserved table, or the key-preserved table was an unmerged view or a table from a read-only view.

Action: Redefine the view or delete it from the underlying base tables.

ORA-01753 column definition incompatible with clustered column definition

Cause: When adding a table to a cluster, the definition of the column in the table was inconsistent with the definition of the column in the cluster.

Action: The table cannot be added to the cluster until all cluster column definitions are consistent.

ORA-01754 a table may contain only one column of type LONG

Cause: An attempt was made to add a LONG column to a table which already had a LONG column. Note that even if the LONG column currently in the table has already been marked unused, another LONG column may not be added until the unused columns are dropped.

Action: Remove the LONG column currently in the table by using the ALTER TABLE command.

ORA-01755 Must specify an extent number or block number

Cause: Expecting an extent or block number but something else was specified.

Action: Correct the error and reissue the command.

ORA-01756 quoted string not properly terminated

Cause: A quoted string must be terminated with a single quote mark (').

Action: Insert the closing quote and retry the statement.

ORA-01757 Must specify an object number

Cause: Expecting an object number but something else was specified.

Action: Correct the error and reissue the command.

ORA-01758 table must be empty to add mandatory (NOT NULL) column

Cause: It is not possible to define a new column as NOT NULL if rows already exist in the table being modified.

Action: Retry the statement without the NOT NULL specification.

ORA-01759 user function is incorrectly defined

Cause: A user function has been improperly defined.

Action: Contact Oracle Support Services.

ORA-01760 illegal argument for function

Cause: The argument or arguments specified for the function are not valid in this context.

Action: Check the definition of the function and correct the arguments.

ORA-01761 DML operation does not map to a unique table in the join

Cause: The primary table is the base table against which the update, insert or delete operation is finally being done. For delete either there is no primary table in the join query or there is more than one. For update or insert the columns specified map to more than one base table.

Action: Change the join specification.

ORA-01762 vopdrv: view query block not in FROM

Cause: This is an internal error message not normally issued.

Action: Contact Oracle Support Services.

ORA-01763 update or delete involves outer joined table

Cause: For deletes, the table being deleted from is outer joined to some other table. For updates, either the table being updated is outer- joined to some other table, or some table reachable from the primary table is being outer joined to a table not reachable from the primary table.

Action: Change the join specification.

ORA-01764 new update value of join is not guaranteed to be unique

Cause: A row of a join query table is being updated using a row of a table that is not guaranteed to have exactly one value for the row being updated.

Action: Change the join specification.

ORA-01765 specifying table's owner name is not allowed

Cause: A table or view name was specified with a period (.) or identified with an invalid prefix.

Action: Check that the object is identified correctly and if necessary remove the period from the name.

ORA-01766 dictionary table not allowed in this context

Cause: The name of a data dictionary object was used outside the FROM clause of a SELECT statement. The only operation allowed on a data dictionary object is to SELECT from it.

Action: Restrict operations on data dictionary objects to queries.

ORA-01767 UPDATE ... SET expression must be a subquery

Cause: An attempt was made to use a single expression without a subquery to update a list of columns.

Action: Check the syntax for using subqueries to update data and add the necessary subquery.

ORA-01768 number string too long

Cause: A number entered exceeds the limit of 255 characters, including digits, sign, decimal point, and exponent.

Action: Shorten the number string, perhaps by expressing it in scientific notation, for example, 1.85E9 instead of 1,850,000,000.

ORA-01769 duplicate CLUSTER option specifications

Cause: During a CREATE of a clustered table, the user attempted to specify more than one CLUSTER option.

Action: Remove the extra CLUSTER option.

ORA-01770 CLUSTER option not allowed in CREATE CLUSTER command

Cause: An attempt was made to use the CLUSTER option within a CREATE CLUSTER statement.

Action: Remove the CLUSTER clause and try again.

ORA-01771 illegal option for a clustered table

Cause: During a CREATE or ALTER of a clustered table, the user attempted to enter one or more of the following options: INITRANS, MAXTRANS, PCTFREE, PCTUSED, STORAGE, TABLESPACE, CACHE, NOCACHE. These options may only be specified for the cluster itself.

Action: Remove the illegal option(s).

ORA-01772 Must specify a value for LEVEL

Cause: Expecting the value of LEVEL but something else was specified.

Action: Correct the error and reissue the command.

ORA-01773 may not specify column datatypes in this CREATE TABLE

Cause: Column datatypes were specified in a SELECT statement used to create and load a table directly.

Action: Remove column datatypes. The datatypes of the SELECT list expressions are automatically used as the column datatypes.

ORA-01774 Dump undo option specified more than once

Cause: The same option for ALTER DUMP UNDO was specified twice.

Action: Remove the redundant options and reissue the command.

ORA-01775 looping chain of synonyms

Cause: Through a series of CREATE synonym statements, a synonym was defined that referred to itself. For example, the following definitions are circular:

CREATE SYNONYM s1 for s2 CREATE SYNONYM s2 for s3 CREATE SYNONYM s3 for s1 

Action: Change one synonym definition so that it applies to a base table or view and retry the operation.

ORA-01776 cannot modify more than one base table through a join view

Cause: Columns belonging to more than one underlying table were either inserted into or updated.

Action: Phrase the statement as two or more separate statements.

ORA-01777 WITH GRANT OPTION not allowed in this system

Cause: This version of Oracle does not support the WITH GRANT OPTION.

Action: Remove the WITH GRANT option.

ORA-01778 maximum subquery nesting level exceeded

Cause: An attempt was made to use more than 255 levels of nested subqueries.

Action: Merge some of the subqueries into their containing queries, until there are less than 255 levels of nesting.

ORA-01779 cannot modify a column which maps to a non key-preserved table

Cause: An attempt was made to insert or update columns of a join view which map to a non-key-preserved table.

Action: Modify the underlying base tables directly.

ORA-01780 string literal required

Cause: In a COMMENT statement, the Comment following the keyword IS must be a quoted string literal.

Action: Check that the Comment is a string literal.

ORA-01781 UNRECOVERABLE cannot be specified without AS SELECT

Cause: UNRECOVERABLE was specified in a CREATE TABLE statement without also specifying a populating subquery with an AS clause.

Action: Do not specify UNRECOVERABLE.

ORA-01782 UNRECOVERABLE cannot be specified for a cluster or clustered table

Cause: A CREATE CLUSTER, or clustered CREATE TABLE statement specified UNRECOVERABLE.

Action: Do not specify UNRECOVERABLE.

ORA-01783 only one RECOVERABLE or UNRECOVERABLE clause may be specified

Cause: RECOVERABLE was specified more than once, UNRECOVERABLE was specified more than once, or both RECOVERABLE and UNRECOVERABLE were specified in a CREATE TABLE or CREATE INDEX or ALTER INDEX REBUILD statement.

Action: Remove all but one of the RECOVERABLE or UNRECOVERABLE clauses and reissue the statement.

ORA-01784 RECOVERABLE cannot be specified with database media recovery disabled

Cause: A CREATE TABLE or CREATE INDEX statement specified RECOVERABLE when the database was running in NOARCHIVELOG mode. Since logs are not being archived, they will be overwritten and the object being created cannot be recovered from a backup taken before the object was created.

Action: Do not specify RECOVERABLE, or restart the database with media recovery enabled.

ORA-01785 ORDER BY item must be the number of a SELECT-list expression

Cause: Either an ORDER BY item for a set expression is not a column number, or the ORDER BY item is not the number of a SELECT list column.

Action: The ORDER BY item must be a number between 1 and the number of columns in the SELECT list. Check the column number and retry the statement.

ORA-01786 FOR UPDATE of this query expression is not allowed

Cause: An attempt was made to use a FOR UPDATE clause on the result of a set expression involving GROUP BY, DISTINCT, UNION, INTERSECT, or MINUS.

Action: Check the syntax, remove the FOR UPDATE clause, and retry the statement.

ORA-01787 only one clause allowed per query block

Cause: An attempt was made to use more than one WHERE, GROUP BY, CONNECT BY, or HAVING clause in the query.

Action: Combine the duplicate clauses into a single clause and retry the statement.

ORA-01788 CONNECT BY clause required in this query block

Cause: A START WITH clause was specified without a CONNECT BY clause.

Action: Check the syntax, specify a CONNECT BY clause, and retry the statement.

ORA-01789 query block has incorrect number of result columns

Cause: All of the queries participating in a set expression do not contain the same number of SELECT list columns.

Action: Check that all the queries in the set expression have the same number of SELECT list columns.

ORA-01790 expression must have same datatype as corresponding expression

Cause: A SELECT list item corresponds to a SELECT list item with a different datatype in another query of the same set expression.

Action: Check that all corresponding SELECT list items have the same datatypes. Use the TO_NUMBER, TO_CHAR, and TO_DATE functions to do explicit data conversions.

ORA-01791 not a SELECTed expression

Cause: There is an incorrect ORDER BY item. The query is a SELECT DISTINCT query with an ORDER BY clause. In this context, all ORDER BY items must be constants, SELECT list expressions, or expressions whose operands are constants or SELECT list expressions.

Action: Remove the inappropriate ORDER BY item from the SELECT list and retry the statement.

ORA-01792 maximum number of columns in a table or view is 1000

Cause: An attempt was made to create a table or view with more than 1000 columns, or to add more columns to a table or view which pushes it over the maximum allowable limit of 1000. Note that unused columns in the table are counted toward the 1000 column limit.

Action: If the error is a result of a CREATE command, then reduce the number of columns in the command and resubmit. If the error is a result of an ALTER TABLE command, then there are two options:

• If the table contained unused columns, remove them by executing ALTER TABLE DROP UNUSED COLUMNS before adding new columns.
• Reduce the number of columns in the command and resubmit.

ORA-01793 maximum number of index columns is 32

Cause: While creating an index, more than 32 columns were specified.

Action: Remove some columns from the index definition. If all the columns indexed are required, split them into two indexes.

ORA-01794 maximum number of cluster columns is 32

Cause: More than 32 columns were specified in the cluster key.

Action: Remove some of the columns from the cluster key definition. Consider concatenating multiple character strings into a single column.

ORA-01795 maximum number of expressions in a list is 1000

Cause: More than 254 columns or expressions were specified in a list.

Action: Remove some of the expressions from the list.

ORA-01796 this operator cannot be used with lists

Cause: A relational operator is not allowed in this context. When comparing lists, use only an operator that tests for equivalence, such as =, !=, or IN.

Action: Rephrase the query so that it only compares lists for equivalence. For example, the following clause is invalid:

WHERE (A,B) > ((C,D), (E,F)) 

It may be necessary to compare individual columns separately. For example, to see if A and B are respectively greater than C and D, use WHERE A>B AND C>D instead of WHERE (A,B)>(C,D).

ORA-01797 this operator must be followed by ANY or ALL

Cause: The keyword ANY or ALL was missing.

Action: Check the statement syntax and add ANY or ALL where appropriate.

ORA-01798 missing EXCEPTION keyword

Cause: The EXCEPTION keyword is missing from the ENABLE clause.

Action: Correct the syntax.

ORA-01799 a column may not be outer-joined to a subquery

Cause: expression(+) relop (subquery) is not allowed.

Action: Either remove the (+) or make a view out of the subquery. In V6 and before, the (+) was just ignored in this case.

ORA-01800 a literal in the date format was too large to process

Cause: A literal specified in a date format was too large. If a literal is entered as a date, it must be less than 220 characters long.

Action: Use only literals less than 220 characters long in the date format.

ORA-01801 date format is too long for internal buffer

Cause: The date format string was too long to process. This should occur only if several long literals are specified as part of a date.

Action: Remove long literals from the date format string.

ORA-01802 Julian date is out of range

Cause: An invalid Julian date was entered. Valid Julian dates run from 1 to 3,442,447.

Action: Enter a valid Julian date between 1 and 3,442,447.

ORA-01803 failure in getting date/time

Cause: This is an internal error message that is not likely to occur. It is usually caused by a failure in the system clock.

Action: Investigate the system clock and the process that requested the date or time. If necessary, contact Oracle Support Services.

ORA-01804 failure to initialize timezone information

Cause: The timezone information file was not properly read.

Action: Please contact Oracle Support Services.

ORA-01810 format code appears twice

Cause: A format code was listed twice in a date specification. Each format code may be specified only once in the function TO_DATE.

Action: Remove the duplicate format code from the date specification, then retry the operation.

ORA-01811 Julian date precludes use of day of year

Cause: Both a Julian date and a day of the year were specified in the TO_DATE function. If a Julian date is specified, the day of the year (DDD) may not be specified, as it is contained in the Julian date.

Action: Remove the day of the year or the Julian date from the specification, then retry the operation.

ORA-01812 year may only be specified once

Cause: More than one year format code was listed in a date specification. Only one of the following year format codes may be specified in a date: YYYY, YYY, YY, Y.

Action: Remove all but one year format from the date specification.

ORA-01813 hour may only be specified once

Cause: More than one hour format code was listed in a date specification. Only one of the following hour format codes may be specified in a date: HH, HH12, HH24.

Action: Remove all but one hour format from the date specification.

ORA-01814 AM/PM conflicts with use of A.M./P.M.

Cause: Both types of meridian indicators, AM and PM, were listed in a date specification. If one of the meridian indicator format masks, such as AM or A.M., is specified in the date, the other may not be specified.

Action: Use one meridian indicator format, with or without periods, consistently.

ORA-01815 BC/AD conflicts with use of B.C./A.D.

Cause: Both types of BC/AD indicators were listed in a date specification. If one of the BC/AD indicator format masks, such as BC or B.C., is specified in the date, the other may not be specified.

Action: Use one BC/AD indicator format, with or without periods, consistently.

ORA-01816 month may only be specified once

Cause: More than one month format code was listed in a date specification. Only one of the following month format codes may be specified in a date: MM, MON, MONTH.

Action: Remove all but one month format from the date specification.

ORA-01817 day of week may only be specified once

Cause: More than one day-of-the-week format code was listed in a date specification. Only one of the following day-of-the-week format codes may be specified in a date: D, DY, DAY.

Action: Remove all but one day-of-the-week format from the date specification.

ORA-01818 'HH24' precludes use of meridian indicator

Cause: A date specification contained both a 24-hour time format code and a meridian indicator code. If hours are specified using the 24-hour time format (HH24), a meridian indicator, AM or PM, may not be specified.

Action: Remove the meridian indicator format code, AM/PM or A.M./P.M., or the 24-hour time format code, HH24, from the date specification.

ORA-01819 signed year precludes use of BC/AD

Cause: A date specification contained both a signed year and a B.C./A.D. indicator. If the year is specified with a sign, such as SYYYY, then B.C. or A.D. is implicit in the date and must not be entered.

Action: Remove the B.C./A.D. indicator from the date specification.

ORA-01820 format code cannot appear in date input format

Cause: A date specification contained an invalid format code. Only the following may be specified when entering a date: year, month, day, hours, minutes, seconds, Julian day, A.M./P.M. and B.C./A.D.

Action: Remove the invalid format code from the date specification.

ORA-01821 date format not recognized

Cause: A date specification contained an invalid format code.

Action: Check that only valid date format codes are specified.

ORA-01822 era format code is not valid with this calendar

Cause: An era format code, E or EE, was specified with a calendar which does not use era information.

Action: Retry the operation using a date format mask which does not contain era format codes.

ORA-01830 date format picture ends before converting entire input string

Cause: A valid date format picture included extra data. The first part of the format picture was converted into a valid date, but the remaining data was not required.

Action: Check the specifications for date format pictures and correct the statement.

ORA-01831 year conflicts with Julian date

Cause: The wrong year was specified with a Julian day. If a year is specified with a Julian date, it must be the year in which the Julian date occurs.

Action: Remove the year value from the date specification or enter the correct year for the Julian date.

ORA-01832 day of year conflicts with Julian date

Cause: A Julian date was specified with the day of the year but the day did not correspond to the Julian date. If the day of the year is specified with a Julian date, it must be the same day as the Julian date.

Action: Remove the day of the year value from the date specification or enter the correct day for the Julian date.

ORA-01833 month conflicts with Julian date

Cause: The wrong month was specified with a Julian date. If a month is specified with a Julian date, it must be the month in which the Julian date occurs.

Action: Remove the month value from the date specification or enter the correct month for the Julian date.

ORA-01834 day of month conflicts with Julian date

Cause: A Julian date was specified with the day of the month, but the month day did not correspond to the Julian date. If the day of the month is specified with a Julian date, it must be the same day of the month as the Julian date.

Action: Remove the day of the month value from the date specification or enter the correct day of the month for the Julian date.

ORA-01835 day of week conflicts with Julian date

Cause: A Julian date was specified with the day of the week, but the weekday did not correspond to the Julian date. If the day of the week is specified with a Julian date, it must be the same day of the week as the Julian date.

Action: Remove the day of the week value from the date specification or enter the correct day of the week for the Julian date.

ORA-01836 hour conflicts with seconds in day

Cause: The wrong hour was specified with seconds in the day. If an hour is specified with seconds past midnight (SSSSS), it must be the hour in which the seconds value falls.

Action: Remove the hour value from the date specification or specify the correct hour for the seconds past midnight.

ORA-01837 minutes of hour conflicts with seconds in day

Cause: A date specification contained both minutes of the hour and seconds in the day but the values did not correspond. If both minutes in the hour (MI) and seconds past midnight (SSSSS) are specified, the minutes value must be the minute in which the seconds value will occur.

Action: Remove the minutes value from the date specification or enter the correct minute value for the specified seconds value.

ORA-01838 seconds of minute conflicts with seconds in day

Cause: A date specification contained both seconds of the minute and seconds in the day but the values did not correspond. If both types of seconds are specified, the seconds of the minute value (SS) must be the second in which the seconds past midnight value (SSSSS) will fall.

Action: Remove the seconds of the minute value from the date specification or enter a value that corresponds to the given seconds in the day.

ORA-01839 date not valid for month specified

Cause: The day of the month specified in the date is invalid for the given month. The day of the month (DD) must be between 1 and the number of days in the month.

Action: Enter a valid day of the month for the specified month.

ORA-01840 input value not long enough for date format

Cause: The data to be converted to date format was incomplete; the date format picture was longer than the input data.

Action: Either add more input or shorten the date picture format, then retry the operation.

ORA-01841 (full) year must be between -4713 and +9999, and not be 0

Cause: A date specified a year that is not in the valid date range. A valid date is any date between January 1, 4712 B.C. and December 31, 9999 A.D.

Action: Enter a valid date value between 4712 B.C. and 9999 A.D.

ORA-01842 quarter must be between 1 and 4

Cause: An invalid value was specified for the quarter of the year in a date. The quarter (Q) must be between 1 and 4.

Action: Enter a value for quarter between 1 and 4.

ORA-01843 not a valid month

Cause: A date specified an invalid month. Valid months are: January-December, for format code MONTH, and Jan-Dec, for format code MON.

Action: Enter a valid month value in the correct format.

ORA-01844 week of year must be between 1 and 52

Cause: An invalid value was specified for the week of the year in a date. Week of the year (WW) must be between 1 and 52.

Action: Enter a week of the year value between 1 and 52.

ORA-01845 week of month must be between 1 and 5

Cause: An invalid value was specified for the week of the month in a date. Week of the month (W) must be between 1 and 5.

Action: Enter a week of the month value between 1 and 5.

ORA-01846 not a valid day of the week

Cause: A date specified an invalid day of the week. Valid days are:

• Monday-Sunday, for format code DAY
• Mon-Sun, for format code DY
• 1-7, for format code D

Action: Enter a valid day of the week value in the correct format.

ORA-01847 day of month must be between 1 and last day of month

Cause: The day of the month listed in a date is invalid for the specified month. The day of the month (DD) must be between 1 and the number of days in that month.

Action: Enter a valid day value for the specified month.

ORA-01848 day of year must be between 1 and 365 (366 for leap year)

Cause: An invalid day of the year was specified in a date. Day of the year (DDD) must be between 1 and 365 for a non-leap year or 1 and 366 for a leap year.

Action: Enter a day of the year value between 1 and 365 (or 366).

ORA-01849 hour must be between 1 and 12

Cause: An invalid hour was specified for a date using the 12-hour time format. If a 12-hour format code (HH or HH12) is used, the specified hour must be between 1 and 12.

Action: Enter an hour value between 1 and 12.

ORA-01850 hour must be between 0 and 23

Cause: An invalid hour was specified for a date using the 24-hour time format. If the 24-hour format code (HH24) is listed, the specified hour must be between 0 and 23.

Action: Enter an hour value between 0 and 23.

ORA-01851 minutes must be between 0 and 59

Cause: An invalid minute value was specified in a date. Minutes must be between 0 and 59.

Action: Enter a minute value between 0 and 59.

ORA-01852 seconds must be between 0 and 59

Cause: An invalid seconds value was specified in a date. Seconds must be between 0 and 59 if the seconds format code (SS) is used.

Action: Enter a seconds value between 0 and 59.

ORA-01853 seconds in day must be between 0 and 86399

Cause: An invalid value for seconds in the day was specified in a date. Seconds must be between 0 and 86399 if the seconds past midnight format code (SSSSS) is used.

Action: Specify a seconds value between 0 and 86399.

ORA-01854 julian date must be between 1 and 5373484

Cause: An invalid Julian date was entered.

Action: Enter a valid Julian date between 1 and 5373484.

ORA-01855 AM/A.M. or PM/P.M. required

Cause: A date specification contained a meridian indicator format code but a valid meridian indicator was not specified. If a meridian indicator code, A.M./P.M. or AM/PM, is included in a date format, the date must include a valid meridian indicator.

Action: Specify the meridian indicator in the correct format, A.M./AM or P.M./PM.

ORA-01856 BC/B.C. or AD/A.D. required

Cause: A date specification contained a BC/AD format code but a valid BC/AD indicator was not specified. If one of the BC/AD format codes, BC/AD or B.C./A.D., is specified in a date format, the date must include BC/B.C. or AD/A.D.

Action: Specify the BC/AD indicator in the date using the correct format.

ORA-01857 not a valid time zone

Cause: An incorrect time zone code was specified for the NEW_TIME function.

Action: Correct the invalid time zone code, then retry the operation.

ORA-01858 a non-numeric character was found where a numeric was expected

Cause: The input data to be converted using a date format model was incorrect. The input data did not contain a number where a number was required by the format model.

Action: Fix the input data or the date format model to make sure the elements match in number and type. Then retry the operation.

ORA-01859 a non-alphabetic character was found where an alphabetic was expected

Cause: The input data to be converted using a date format model was incorrect. The input data did not contain a letter where a letter was required by the format model.

Action: Fix the input data or the date format model to make sure the elements match in number and type. Then retry the operation.

ORA-01860 week of year must be between 1 and 53

Cause: A week number outside the range 1 to 53 was specified.

Action: Use only a value within the valid range for the week number.

ORA-01861 literal does not match format string

Cause: Literals in the input must be the same length as literals in the format string (with the exception of leading white space). If the "FX" modifier has been toggled on, the literal must match exactly, with no extra white space.

Action: Correct the format string to match the literal.

ORA-01862 the numeric value does not match the length of the format item

Cause: When the FX and FM format codes are specified for an input date, then the number of digits must be exactly the number specified by the format code. For example, 9 will not match the format specifier DD but 09 will.

Action: Correct the input date or turn off the FX or FM format specifier in the format string.

ORA-01863 the year is not supported for the current calendar

Cause: The year is not supported for the current calendar.

Action: Check the documentation to find out what years are supported for the current calendar.

ORA-01864 the date is out of range for the current calendar

Cause: Your calendar does not extend to the specified date.

Action: Specify a date which is legal for this calendar.

ORA-01865 not a valid era

Cause: Era input does not match a known era.

Action: Provide a valid era on input.

ORA-01866 the datetime class is invalid

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-01867 the interval is invalid

Cause: The character string you specified is not a valid interval.

Action: Specify a valid interval.

ORA-01868 the leading precision of the interval is too small

Cause: The leading precision of the interval is too small to store the specified interval.

Action: Increase the leading precision of the interval or specify an interval with a smaller leading precision.

ORA-01869 reserved for future use

Cause: Not an error.

Action: No action required.

ORA-01870 the intervals or datetimes are not mutually comparable

Cause: The intervals or datetimes are not mutually comparable.

Action: Specify a pair of intervals or datetimes that are mutually comparable.

ORA-01871 the number of seconds must be less than 60

Cause: The number of seconds specified was greater than 59.

Action: Specify a value for seconds that is 59 or smaller.

ORA-01872 reserved for future use

Cause: Not an error.

Action: No action required.

ORA-01873 the leading precision of the interval is too small

Cause: The leading precision of the interval is too small to store the specified interval.

Action: Increase the leading precision of the interval or specify an interval with a smaller leading precision.

ORA-01874 time zone hour must be between -12 and 13

Cause: The time zone hour specified was not in the valid range.

Action: Specify a time zone hour between -12 and 13.

ORA-01875 time zone minute must be between -59 and 59

Cause: The time zone minute specified was not in the valid range.

Action: Specify a time zone minute between -59 and 59.

ORA-01876 year must be at least -4713

Cause: The specified year was not in range.

Action: Specify a year that is greater than or equal to -4713.

ORA-01877 string is too long for internal buffer

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-01878 specified field not found in datetime or interval

Cause: The specified field was not found in the datetime or interval.

Action: Make sure that the specified field is in the datetime or interval.

ORA-01879 the hh25 field must be between 0 and 24

Cause: The specified hh25 field was not in the valid range.

Action: Specify an hh25 field between 0 and 24.

ORA-01880 the fractional seconds must be between 0 and 999999999

Cause: The specified fractional seconds were not in the valid range.

Action: Specify a value for fractional seconds between 0 and 999999999.

ORA-01881 timezone region id number is invalid

Cause: The region id referenced an invalid region.

Action: Please contact Oracle Support Services.

ORA-01882 timezone region string not found

Cause: The specified region name was not found.

Action: Please contact Oracle Support Services.

ORA-01883 overlap was disabled during a region transition

Cause: The region was changing state and the overlap flag was disabled.

Action: Please contact Oracle Support Services.

ORA-01890 NLS error detected

Cause: An NLS error was detected.

Action: Look for additional error messages and take appropriate action. If there are no additional errors, contact Oracle Support Services.

ORA-01891 Datetime/Interval internal error

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-01898 too many precision specifiers

Cause: While trying to truncate or round dates, extra data was found in the date format picture.

Action: Check the syntax of the date format picture and retry.

ORA-01899 bad precision specifier

Cause: An invalid precision code was specified in a date.

Action: Enter a valid precision code in the date format. Valid precision types are: century, year, month, day, Julian date, hours, minutes, and seconds.

ORA-01900 LOGFILE keyword expected

Cause: A keyword is missing.

Action: Supply the missing keyword.

ORA-01901 ROLLBACK keyword expected

Cause: A keyword is missing.

Action: Supply the missing keyword.

ORA-01902 SEGMENT keyword expected

Cause: A keyword is missing.

Action: Supply the missing keyword.

ORA-01903 EVENTS keyword expected

Cause: A keyword is missing.

Action: Supply the missing keyword.

ORA-01904 DATAFILE keyword expected

Cause: A keyword is missing.

Action: Supply the missing keyword.

ORA-01905 STORAGE keyword expected

Cause: A keyword is missing.

Action: Supply the missing keyword.

ORA-01906 BACKUP keyword expected

Cause: A keyword is missing.

Action: Supply the missing keyword.

ORA-01907 TABLESPACE keyword expected

Cause: A keyword is missing.

Action: Supply the missing keyword.

ORA-01908 EXISTS keyword expected

Cause: A keyword is missing.

Action: Supply the missing keyword.

ORA-01909 REUSE keyword expected

Cause: A keyword is missing.

Action: Supply the missing keyword.

ORA-01910 TABLES keyword expected

Cause: A keyword is missing.

Action: Supply the missing keyword.

ORA-01911 CONTENTS keyword expected

Cause: A keyword is missing.

Action: Supply the missing keyword.

ORA-01912 ROW keyword expected

Cause: A keyword is missing.

Action: Supply the missing keyword.

ORA-01913 EXCLUSIVE keyword expected

Cause: A keyword is missing.

Action: Supply the missing keyword.

ORA-01914 invalid auditing option for sequence numbers

Cause: AUDIT or NOAUDIT on a sequence number specifies an auditing option that is not legal for sequence numbers.

Action: The following options may not be used for sequence numbers and should be removed: COMMENT, DELETE, INDEX, INSERT, LOCK, RENAME, UPDATE, REFERENCES, EXECUTE.

ORA-01915 invalid auditing option for views

Cause: AUDIT or NOAUDIT on a view specifies an auditing option that is not legal for views.

Action: The following options may not be used for views and should be removed: ALTER, INDEX, REFERENCES, EXECUTE.

ORA-01916 keyword ONLINE, OFFLINE, RESIZE, AUTOEXTEND or END/DROP expected

Cause: An expected keyword was not used for DATAFILE/TEMPFILE clause

Action: Use correct syntax.

ORA-01917 user or role 'string' does not exist

Cause: There is not a user or role by that name.

Action: Re-specify the name.

ORA-01918 user 'string' does not exist

Cause: User does not exist in the system.

Action: Verify the user name is correct.

ORA-01919 role 'string' does not exist

Cause: Role by that name does not exist.

Action: Verify you are using the correct role name.

ORA-01920 user name 'string' conflicts with another user or role name

Cause: There is already a user or role with that name.

Action: Specify a different user name.

ORA-01921 role name 'string' conflicts with another user or role name

Cause: There is already a user or role with that name.

Action: Specify a different role name.

ORA-01922 CASCADE must be specified to drop 'string'

Cause: Cascade is required to remove this user from the system. The user own's object which will need to be dropped.

Action: Specify cascade.

ORA-01923 CASCADE aborted, objects locked by another user

Cause: Cannot drop the user's objects; someone has them locked.

Action: Use the lock monitor to determine who has the objects locked.

ORA-01924 role 'string' not granted or does not exist

Cause: Set role can only be performed with roles granted directly to your account (for example, a sub-role cannot be enabled).

Action: Do not try to set the role.

ORA-01925 maximum of string enabled roles exceeded

Cause: The initialization parameter MAX_ENABLED_ROLES has been exceeded.

Action: Increase MAX_ENABLED_ROLES and warm start the database.

ORA-01926 cannot GRANT to a role WITH GRANT OPTION

Cause: Role cannot have a privilege with the grant option.

Action: Perform the grant without the grant option.

ORA-01927 cannot REVOKE privileges you did not grant

Cause: You can only revoke privileges you granted.

Action: Do not revoke these privileges.

ORA-01928 GRANT option not granted for all privileges

Cause: In order to grant a privilege, you must first have the privilege with the grant option.

Action: Obtain the privilege with the grant option and try again.

ORA-01929 no privileges to GRANT

Cause: "ALL" was specified but the user does not have any privileges with the grant option.

Action: Do not grant privileges on that object.

ORA-01930 auditing the object is not supported

Cause: AUDIT or NOAUDIT was specified for an object that cannot be audited.

Action: Do not attempt to AUDIT the object.

ORA-01931 cannot grant string to a role

Cause: UNLIMITED TABLESPACE, REFERENCES, INDEX, SYSDBA or SYSOPER privilege cannot be granted to a role.

Action: Grant privilege directly to the user.

ORA-01932 ADMIN option not granted for role 'string'

Cause: The operation requires the ADMIN option on the role.

Action: Obtain the grant option and retry.

ORA-01933 cannot create a stored object using privileges from a role

Cause: An attempt was made to create a stored object using privileges from a role. Stored objects cannot use privileges from roles.

Action: Grant the privileges required to the user directly.

ORA-01934 circular role grant detected

Cause: Roles cannot be granted circularly. Also, a role cannot be granted to itself.

Action: Do not perform the grant.

ORA-01935 missing user or role name

Cause: A user or role name was expected.

Action: Specify a user or role name.

ORA-01936 cannot specify owner when creating users or roles

Cause: Users and roles do not have owners.

Action: Do not specify an owner.

ORA-01937 missing or invalid role name

Cause: A valid role name was expected.

Action: Specify a valid role name.

ORA-01938 IDENTIFIED BY must be specified for CREATE USER

Cause: Cannot create a user without specifying a password or IDENTIFIED EXTERNALLY.

Action: Specify one of the password clauses.

ORA-01939 only the ADMIN OPTION can be specified

Cause: System privileges and Roles can only be granted with the ADMIN option. The grant option cannot be used with these privileges.

Action: Specify the ADMIN option.

ORA-01940 cannot drop a user that is currently connected

Cause: Attempt was made to drop a user that is currently logged in.

Action: Make sure user is logged off, then repeat command.

ORA-01941 SEQUENCE keyword expected

Cause: A keyword is missing.

Action: Supply the missing keyword.

ORA-01942 IDENTIFIED BY and EXTERNALLY cannot both be specified

Cause: A user cannot be specified to have and not have a password.

Action: Specify only one of the options.

ORA-01943 IDENTIFIED BY already specified

Cause: The IDENTIFIED clause has been given twice.

Action: Use only one IDENTIFIED BY clause.

ORA-01944 IDENTIFIED EXTERNALLY already specified

Cause: The IDENTIFIED EXTERNALLY clause has been given twice.

Action: Use only one IDENTIFIED clause.

ORA-01945 DEFAULT ROLE[S] already specified

Cause: The DEFAULT ROLES clause has been given twice.

Action: Use only one DEFAULT ROLE clause.

ORA-01946 DEFAULT TABLESPACE already specified

Cause: The DEFAULT TABLESPACE clause has been given twice.

Action: Use only one DEFAULT TABLESPACE clause.

ORA-01947 TEMPORARY TABLESPACE already specified

Cause: The TEMPORARY TABLESPACE clause has been given twice.

Action: Use only one TEMPORARY TABLESPACE clause.

ORA-01948 identifier's name length (string) exceeds maximum (string)

Cause: A name has been specified that is too long. For example, DBMS_SESSION.IS_ROLE_ENABLED() specifies that is too long.

Action: Change the application or command to use a correct identifier.

ORA-01949 ROLE keyword expected

Cause: The ROLE keyword is required here.

Action: Specify the ROLE keyword.

ORA-01950 no privileges on tablespace 'string'

Cause: User does not have privileges to allocate an extent in the specified tablespace.

Action: Grant the user the appropriate system privileges or grant the user space resource on the tablespace.

ORA-01951 ROLE 'string' not granted to 'string'

Cause: The role you tried to revoke was not granted to the user.

Action: Do not try to revoke a privilege which is not granted.

ORA-01952 system privileges not granted to 'string'

Cause: A system privilege you tried to revoke was not granted to the user.

Action: Make sure the privileges you are trying to revoke are granted.

ORA-01953 command no longer valid, see ALTER USER

Cause: The syntax for assigning quotas on tablespaces has changed. The ALTER USER command is now used to perform the functionality.

Action: Use the ALTER USER command instead.

ORA-01954 DEFAULT ROLE clause not valid for CREATE USER

Cause: Default roles cannot be specified for create user.

Action: Grant and alter the user's default roles after creating the user.

ORA-01955 DEFAULT ROLE 'string' not granted to user

Cause: The user being altered does not have the specified role granted directly to the user. Note, sub-roles cannot be used in the DEFAULT ROLE clause.

Action: Grant the role to the user.

ORA-01956 invalid command when OS_ROLES are being used

Cause: This command cannot be used when the initialization parameter OS_ROLES is TRUE.

Action: Grant the role to the user in the operating system.

ORA-01957 Keyword MIN or MAX expected, not found

Cause: The keyword MIN or MAX was expected as an argument.

Action: Enter the keyword MIN or MAX and retry the operation.

ORA-01958 Must supply an integer for the LAYER option

Cause: An item other than an integer was entered for the LAYER option.

Action: Enter an integer for the LAYER option and retry the operation.

ORA-01959 Must supply an integer for the OPCODE option

Cause: An item other than an integer was entered for the OPCODE option. Thevalue in ALTER SYSTEM DUMP ... OPCODE value must be an integer.

Action: Enter an integer for the OPCODE option and retry the operation.

For more information on the OPCODE option, see the Oracle9i SQL Reference.

ORA-01960 Invalid dump logfile option

Cause: An invalid option was entered for the ALTER SYSTEM DUMP LOGFILEoption command.

Action: For a list of valid options for DUMP LOGFILE, see theOracle9i SQL Reference.

ORA-01961 invalid dump option

Cause: An invalid option was entered for the ALTER SYSTEM DUMP statement.

Action: Enter a valid option for ALTER SYSTEM DUMP. Examples of valid options areLOGFILE and UNDO. For more information on the DUMP option, see theOracle9i SQL Reference.

ORA-01962 Must specify a file number or log sequence number

Cause: An invalid file number or log sequence number was specified.

Action: Enter a valid file number or log sequence number and retry the operation. For more information on valid file and log sequence numbers, see theOracle9i SQL Reference.

ORA-01963 Must specify a block number

Cause: An invalid block number was specified.

Action: Enter a valid block number and retry the operation. For more information on valid block numbers, see theOracle9i SQL Reference.

ORA-01964 Must specify a time for the TIME option

Cause: A value was entered for the TIME option that could not be interpreted as a date.

Action: Enter a valid date. For more information on the TIME option, see theOracle9i SQL Reference.

ORA-01965 Must specify a PERIOD

Cause: A period is missing between the file number and the block number.

Action: Enter a period between the file number and the block number, then retry the operation. For more information on file numbers and block numbers, see theOracle9i SQL Reference.

ORA-01967 invalid option for CREATE CONTROLFILE

Cause: An invalid CREATE CONTROLFILE option is present.

Action: Specify only valid CREATE CONTROLFILE options.

ORA-01968 Only specify RESETLOGS or NORESETLOGS once

Cause: The keyword RESETLOGS or NORESETLOGS has appeared more than once.

Action: Be sure to specify RESETLOGS or NORESETLOGS exactly once.

ORA-01969 You must specify RESETLOGS or NORESETLOGS

Cause: Missing a RESETLOGS or a NORESETLOGS.

Action: Be sure to specify RESETLOGS or NORESETLOGS exactly once.

ORA-01970 You must specify a database name for CREATE CONTROLFILE

Cause: Missing a database name.

Action: Retype CREATE CONTROLFILE command with the DATABASE keyword.

ORA-01971 Illegal ALTER TRACING option

Cause: An invalid ALTER TRACING option is present.

Action: Specify only valid ALTER TRACING options. Examples of valid options are ENABLE and DISABLE. For more information, see theOracle9i SQL Reference.

ORA-01972 Must specify a string for ALTER TRACING ENABLE or DISABLE

Cause: Something other than a valid identifier was specified for ALTER TRACING ENABLE or DISABLE.

Action: Specify a valid identifier for ALTER TRACING ENABLE or DISABLE and retry the operation. For more information on valid identifiers, see theOracle9i SQL Reference.

ORA-01973 Missing change number

Cause: Keyword CHANGE found but change number not specified.

Action: Fix the command line and resubmit.

ORA-01974 Illegal archive option

Cause: An invalid option to the ALTER SYSTEM ARCHIVE command was specified.

Action: Check the syntax of the command and retry it.

ORA-01975 Illegal character in change number string

Cause: An invalid change number was supplied.

Action: Resubmit the command with a valid change number.

ORA-01976 Missing change number

Cause: A change number was required, but not supplied.

Action: Check the syntax of the command, supply a change number where needed, then retry the command.

ORA-01977 Missing thread number

Cause: Keyword THREAD found but thread number not specified.

Action: Fix the command line and resubmit.

ORA-01978 Missing sequence number

Cause: Keyword SEQUENCE found but sequence number not specified.

Action: Fix the command line and resubmit.

ORA-01979 missing or invalid password for role 'string'

Cause: An attempt was made to enable a role without giving the proper password.

Action: Use the IDENTIFIED BY clause in SET ROLE to specify the correct password.

ORA-01980 error during OS ROLE initialization

Cause: An operating system error occurred while loading a users OS ROLES.

Action: Check the operating system error.

ORA-01981 CASCADE CONSTRAINTS must be specified to perform this revoke

Cause: During this revoke some foreign key constraints will be removed. In order to perform this automatically, CASCADE CONSTRAINTS must be specified.

Action: Remove the constraints or specify CASCADE CONSTRAINTS.

ORA-01982 invalid auditing option for tables

Cause: AUDIT or NOAUDIT on a table specifies an auditing option that is not legal for tables.

Action: The following options may not be used for tables and should be removed: REFERENCES, EXECUTE.

ORA-01983 invalid auditing option for DEFAULT

Cause: AUDIT or NOAUDIT on a DEFAULT specifies an auditing option that is not legal for DEFAULT.

Action: The following options may not be used for DEFAULT and should be removed: REFERENCES.

ORA-01984 invalid auditing option for procedures/packages/functions

Cause: AUDIT or NOAUDIT on a DEFAULT specifies an auditing option that is not legal for procedures, packages, or functions.

Action: The following options may not be used for procedures, packages, and functions and should be removed: all but EXECUTE.

ORA-01985 cannot create user as LICENSE_MAX_USERS parameter exceeded

Cause: Maximum users in the database license limit exceeded.

Action: Increase license limit.

ORA-01986 invalid option for OPTIMIZER_GOAL

Cause: An invalid OPTIMIZER_GOAL option is present.

Action: Check the syntax for OPTIMIZER_GOAL, specify a valid option and re-execute the statement.

ORA-01987 client os username is too long

Cause: A client's operating system username is too long for the operating system logon to succeed.

Action: Use a shorter operating system username.

ORA-01988 remote os logon is not allowed

Cause: Remote operating system login attempted when not allowed.

Action: Use a local client, or use the REMOTE_OS_AUTHENT system parameter to turn on remote operating system logon.

ORA-01989 role 'string' not authorized by operating system

Cause: The operating system role does not exist, is not granted to you, or you did not provide the correct password.

Action: Re-attempt the SET ROLE with a valid operating system role and password, if necessary.

ORA-01990 error opening password file 'string'

Cause: An attempt to open the specified password file failed because of one of the following errors:

• An operating system error occurred.
• ORAPWD is already running, so the password file is locked.

The environment variables ORA_sid_PWFILE and ORA_PWFILE are not set.

Action: Check for the above causes and correct as necessary.

ORA-01991 invalid password file 'string'

Cause: The specified password file name is invalid.

Action: Specify a correct password file name.

ORA-01992 error closing password file 'string'

Cause: The password file could not be closed because of an operating system error or because an authentication action failed.

Action: Check for the above causes and correct as necessary.

ORA-01993 error writing password file 'string'

Cause: The password file could not be written to because of an operating system error or because an authentication action failed.

Action: Check for the above causes and correct as necessary.

ORA-01994 GRANT failed: cannot add users to shared password file

Cause: A grant failed because a user could not be added to the password file. This is because the value of the REMOTE_LOGIN_PASSWORDFILE initialization parameter is set to SHARED.

Action: To add a user to the password file, shut down the database, change the REMOTE_LOGIN_PASSWORDFILE initialization parameter to EXCLUSIVE, and restart the database.

ORA-01995 error reading password file 'string'

Cause: An operating system error occurred when trying to read the password file.

Action: Fix the operating system error.

ORA-01996 GRANT failed: password file 'string' is full

Cause: The grant failed when a user could not be added to the password file, because all available slots in it were used already.

Action: Either create a larger password file or free up slots in the password file by revoking the SYSOPER and SYSDBA privileges from some of the remote users. You can determine which remote users are valid and their privileges by issuing the following query in SQL*DBA:

SELECT * FROM V$REMOTE_USERS;

ORA-01997 GRANT failed: user 'string' is identified externally

Cause: You cannot grant the SYSOPER or SYSDBA privilege to a user created with the IDENTIFIED EXTERNALLY clause.

Action: If you wish to grant the user the SYSOPER or SYSDBA privileges, drop and re-create the user without the IDENTIFIED EXTERNALLY clause.

ORA-01998 REVOKE failed: user SYS always has SYSOPER and SYSDBA

Cause: You attempted to revoke one of the necessary privileges, SYSOPER or SYSDBA, from user SYS. These privileges cannot be revoked.

Action: Do not attempt this operation.

ORA-01999 password file mode has changed from 'string' to 'string'

Cause: Another instance has started with the FORCE_PASSWORD_FILEMODE initialization parameter, which is incompatible with the startup mode of your instance.

Action: Shut down your instance and start up later when the password file changes are completed for the other instance.

ORA-02000 missing string keyword

Cause: The statement entered requires the missing keyword.

Action: Use the specified keyword.

ORA-02001 user SYS is not permitted to create indexes with freelist groups

Cause: An attempt was made to create an index while running with SYS authorization.

Action: Indexes cannot be created with SYS authorization. Either do not create the index or switch to USER authorization.

ORA-02002 error while writing to audit trail

Cause: The auditing facility is unable to write to the AUDIT_TRAIL table. If this error occurs, SQL statements that are currently being audited may also fail. This error will occur if the SYSTEM tablespace runs out of disk space.

Action: Add space to the SYSTEM tablespace or delete rows from the AUDIT_TRAIL table. If these operations fail or do not eliminate the problem, shut down and restart Oracle with auditing disabled. This is done by setting the initialization parameter AUDIT_TRAIL to FALSE.

ORA-02003 invalid USERENV parameter

Cause: An invalid parameter was specified for the USERENV function.

Action: Specify one of the allowable parameters TERMINAL, SESSIONID, ENTRYID, or NLS_LANG.

ORA-02004 security violation

Cause: A user is attempting to perform an operation without the proper permission, and this fact is being recorded in the AUDIT_TRAIL table. This message only appears in the AUDIT_TRAIL table's return code column.

Action: For auditing information only; no action required.

ORA-02005 implicit (-1) length not valid for this bind or define datatype

Cause: A negative length for the define variable was passed to a define function.

Action: An explicit, non-negative, length parameter must be passed.

ORA-02006 invalid packed decimal format string

Cause: A packed decimal datatype was passed to a bind or define function, and the format string parameter was either not present or invalid.

Action: A valid format string parameter must be passed for a packed decimal variable. Check the programming manual for the definition of a packed decimal format string.

ORA-02007 can't use ALLOCATE or DEALLOCATE options with REBUILD

Cause: Allocate or deallocate storage and rebuild index are not compatible.

Action: Choose one or the other.

ORA-02008 non-zero scale specified for nonnumeric column

Cause: A scale factor was specified for a bind or define of a non-numeric variable.

Action: Set the scale factor to zero, then retry the operation.

ORA-02009 the size specified for a file must not be zero

Cause: A value of zero was specified in a SIZE or RESIZE clause of a file specification.

Action: Use correct syntax, or, if allowed, omit the SIZE or RESIZE clause.

ORA-02010 missing host connect string

Cause: A quoted character string does not follow the keyword USING in the USING clause of a CREATE DATABASE LINK statement.

Action: Specify the host connect string, then retry the operation.

ORA-02011 duplicate database link name

Cause: The database link name specified in a CREATE DATABASE LINK statement already exists.

Action: Either specify a new name or drop the existing link.

ORA-02012 missing USING keyword

Cause: The keyword USING does not follow the CONNECT TO clause in a CREATE DATABASE LINK statement.

Action: Specify the USING clause after the CONNECT TO clause.

ORA-02013 missing CONNECT keyword

Cause: The keyword CONNECT does not follow the database link name in a CREATE DATABASE LINK statement.

Action: Specify the CONNECT clause after the database link name.

ORA-02014 cannot select FOR UPDATE from view with DISTINCT, GROUP BY, etc.

Cause: An attempt was made to SELECT... FOR UPDATE from a view whose defining SELECT statement uses at least one of the following constructs in its outer block: outer join, GROUP BY clause, aggregate functions, SELECT DISTINCT, CONNECT BY clause, or set operation, UNION, INTERSECT, or MINUS.

Action: Do not use SELECT... FOR UPDATE on this view.

ORA-02015 cannot select FOR UPDATE from remote table

Cause: An attempt was made to SELECT... FOR UPDATE from a table in a remote database.

Action: It is not currently possible to SELECT... FOR UPDATE from a table in a remote database. Instead, log in or connect directly to the remote database before entering a SELECT... FOR UPDATE on its tables.

ORA-02016 cannot use a subquery in a START WITH on a remote database

Cause: An attempt was made to use a subquery in a START WITH clause. Such a subquery is not currently permitted if the table in the FROM clause of the tree query is in a remote database.

Action: It is necessary to connect directly to the remote database before using a subquery in the START WITH clause.

ORA-02017: integer value required

Cause: The specified value must be an integer.

Action: Specify an appropriate integer value, then retry the operation.

ORA-02018 database link of same name has an open connection

Cause: The user is currently connected to a PUBLIC database link with the same name as the database link name specified in a CREATE or DROP DATABASE LINK statement.

Action: Close the cursors that use the PUBLIC database link.

ORA-02019 connection description for remote database not found

Cause: An attempt was made to connect or log in to a remote database using a connection description that could not be found.

Action: Specify an existing database link. Query the data dictionary to see all existing database links. See your operating system-specific Net8 documentation for valid connection descriptors.

ORA-02020 too many database links in use

Cause: The current session has exceeded the INIT.ORA OPEN_LINKS maximum.

Action: Increase the OPEN_LINKS limit, or free up some open links by committing or rolling back the transaction and canceling open cursors that reference remote databases.

ORA-02021 DDL operations are not allowed on a remote database

Cause: An attempt was made to use a DDL operation on a remote database. For example, "CREATE TABLE tablename@remotedbname...".

Action: To alter the remote database structure, you must connect to the remote database with the appropriate privileges.

ORA-02022 remote statement has unoptimized view with remote object

Cause: The local view is unoptimized and contains references to objects at the remote database and the statement must be executed at the remote database.

Action: Create a similar view on the remote database and modify the violating view in the SQL statement with the new view@remote.

ORA-02023 START WITH or CONNECT BY predicate cannot be evaluated by remote data base

Cause: The statement contains a tree query on a remote database, and the tree query's START WITH or CONNECT BY predicate contains a term that cannot be evaluated at the remote database. Such terms include calls to user functions, calls to USERENV, and references to ROWID.

Action: Remove the disallowed term, directly connect, or log on to the remote database.

ORA-02024 database link not found

Cause: Database link to be dropped is not found in dictionary.

Action: Correct the database link name.

ORA-02025 all tables in the SQL statement must be at the remote database

Cause: A SQL statement referenced tables from multiple databases, and one or more of the remote databases are not Oracle Servers.

Action: Remote updates can be performed only if all databases in the SQL statement are Oracle Servers. Update the earlier version databases in a separate statement.

ORA-02026 missing LINK keyword

Cause: A keyword is missing.

Action: Supply the missing keyword.

ORA-02027 multi-row UPDATE of LONG column is not supported

Cause: A bind variable with length greater than 4000 bytes is being used to update a column, and the update statement updates more than one row.

Action: You may only update a single row with such a bind variable.

ORA-02028 fetching an exact number of rows is not supported by the server

Cause: The server does not support UPIALL, so the fetch of an exact number of rows cannot be emulated on the user side.

Action: Connect to a valid server or do not use an exact fetch.

ORA-02029 missing FILE keyword

Cause: A keyword is missing.

Action: Supply the missing keyword.

ORA-02030 can only select from fixed tables/views

Cause: An attempt is being made to perform an operation other than a retrieval from a fixed table/view.

Action: You may only select rows from fixed tables/views.

ORA-02031 no ROWID for fixed tables or for external-organized tables

Cause: An attempt was made to access rowid from a fixed table or from an external-organized table.

Action: Do not access ROWID from a fixed table or from an external-organized table.

ORA-02032 clustered tables cannot be used before the cluster index is built

Cause: User attempted to perform a DML statement on a clustered table for which no cluster index has yet been created.

Action: Create the cluster index.

ORA-02033 a cluster index for this cluster already exists

Cause: A cluster index already exists for the cluster.

Action: No action required.

ORA-02034 speed bind not permitted

Cause: Speed bind not allowed with supplied bind variables. Trapped internally by the system.

Action: No action required.

ORA-02035 illegal bundled operation combination

Cause: User requested that the UPI bundled execution call perform an illegal combination of operations.

Action: Use a legal combination of operations and retry.

ORA-02036 too many variables to describe with automatic cursor open

Cause: UPI-bundled execution call tried to perform automatic cursor open and close on a describe operation. There were too many SELECT list items or bind variables to do this.

Action: Open and close cursor explicitly.

ORA-02037 uninitialized speed bind storage

Cause: An attempt was made to perform a speed-execution call on a SQL statement containing host variables without first performing a speed-bind call.

Action: Perform a speed-bind call before performing a speed-execution call.

ORA-02038 define is not allowed for array type

Cause: A user attempted to define a select list variable of type "array". Arrays may serve only as host bind variables.

Action: Correct the offending code.

ORA-02039 bind by value is not allowed for array type

Cause: User attempted to bind an array host variable by value. Arrays may be bound only by reference.

Action: Correct the offending code.

ORA-02040 remote database string does not support two-phase commit

Cause: A distributed update of more than one database was attempted, but the named database does not support the prepare phase of the two-phase commit, as determined by its logon transaction traits. The transaction was rolled back.

Action: Do not attempt to update the named database, unless it is the only database updated in the transaction. Distributed updates of more than one database in a single transaction can be performed only if all databases support the two-phase commit mechanism.

ORA-02041 client database did not begin a transaction

Cause: An update occurred at a coordinated database without the coordinator beginning a distributed transaction. This may happen if a stored procedure commits and then performs updates, and the stored procedure is invoked remotely. It could also happen if an external transaction monitor violates the XA protocol.

Action: If the cause is the former, check that any commit is not followed by an update.

ORA-02042 too many distributed transactions

Cause: The distributed transaction table is full because too many distributed transactions are active.

Action: Increase the DISTRIBUTED_TRANSACTIONS parameter in the initialization parameter file, shut down and restart Oracle, or run fewer transactions. If it is certain there are not too many concurrent distributed transactions, this may be an internal error. In this case, contact Oracle Support Services. Shutting down and restarting the instance could be a workaround.

ORA-02043 must end current transaction before executing string

Cause: A transaction was in progress and one of the following commands was issued:

• COMMIT FORCE
• ROLLBACK FORCE
• ALTER SYSTEM ENABLE DISTRIBUTED RECOVERY in single process mode

Action: COMMIT or ROLLBACK the current transaction and retry the command.

ORA-02044 transaction manager login denied: transaction in progress

Cause: A remote transaction manager tried to log in while a distributed transaction is in progress. A protocol error occurred in the remote transaction manager.

Action: End the current transaction.

ORA-02045 too many local sessions participating in global transaction

Cause: There are too many sessions at this site to accommodate this transaction.

Action: Use an existing database link so that another session need not be created at the remote site.

ORA-02046 distributed transaction already begun

Cause: This is an internal error not normally encountered. A server session received a BEGIN_TRAN remote procedure call before finishing with a previous distributed transaction.

Action: Contact Oracle Support Services.

ORA-02047 cannot join the distributed transaction in progress

Cause: This can happen only when attempting to update an Oracle Version 6 and an Oracle7 database in the same transaction, because either

• A transaction is in progress against a remote database that does not support two-phase commit.
• Updates are pending and an attempt was made to update a different database that does not support two-phase commit.

Action: Complete the current transaction before attempting the action that caused the error.

ORA-02048 attempt to begin distributed transaction without logging on

Cause: The client program did not issue a distributed transaction login. This is an internal error.

Action: Contact Oracle Support Services.

ORA-02049 timeout: distributed transaction waiting for lock

Cause: Exceeded INIT.ORA DISTRIBUTED_LOCK_TIMEOUT seconds waiting for lock.

Action: Treat as a deadlock.

ORA-02050 transaction string rolled back, some remote DBs may be in-doubt

Cause: Network or remote failure during a two-phase commit.

Action: Notify operations; remote databases will automatically re-sync when the failure is repaired.

ORA-02051 another session in same transaction failed

Cause: A session at the same site with same global transaction ID failed.

Action: No action necessary; the transaction is automatically recovered.

ORA-02052 remote transaction failure at string

Cause: There was some error in a remote transaction at the named database link.

Action: More descriptive messages will follow. Correct the problem specified in the following messages and retry the operation.

ORA-02053 transaction string committed, some remote DBs may be in-doubt

Cause: There was a network failure or a remote failure during the two-phase commit.

Action: Notify the database administrator. The remote databases will resynchronize automatically when the failure is repaired.

ORA-02054 transaction string in-doubt

Cause: There was a network failure or a remote failure in the two-phase commit.

Action: Notify the database administrator. The remote databases will resynchronize automatically when the failure is repaired. Monitor the DBA_2PC_PENDING table for the outcome and resubmit the transaction, if necessary.

ORA-02055 distributed update operation failed; rollback required

Cause: A failure during a distributed update operation may not have rolled back all effects of the operation. Since some sites may be inconsistent with others, the transaction must roll back to a savepoint or roll back entirely.

Action: Roll back to a savepoint or roll back the entire transaction and resubmit the rolled-back statements.

ORA-02056 2PC: string: bad two-phase command numberstring from string

Cause: There was a two-phase commit protocol error.

Action: The transaction may automatically recover. Monitor the DBA_2PC_PENDING table to determine the resolution. Enter the transaction again, if necessary. Contact Oracle Support Services if necessary.

ORA-02057 2PC: string: bad two-phase recovery state numberstring from string

Cause: An internal error in the two-phase recovery protocol occurred.

Action: Contact Oracle Support Services.

ORA-02058 no prepared transaction found with ID string

Cause: No transaction with LOCAL_TRAN_ID or GLOBAL_TRAN_ID found in the PENDING_TRANS$ table in prepared state.

Action: Check the PENDING_TRANS$ table.

ORA-02059 ORA-2PC-CRASH-TEST-string in commit comment

Cause: This is a special comment used to test the two-phase commit.

Action: Do not use this special comment (string a number 1-10).

ORA-02060 select for update specified a join of distributed tables

Cause: An attempt was made to join tables in different remote databases in a SELECT... FOR UPDATE statement.

Action: Joined tables in a SELECT statement with the FOR UPDATE clause must reside at the same database. Simplify the SELECT... FOR UPDATE statement so that it joins only tables in the same database.

ORA-02061 lock table specified list of distributed tables

Cause: Tables in a LOCK TABLE statement must reside at the same database.

Action: Issue multiple LOCK TABLE commands.

ORA-02062 distributed recovery received DBID string, expectedstring

Cause: A database link at a coordinator no longer points to the expected database. Link may have been redefined, or a different database mounted.

Action: Restore the link definition or the remote database.

ORA-02063 preceding stringstring from stringstring

Cause: An Oracle error was received from a remote database link.

Action: Refer to the preceding error message(s).

ORA-02064 distributed operation not supported

Cause: One of the following unsupported operations was attempted:

• Array execute of a remote update with a subquery that references a database link, or
• An update of a long column with bind variable and an update of a second column with a subquery that both references a database link and a bind variable, or
• A commit is issued in a coordinated session from an RPC with OUT parameters.

Action: Simplify the remote update statement.

ORA-02065 illegal option for ALTER SYSTEM

Cause: The option specified for ALTER SYSTEM is not supported.

Action: Refer to the Oracle9i SQL Reference for information about options supported.

ORA-02066 missing or invalid DISPATCHERS text

Cause: A character string literal was expected, but not found, followingALTER SYSTEM SET DISPATCHERS.

Action: Place the string literal containing the dispatcher's specification afterALTER SYSTEM SET DISPATCHERS.

ORA-02067 transaction or savepoint rollback required

Cause: A failure (typically a trigger or stored procedure with multiple remote updates) occurred such that the all-or-nothing execution of a previous Oracle call cannot be guaranteed.

Action: Roll back to a previous savepoint or roll back the transaction and resubmit.

ORA-02068 following severe error from stringstring

Cause: A severe error (disconnect, fatal Oracle error) was received from the indicated database link. See following error text.

Action: Contact the remote system administrator.

ORA-02069 global_names parameter must be set to TRUE for this operation

Cause: A remote mapping of the statement is required but cannot be achieved because GLOBAL_NAMES should be set to TRUE for it to be achieved.

Action: Issue ALTER SESSION SET GLOBAL_NAMES = TRUE if possible.

ORA-02070 database stringstring does not support string in this context

Cause: The remote database does not support the named capability in the context in which it is used.

Action: Simplify the SQL statement.

ORA-02071 error initializing capabilities for remote database string

Cause: Could not load a remote-specified capability table.

Action: Contact Oracle Support Services for the remote SQL*Connect product.

ORA-02072 distributed database network protocol mismatch

Cause: This should never happen between different PRODUCTION releases of ORACLE, but may happen between alpha and beta releases, for example.

Action: Upgrade the older release.

ORA-02073 sequence numbers not supported in remote updates

Cause: Sequence numbers may not be used in INSERTS, UPDATES, or DELETES on remote tables.

Action: Perform the operation without specifying a sequence number.

ORA-02074 cannot string in a distributed transaction

Cause: A commit or rollback was attempted from session other than the parent of a distributed transaction.

Action: Only commit or roll back from the parent session.

ORA-02075 another instance changed state of transaction string

Cause: A commit force or rollback force was issued from a session in another instance.

Action: Check if another Oracle instance is performing recovery of pending transactions. Query DBA_2PC_PENDING to determine the new state of the transaction.

ORA-02076 sequence not co-located with updated table or long column

Cause: All referenced sequences must be located on the same node as the updated table or the long column.

Action: Correct the problem and then reissue the statement.

ORA-02077 selects of long columns must be from co-located tables

Cause: All tables returning values of long columns in a SELECT statement must be located at the same node.

Action: Correct the problem, then reissue the statement.

ORA-02078 invalid setting for ALTER SYSTEM FIXED_DATE

Cause: An invalid value was used.

Action: Use a correct value.

ORA-02079 no new sessions may join a committing distributed transaction

Cause: A call to UPI2BG was issued in a session for a transaction that has begun to commit in a different branch; that is, a call to UPI2EN was issued for a branch of the same transaction in another session. This can only happen when using an external transaction manager.

Action: Contact Oracle Support Services.

ORA-02080 database link is in use

Cause: A transaction is active or a cursor is open on the database link given in the ALTER SESSION CLOSE DATABASE LINKlink command.

Action: Commit or roll back, and close all cursors

ORA-02081 database link is not open

Cause: An attempt was made to use a database link that is not currently open.

Action: Resolve network problems or contact the remote database administrator to determine if the remote database's problem has been fixed. Contact the local database administrator to determine if network problems have been resolved. Wait until the link is open and try the operation again.

ORA-02082 a loopback database link must have a connection qualifier

Cause: An attempt was made to create a database link with the same name as the current database.

Action: This database link needs a trailing qualifier to make the name unique. These qualifiers are operating system-specific. See your operating system-specific Oracle documentation for more information about creating database links.

ORA-02083 database name has illegal character 'string'

Cause: The database name supplied contains an invalid character. For example, there can be no periods, semicolons, single quotes, double quotes, blanks, or non-printable characters in the database name. See theOracle9i Database Administrator's Guide for naming rules.

Action: Specify a valid database name.

ORA-02084 database name is missing a component

Cause: The complete database name was not provided.

Action: Specify the full database name.

ORA-02085 database link string connects to string

Cause: The database link attempted to connect to a database with a different name. The name of the database link must be the same name as the name of the database.

Action: Create a database link with the same name as the database to which it connects.

ORA-02086 database (link) name is too long

Cause: The name of the database or database link is too long. Database and database link names can be no longer than 128 characters.

Action: Specify the correct database or database link name or specify a name with fewer characters.

ORA-02087 object locked by another process in same transaction

Cause: A database link is being used in the cluster database environment that loops back to the same instance. One session is trying to convert a lock that was obtained by the other session.

Action: Get the more restrictive lock first. For example, if session 1 gets a share lock and session 2 gets an exclusive lock on the same object, get the exclusive lock first. Or use the same session to access the object.

ORA-02088 distributed database option not installed

Cause: The distributed database option is not installed at this site, so the requested operation is not possible.

Action: Contact Oracle Support Services about obtaining the distributed database option.

ORA-02089 COMMIT is not allowed in a subordinate session

Cause: COMMIT was issued in a session that is not the two-phase commit global coordinator.

Action: Issue commit at the global coordinator only.

ORA-02090 network error: attempted callback+passthru

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-02091 transaction rolled back

Cause: The distributed transaction is assigned to the system rollback segment and is trying to get into the prepared state, but the required number of non-PREPARED slots are not available, so the transaction is rolled back.

If the transaction aborted at a remote site, only ORA-02091 will be seen. If the transaction aborted at the host site, then both ORA-02091 and ORA-02092 will be seen.

Action: Complete the current transaction and then do the operation required.

ORA-02092 out of transaction table slots for distributed transaction

Cause: The transaction is assigned to the system rollback segment and is trying to get into the PREPARED state, but the required number of non-PREPARED slots are not available, hence the transaction is rolled back.

Action: Add a rollback segment and retry the transaction.

ORA-02093 TRANSACTIONS_PER_ROLLBACK_SEGMENT(string) more than maximum possible(string)

Cause: Value of the parameter specified is greater than allowed on this port.

Action: Use default or reduce it to less than the maximum.

ORA-02094 replication option not installed

Cause: The replication option was not installed at this site. Updatable materialized views, deferred RPCs, and other replication features were, therefore, unavailable.

Action: Install the replication option. The replication option is not part of the Oracle Server product and must be purchased separately. Contact an Oracle Sales representative if the replication option needs to be purchased.

ORA-02095 specified initialization parameter cannot be modified

Cause: Specified initialization parameter is not modifiable with this option.

Action: Check the Oracle9i Database Administrator's Guide for information about under what scope the parameter may be modified.

For more information about modifying an initialization parameter, see theOracle9i Database Reference.

ORA-02096 specified initialization parameter is not modifiable with this option

Cause: Though the initialization parameter is modifiable, it cannot be modified using the specified command.

Action: Check the Oracle9i Database Administrator's Guide for information about under what scope the parameter may be modified

ORA-02097 parameter cannot be modified because specified value is invalid

Cause: Though the initialization parameter is modifiable, the modified value is not acceptable to the parameter.

Action: Check the Oracle9i Database Administrator's Guide for range of acceptable values for this parameter.

ORA-02098 error parsing index-table reference (:I)

Cause: An incorrect index-table (:I) syntax was encountered.

Action: This syntax is for Oracle internal use only.

---

Copyright © 1996, 2002 Oracle Corporation.
All Rights Reserved.
Home
Book List
Contents
Index
Master Index
Feedback