Release 8.1.5
A67785-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8i Error Messages Release 8.1.5 A67785-01 |
|
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. For Trusted Oracle configured in DBMS MAC mode, you may see this message if a duplicate entry exists at a different level.
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 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 (not string)
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:
Action: For one of the above causes, either:
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:
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:
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. Use extra + level to dump global area level as well as extra 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: An OPS command was issued for a non-OPS ORADEBUG command.
Action: Issue the command without the OPS syntax.
ORA-00088 command cannot be executed by MTS server
Cause: A debug command was issued on an MTS 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 an OPS ORADEBUG command.
Action: Reissue the command with valid instance numbers.
ORA-00090 failed to allocate memory for OPS ORADEBUG command
Cause: Could not allocate the memory needed to execute parallel 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 MTS_DISPATCHERS
Cause: The syntax for the MTS_DISPATCHERS parameter is incorrect.
Action: Enter the MTS_DISPATCHERS 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 MTS_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 MTS_MAX_SERVERS as the system will automatically start new servers to break the deadlock until the number of servers reaches the value specified in MTS_MAX_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 INIT.ORA file.
Action: Do one of the following:
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:
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 Customer Support.
ORA-00111 no servers started because number of servers is limited to string
Cause: An attempt was made to start more servers than the maximum number specified by the system parameter MTS_MAX_SERVERS.
Action: Increase the value of the MTS_MAX_SERVERS initialization parameter as needed or re-issue the ALTER SYSTEM SET MTS_SERVERS command 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 parameter MTS_MAX_DISPATCHERS.
Action: Increase the value of the MTS_MAX_DISPATCHERS initialization parameter as needed.
ORA-00113 protocol name string is too long
Cause: A protocol name specified in the MTS_DISPATCHERS initialization parameter is too long.
Action: Use a valid protocol name for the MTS_DISPATCHERS value.
ORA-00114 missing value for system parameter MTS_SERVICE
Cause: No value was specified for the MTS_SERVICE initialization parameter, nor for the DB_NAME parameter.
Action: Add an MTS_SERVICE or DB_NAME definition to the initialization file. By default, MTS_SERVICE is the value of DB_NAME unless MTS_SERVICE 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 MTS_SERVICE name is too long
Cause: The service name specified in the MTS_SERVICE initialization parameter is too long.
Action: Use a shorter name for the MTS_SERVICE value (less than or equal to 255 characters).
ORA-00117 value out of range for system parameter MTS_SERVERS
Cause: The specified value of the MTS_SERVERS parameter is incorrect.
Action: MTS_SERVERS must be greater than or equal to 0 and less than or equal to the value of MTS_MAX_SERVERS.
ORA-00118 value out of range for system parameter MTS_DISPATCHERS
Cause: The value of the MTS_DISPATCHERS parameter is incorrect.
Action: The sum of all MTS_DISPATCHERS values must be greater than or equal to 0 and less than or equal to the value of MTS_MAX_DISPATCHERS.
ORA-00119 invalid specification for system parameter MTS_LISTENER_ADDRESS
Cause: The syntax for the MTS_LISTENER_ADDRESS parameter is incorrect.
Action: Refer to the Oracle8i Reference manual 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 Oracle8i Administrator's Guide and your operating system-specific documentation for procedures for starting and configuration the dispatcher process.
ORA-00121 MTS_SERVERS specified without MTS_DISPATCHERS
Cause: A definition for MTS_SERVERS was specified in the INIT.ORA file, but no definition for MTS_DISPATCHERS was specified. Without a value for MTS_DISPATCHERS, shared servers will never be used.
Action: Add a definition for MTS_DISPATCHERS in the INIT.ORA file (or take out the definition for MTS_SERVERS, if MTS is 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 MTS_DISPATCHERS specified without MTS_MAX_SERVERS
Cause: A definition for MTS_DISPATCHERS was specified in the INIT.ORA file, but MTS_MAX_SERVERS was specified as zero.
Action: Specify MTS_MAX_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-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 Customer Support.
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 an Oracle 7.3 server 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.
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 allowed string)
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-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 version string
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, # blocks string) 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 the Oracle8i Administrator's Guide for information on recovering from the loss of a control file. See also your operation 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:
ORA-00206 error in writing (block string, # blocks string) 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 the Oracle8i Administrator's Guide for information on recovering from the loss of a control file. See also your operation 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 of string 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-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 size string
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 size string
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 string string
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 string string
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 thread string
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:
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 not string
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 LOGFILE filename 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 thread string
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 for string are s, S, t, and T.
Action: Correct the initialization file and restart the instance.
ORA-00295 datafile number string is invalid, must be between 1 and string
Cause: An invalid file number was specified.
Action: Specify a correct datafile 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 Customer Support.
ORA-00298 Missing or invalid TIMEOUT interval
Cause: A non-zero integer timeout interval (in minutes) must be specified after the TIMEOUT keyword.
Action: Correct the syntax and retry the command.
ORA-00300 illegal redo log block size string specified - exceeds limit of string
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:
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-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:
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:
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; sequence string 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 thread string
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 the Oracle8i 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 the Oracle8i 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 the Oracle8i 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 Oracle8i 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 the Oracle8i 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 the Oracle8i Administrator's Guide for recovery procedures.
ORA-00320 cannot read file header from log string of thread string
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 the Oracle8i 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 change string
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 change string
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 change string
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 change string
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 version string
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 minimum string 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 thread string
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 the Oracle8i 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 count string
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 change string 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 group string
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 no free buffer handles available
Cause: The value of the initialization parameter DB_HANDLES is too small.
Action: Increase the parameter value. The default value should be sufficient.
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 version string
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, valid 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 INIT.ORA 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
Cause: All buffers in the specified buffer pool are in use and no free buffers are available.
Action: Increase the number of buffers in the specified pool.
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-00400 invalid release value string for parameter string
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 release string
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 to string.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-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 Customer Support.
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 Customer Support.
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 after string 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 Customer Support.
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 error string
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 snapshot refresh process terminated abnormally.
Action: Restart 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 Lock Manager monitor process terminated abnormally.
Action: Restart the instance.
ORA-00482 LMD* process terminated with error
Cause: A Lock Manager 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-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:
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 Customer Support after gathering the following information:
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 Customer Support.
ORA-00602 internal programming exception
Cause: Internal programming exception occurred.
Action: Report this error as a program bug to Oracle Customer Support.
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 Customer Support.
ORA-00606 Internal error code
Cause: A call to deferred UPI functions was made in non-deferred mode.
Action: Contact Oracle Customer Support.
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 Customer Support.
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-00816 error message translation failed
Cause: There is an internal error where a routine was unable to translate a message code.
Action: Contact Oracle Customer Support.
