ORACLE错误代码超级大全
ORA-00000: normal, successful completion
原因：Normal exit.
解决：None.
ORA-00001: unique constraint (string.string) violated
原因：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.
解决：Either remove the unique restriction or do not insert the key.
ORA-00017: session requested to set trace event
原因：The current session was requested to set a trace event by another session.
解决：This is used internally; no action is required.
ORA-00018: maximum number of sessions exceeded
原因：All session state objects are in use.
解决：Increase the value of the SESSIONS initialization parameter.
ORA-00019: maximum number of session licenses exceeded
原因：All licenses are in use.
解决：Increase the value of the LICENSE MAX SESSIONS initialization parameter.
ORA-00020: maximum number of processes (string) exceeded
原因：All process state objects are in use.
解决：Increase the value of the PROCESSES initialization parameter.
ORA-00021: session attached to some other process; cannot switch session
原因：The user session is currently used by others.
解决：Do not switch to a session attached to some other process.
ORA-00022: invalid session ID; access denied
原因：Either the session specified does not exist or the caller does not have the privilege to access it.
解决：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
原因：An attempt was made to detach the current session when it contains references to process private memory.
解决：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
原因：Trying to login more than once from different processes for ORACLE started in single-process mode.
解决：Logoff from the other process.
ORA-00025: failed to allocate string
原因：Out of memory.
解决：Restart with larger sga heap.
ORA-00026: missing or invalid session ID
原因：Missing or invalid session ID string for ALTER SYSTEM KILL SESSION.
解决：Retry with a valid session ID.
ORA-00027: cannot kill current session
原因：Attempted to use ALTER SYSTEM KILL SESSION to kill the current session.
解决：None.
ORA-00028: your session has been killed
原因：A privileged user has killed your session and you are no longer logged on to the database. 解决：Login again if you wish to continue working.
ORA-00029: session is not a user session
原因：The session ID specified in an ALTER SYSTEM KILL SESSION command was not a user session (for example, recursive, etc.).
解决：Retry with a user session ID.
ORA-00030: User session ID does not exist.
原因：The user session ID no longer exists, probably because the session was logged out.
解决：Use a valid session ID.
ORA-00031: session marked for kill
原因：The session specified in an ALTER SYSTEM KILL SESSION command cannot be killed immediately (because it is rolling back or blocked on a network operation), but it has been marked for kill. This means it will be killed as soon as possible after its current uninterruptable operation is done.
解决：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
原因：The session migration password specified in a session creation call was invalid (probably too long).
解决：Retry with a valid password (less than 30 chars).
ORA-00033: current session has empty migration password
原因：An attempt was made to detach or clone the current session and it has an empty migration password. This is not allowed.
解决：Create the session with a non-empty migration password.
ORA-00034: cannot string in current PL/SQL session
原因：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 "alter session disable commit in procedure")
解决：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-00036: maximum number of recursive SQL levels (string) exceeded
原因：An attempt was made to go more than the specified number of recursive SQL levels.
解决：Remove the recursive SQL, possibly a recursive trigger.
ORA-00037: cannot switch to a session belonging to a different server group
原因：An attempt was made to switch to a session in a different server group. This is not allowed. 解决：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
原因：An attempt was made to create a non-migratable session in a server group that is owned by
a different user.
解决：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 login 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-00040: active time limit exceeded - call aborted
原因：The Resource Manager SWITCH_TIME limit was exceeded.
解决：Reduce the complexity of the update or query, or contact your database administrator for more information.
ORA-00041: active time limit exceeded - session terminated
原因：The Resource Manager SWITCH_TIME limit was exceeded.
解决：Reduce the complexity of the update or query, or contact your database administrator for more information.
ORA-00042: Unknown Service name string
原因：An attempt was made to use an invalid application service.
解决：Use a valid service name from SERVICE$ or add a new service using the DBMS_SERVICE package.
ORA-00050: operating system error occurred while obtaining an enqueue
原因：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.
解决：Look up the operating system error in your system documentation and perform the needed action.
ORA-00051: timeout occurred while waiting for a resource
原因：Usually due to a dead instance.
解决：Check for any dead, unrecovered instances and recover them.
ORA-00052: maximum number of enqueue resources (string) exceeded
原因：Ran out of enqueue resources.
解决：Increase the value of the ENQUEUE_RESOURCES initialization parameter.
ORA-00053: maximum number of enqueues exceeded
原因：Ran out of enqueue state objects.
解决：Increase the value of the ENQUEUES initialization parameter.
ORA-00054: resource busy and acquire with NOWAIT specified
原因：Resource interested is busy.
解决：Retry if necessary.
ORA-00055: maximum number of DML locks exceeded
原因：Ran out of DML lock state objects.
解决：Increase the value of the DML_LOCKS initialization parameter and warm start.
ORA-00056: DDL lock on object "string.string" is already held in an incompatible mode
原因：An attempt was made to acquire a DDL lock that is already locked.
解决：This happens if you attempt to drop a table that has parse locks on it.
ORA-00057: maximum number of temporary table locks exceeded
原因：The number of temporary tables equals or exceeds the number of temporary table locks.
Temporary tables are often created by large sorts.
解决：Increase the value of the TEMPORARY_TABLE_LOCKS initialization parameter and warm start.
ORA-00058: DB_BLOCK_SIZE must be string to mount this database (not string)
原因：DB_BLOCK_SIZE initialization parameter is wrong for the database being mounted. It does not match the value used to create the database.
解决：Fix the value of the DB_BLOCK_SIZE parameter or mount a database that matches the value.
ORA-00059: maximum number of DB_FILES exceeded
原因：The value of the DB_FILES initialization parameter was exceeded.
解决：Increase the value of the DB_FILES parameter and warm start.
ORA-00060: deadlock detected while waiting for resource
原因：Transactions deadlocked one another while waiting for resources.
解决：Look at the trace file to see the transactions and resources involved. Retry if necessary. ORA-00061: another instance has a different DML_LOCKS setting
原因：The shared instance being started is using DML locks, and the running instances are not, or vice-versa.
解决：Ensure that all instances" INIT.ORA files specify the DML_LOCKS parameter as 0 or all as non-zero.
ORA-00062: DML full-table lock cannot be acquired; DML_LOCKS is 0
原因：The instance was started with DML_LOCKS = 0, and the statement being executed needs a full-table lock (S, X, or SSX).
解决：Restart the instance with DML_LOCKS not equal to zero, and reexecute the statement. ORA-00063: maximum number of log files exceeded string
原因：The number of log files specificied exceeded the maximum number of log files supported in this release.
解决：Re-create the control file with the highest number of log files no greater than the maximum supported in this release.
ORA-00064: object is too large to allocate on this O/S (string,string)
原因：An initialization parameter was set to a value that required allocating more contiguous space than can be allocated on this operating system.
解决：Reduce the value of the initialization parameter.
ORA-00065: initialization of FIXED_DA TE failed
原因：The FIXED_DATE string was not in date format yyyy-mm-dd:hh24:mi:ss.
解决：Make sure the initialization parameter is in the correct date format.
ORA-00067: invalid value string for parameter string; must be at least string
原因：The value for the initialization parameter is invalid.
解决：Choose a value as indicated by the message.
ORA-00068: invalid value string for parameter string, must be between string and string
原因：The value for the initialization parameter is invalid.
解决：Choose a value as indicated by the message.
ORA-00069: cannot acquire lock -- table locks disabled for string
原因：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.
解决：Use the ALTER TABLE ... ENABLE TABLE LOCK command, and retry the command. ORA-00070: command string is not valid
原因：An invalid debugger command was specified.
解决：Type HELP to see the list of available commands.
ORA-00071: process number must be between 1 and string
原因：An invalid process number was specified.
解决：Specify a valid process number.
ORA-00072: process "string" is not active
原因：An invalid process was specified.
解决：Specify a valid process.
ORA-00073: command string takes between string and string argument(s)
原因：An incorrect number of arguments was specified.
解决：Specify the correct number of arguments. Type HELP to see the list of commands and their syntax.
ORA-00074: no process has been specified
原因：No debug process has been specified.
解决：Specify a valid process.
ORA-00075: process "string" not found in this instance
原因：The specified process was not logged on to the current instance.
解决：Specify a valid process.
ORA-00076: dump string not found
原因：An attempt was made to invoke a dump that does not exist.
解决：Type DUMPLIST to see the list of available dumps.
ORA-00077: dump string is not valid
原因：An attempt was made to invoke an invalid dump.
解决：Try another dump.
ORA-00078: cannot dump variables by name
原因：An attempt was made to dump a variable by name on a system that does not support this feature.
解决：Try the PEEK command.
ORA-00079: variable string not found
原因：An attempt was made to dump a variable that does not exist.
解决：Use a valid variable name.
ORA-00080: invalid global area specified by level string
原因：An attempt was made to dump an invalid global area.
解决：Use level 1 for the PGA, 2 for the SGA, and 3 for the UGA. Use
原因：An attempt was made to read/write an invalid memory address range.
解决：Try another address or length.
ORA-00082: memory size of string is not in valid set of [1], [2], [4]stringstringstringstringstring 原因：An invalid length was specified for the POKE command.
解决：Use a valid length (either 1, 2, 4, or possibly 8).
ORA-00083: warning: possibly corrupt SGA mapped
原因：Even though there may be SGA corruptions, the SGA was mapped.
解决：Use the DUMPSGA command to dump the SGA.
ORA-00084: global area must be PGA, SGA, or UGA
原因：An attempt was made to dump an invalid global area.
解决：Specify either PGA, SGA, or UGA.
ORA-00085: current call does not exist
原因：An invalid attempt was made to dump the current call heap.
解决：Wait until the process starts a call.
ORA-00086: user call does not exist
原因：An invalid attempt was made to dump the user call heap.
解决：Wait until the process starts a call.
ORA-00087: command cannot be executed on remote instance
原因：Cluster database command issued for non cluster database ORADEBUG command.
解决：Issue the command without the cluster database syntax.
ORA-00088: command cannot be executed by shared server
原因：Debug command issued on shared server.
解决：Reissue the command using a dedicated server.
ORA-00089: invalid instance number in ORADEBUG command
原因：An invalid instance number was specified in a cluster database ORADEBUG command. 解决：Reissue the command with valid instance numbers.
ORA-00090: failed to allocate memory for cluster database ORADEBUG command
原因：Could not allocate memory needed to execute cluster database oradebug.
解决：Reissue the command on each instance with single-instance oradebug.
ORA-00091: LARGE_POOL_SIZE must be at least string
原因：The value of LARGE_POOL_SIZE is below the minimum size.
解决：Increase the value of LARGE_POOL_SIZE past the minimum size.
ORA-00092: LARGE_POOL_SIZE must be greater than LARGE_POOL_MIN_ALLOC
原因：The value of LARGE_POOL_SIZE is less than the value of LARGE_POOL_MIN_ALLOC.
解决：Increase the value of LARGE_POOL_SIZE past the value of LARGE_POOL_MIN_ALLOC.
ORA-00093: %s must be between string and string
原因：The parameter value is not in a valid range.
解决：Modify the parameter value to be within the specified range.
ORA-00094: %s requires an integer value
原因：The parameter value is not an integer.
解决：Modify the parameter value to be an integer.
ORA-00096: invalid value string for parameter string, must be from among string
原因：The value for the initialization parameter is invalid.
解决：Choose a value as indicated by the message.
ORA-00097: use of Oracle SQL feature not in SQL92 string Level
原因：Usage of Oracle"s SQL extensions.
解决：none
ORA-00100: no data found
原因：An application made reference to unknown or inaccessible data.
解决：Handle this condition within the application or make appropriate modifications to the application code. NOTE: If the application uses Oracle-mode SQL instead of ANSI-mode SQL, ORA-01403 will be generated instead of ORA-00100.
ORA-00101: invalid specification for system parameter DISPATCHERS
原因：The syntax for the DISPATCHERS parameter is incorrect.
解决：Refer to the manual for correct syntax.
ORA-00102: network protocol string cannot be used by dispatchers
原因：The network specified in DISPA TCHERS does not have the functionality required by the dispatchers.
解决：Refer to the manual on network protocols supported by the dispatchers.
ORA-00103: invalid network protocol; reserved for use by dispatchers
原因：The network specified in the SQL*Net connect string is reserved for use by the dispatchers.
解决：Specify other network protocols in the connection string.
ORA-00104: deadlock detected; all public servers blocked waiting for resources
原因：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.
解决：Increase the limit for the system parameter MAX_SHARED_SERVERS as the system will automaticaly start up new servers to break the deadlock until the number of servers reaches the value specified in MAX_SHARED_SERVERS.
ORA-00105: too many dispatcher configurations
原因：Too many dispatcher configurations have been specified. No more can be added.
解决：Consolidate the dispatcher configurations if possible.
ORA-00106: cannot startup/shutdown database when connected to a dispatcher
原因：An attempt was made to startup/shutdown database when connected to a shared server via a dispatcher.
解决：Re-connect 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
原因：Most likely due to the fact that ORACLE listener has not been started.
解决：Start ORACLE listener if it has not been started. Or else contact your ORACLE representative.
ORA-00108: failed to set up dispatcher to accept connection asynchronously
原因：Most likely due to the fact that the network protocol used by the the dispatcher does not support aynchronous operations.
解决：Contact your ORACLE representative.
ORA-00109: invalid value for attribute string: string
原因：The value specified for the attribute was incorrect.
解决：Refer to the manual for the proper values.
ORA-00110: invalid value string for attribute string, must be between string and string
原因：The value specified for the attribute was incorrect.
解决：Specify a value within the range allowed.
ORA-00111: invalid attribute string
原因：The specified attribute was not recognized.
解决：Refer to the manual for the proper keyword to use to specify a dispatcher attribute.
ORA-00112: value of string is null
原因：The attribute was specified with no value.
解决：Specify a non-null value.
ORA-00113: protocol name string is too long
原因：A protocol name specified in the DISPA TCHERS system parameter is too long.
解决：Use a valid protocol name for the DISPATCHERS value.
ORA-00114: missing value for system parameter SERVICE_NAMES
原因：No value was specified for the SERVICE_NAMES system parameter, nor for the DB_NAME parameter.
解决：Add an SERVICE_NAMES or DB_NAME definition to the INIT.ORA 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
原因：A connection request was refused by a dispatcher because the dispatcher cannot support any more connections.
解决：Connect to a different dispatcher, or use a dedicated server.
ORA-00116: SERVICE_NAMES name is too long
原因：A service name specified in the SERVICE_NAMES system parameter is too long.
解决：Use a shorter name in the SERVICE_NAMES value (<= 255 chars).
ORA-00117: PROTOCOL, ADDRESS or DESCRIPTION must be specified
原因：PROTOCOL, ADDRESS or DESCRIPTION was not specified.
解决：Use one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION to specify the listening address for dispatchers.
ORA-00118: Only one of PROTOCOL, ADDRESS or DESCRIPTION may be specified
原因：More than one of PROTOCOL, ADDRESS or DESCRIPTION was specified.
解决：Use only one of the attributes: PROTOCOL, ADDRESS or DESCRIPTION to specify the listening address for dispatchers.
ORA-00119: invalid specification for system parameter string
原因：The syntax for the specified parameter is incorrect.
解决：Refer to the Oracle Reference Manual for the correct syntax.
ORA-00122: cannot initialize network configuration
原因：ORACLE could not initialize SQL*Net version 2.
解决：Check the error stack for detailed information.
ORA-00123: idle public server terminating
原因：Too many idle servers were waiting on the common queue.
解决：This error is used internally, no action is required.
ORA-00125: connection refused; invalid presentation
原因：The PRESENTA TION in the CONNECT_DA TA of the TNS address DESCRIPTION is not correct or is not supported.
解决：Correct the PRESENTATION specified in the TNS address.
ORA-00126: connection refused; invalid duplicity
原因：The DUPLICITY in the CONNECT_DATA of the TNS address DESCRIPTION is not correct or is not supported.
解决：Correct the DUPLICITY specified in the TNS address.
ORA-00127: dispatcher string does not exist
原因：There is currently no dispatcher running with the specified name.
解决：Retry with a name of the form "D###" denoting an existing dispatcher process.
ORA-00128: this command requires a dispatcher name
原因：Wrong syntax for ALTER SYSTEM SHUTDOWN
解决：Use correct syntax: ALTER SYSTEM SHUTDOWN [ IMMEDIATE ] "dispatcher name" ORA-00129: listener address validation failed "string"
原因：An error was encountered while validating the listener address.
解决：Resolve error or contact your ORACLE representative.
ORA-00130: invalid listener address "string"
原因：The listener address specification is not valid.
解决：Make sure that all fields in the listener address (protocol, port, host, key, ...) are correct. ORA-00131: network protocol does not support registration "string"
原因：The specified protocol does not support async notification.
解决：Refer to the manual for information on supported network protocols.
ORA-00132: syntax error or unresolved network name "string"
原因：Listener address has syntax error or cannot be resolved.
解决：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-00133: value of string is too long
原因：The value specified for the attribute was too long.
解决：Use shorter names and keywords or remove unneeded blanks.
ORA-00134: invalid DISPA TCHERS specification #string
原因：The syntax for the n-th DISPATCHERS specification was incorrect.
解决：Refer to the Oracle Reference Manual for the correct syntax.
ORA-00150: duplicate transaction ID
原因：Attempted to start a new transaction with an ID already in use by an existing transaction. 解决：Check your application.
ORA-00151: invalid transaction ID
原因：The specified transaction ID does not correspond to an existing valid transaction.
解决：Check your application.
ORA-00152: current session does not match requested session
原因：The current session is not the same as the session that was passed into a upixado() call.
解决：Check your application.
ORA-00153: internal error in XA library
原因：The XA library could not access thread-specific pointers.
解决：Contact customer support.
ORA-00154: protocol error in transaction monitor
原因：The transaction monitor returned TMJOIN on an AX_REG call but the transaction was locally suspended.
解决：Contact the transaction monitor customer support.
ORA-00155: cannot perform work outside of global transaction
原因：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.
解决：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)
原因：An external global transaction ID with a too large length field was passed in.
解决：Report the problem to your external transaction coordinator vendor.
ORA-00161: transaction branch length string is illegal (maximum allowed string)
原因：An external transaction branch ID with a length either too large or 0 was passed in.
解决：Report the problem to your external transaction coordinator vendor.
ORA-00162: external dbid length string is greater than maximum (string)
原因：An external database name with too large a length field was passed in.
解决：Report the problem to your external transaction coordinator vendor.
ORA-00163: internal database name length string is greater than maximum (string)
原因：An internal database name with a too large length field was passed in.
解决：Report the problem to your external transaction coordinator vendor.
ORA-00164: distributed autonomous transaction disallowed within migratable distributed transaction
原因：A request was made by the application to start a distributed autonomous transaction when the application was in a migratable distributed transaction.
解决：Roll back or commit the current distributed transaction first.
ORA-00165: migratable distributed autonomous transaction with remote operation is not allowed 原因：A request was made by the application to start a migratable distributed autonomous transaction with remote operation.
解决：none
ORA-00166: remote/local nesting level is too deep
原因：Too many remote table operations required a reverse trip back to the local site, for example to execute a local function on a remote table.
解决：Rearrange the query or co-locate the functions with the tables.
ORA-00200: control file could not be created
原因：It was not possible to create the control file.
解决：Check that there is sufficient disk space and no conflicts in filenames and try to create the control file again.
ORA-00201: control file version string incompatible with ORACLE version string
原因：The control file was created by incompatible software.
解决：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: control file: "string"
原因：This message reports the name file involved in other messages.
解决：See associated error messages for a description of the problem.
ORA-00203: using the wrong control files
原因：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.
解决：Check that the correct control files were specified.
ORA-00204: error in reading (block string, # blocks string) of control file
原因：A disk I/O failure was detected on reading the control file.
解决：Check if the disk is online, if it is not, bring it online and try a warm start again. If it is online, then you need to recover the disk.
ORA-00205: error in identifying control file, check alert log for more info
原因：The system could not find a control file of the specified name and size.
解决：Check that ALL control files are online and that they are the same files that the system created at cold start time.
ORA-00206: error in writing (block string, # blocks string) of control file
原因：A disk I/O failure was detected on writing the control file.
解决：Check if the disk is online, if it is not, bring it online and try a warm start again. If it is online, then you need to recover the disk.
ORA-00207: control files are not for the same database
原因：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.
解决：Check that the control file is for the correct database and is not an old version.
ORA-00208: number of control file names exceeds limit of string
原因：An attempt was made to use more control files than Oracle supports.
解决：Shut down Oracle. Reduce the number of control files specified in the CONTROL_FILES parameter in the initialization parameter file, and restart Oracle. Delete usused files.
ORA-00209: control file blocksize mismatch, check alert log for more info
原因：The block size in the control file header does not match the size specified in the DB_BLOCK_SIZE parameter.
解决：Look at the alert log for more information.
ORA-00210: cannot open the specified control file
原因：Cannot open the control file.
解决：Check to make sure the control file exists and is not locked by some other program. ORA-00211: control file does not match previous control files
原因：A control file was specified that belongs to another database.
解决：Find and install the correct control file.
ORA-00212: block size string below minimum required size of string bytes
原因：The block size specified was too small. Space for the system overhead is required.
解决：Specify a larger block size and retry the operation.
ORA-00213: cannot reuse control file; old file size string, string required
原因：To reuse a control file, it must be the same size as the one previously used.
解决：Either do not specify REUSE, or specify a matching combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses in the CREATE DA TABASE or CREATE CONTROLFILE statement.
ORA-00214: control file "string" version string inconsistent with file "string" version string
原因：An inconsistent set of control files, datafiles/logfiles, and redo files was used.
解决：Use a consistant set of control files, datafiles/logfiles, 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 control file
原因：No control file is specified or the control file specified does not exist.
解决：Specify at least one valid control file and retry the operation.
ORA-00216: control file could not be resized for migration from 8.0.2
原因：The control file created by release 8.0.2 was missing some record types. These record types are automatically added by resizing the control file during mount. The resize has failed.
解决：Look in the alert log for the reason that the resize has failed. If indicated in the alert log, give the control file more space. Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file.
ORA-00217: control file could not be resized for new record types
原因：The control file was missing some new record types supported by this release. These record types are automatically added by resizing the contol file during mount. The resize has failed.
解决：Look in the alert log for the reason that the resize has failed. If indicated in the alert log, give the control file more space. Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new control file.
ORA-00218: block size string of control file "string" does not match DB_BLOCK_SIZE (string) 原因：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.
解决：Restore a good copy of the control file. If the control file is known to be clean set the DB_BLOCK_SIZE to match control file headers block size value.
ORA-00219: required control file size (string logical blocks) exceeds maximum allowable size (string logical blocks)
原因：An invocation of CREATE DATABASE or CREATE CONTROLFILE was executed specifying a combination of parameters that would require the control file size in blocks to exceed the maximum allowable value.
解决：In the case of CREATE DA TABASE or CREATE CONTROLFILE, use a different combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses.
ORA-00220: control file not mounted by first instance, check alert log for more info
原因：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.
解决：Find and install the correct control file.
ORA-00221: error on write to control file
原因：An error occurred when writing to one or more of the control files.
解决：See accompanying messages.
ORA-00222: operation would reuse name of a currently mounted control file
原因：The filename supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of the specified
currently mounted control file.
解决：Retry the operation with a different filename.
ORA-00223: convert file is invalid or incorrect version
原因：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 ALTER DATABASE CONVERT command is issued.
解决：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: control file resize attempted with illegal record type (string)
原因：An attempt was made to expand or shrink the control file by calling cfileResizeSection using an invalid value for the RECORD_TYPE parameter.
解决：Use a value for the RECORD_TYPE parameter that specifies a valid record type other than type 0 (valid range is 1-16).
ORA-00225: expected size string of control file differs from actual size string
原因：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.
解决：Restore a good copy of the control file.
ORA-00226: operation disallowed while alternate control file open
原因：The attempted operation could not be executed at this time because this process had an alternate control file open for fixed table access.
解决：Retry the operation after calling cfileUseCurrent.
ORA-00227: corrupt block detected in control file: (block string, # blocks string)
原因：A block header corruption or checksum error was detected on reading the control file.
解决：Use the CREATE CONTROLFILE or RECOVER DA TABASE USING BACKUP CONTROLFILE command.
ORA-00228: length of alternate control file name exceeds maximum of string
原因：The specified filename, which was supplied as a parameter to cfileSetSnapshotName or cfileUseCopy, exceeds the maximum filename length for this operating system.
解决：Retry the operation with a shorter filename.
ORA-00229: operation disallowed: already hold snapshot control file enqueue
原因：The attempted operation cannot be executed at this time because this process currently holds the snapshot control file enqueue.
解决：Retry the operation after calling cfileUseCurrent to release the snapshot control file enqueue.
ORA-00230: operation disallowed: snapshot control file enqueue unavailable
原因：The attempted operation cannot be executed at this time because another process currently holds the snapshot control file enqueue.
解决：Retry the operation after the concurrent operation that is holding the snapshot control file enqueue terminates.
ORA-00231: snapshot control file has not been named
原因：During an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot it was detected that no filename for the snapshot control file had previously been specified.
解决：Specify a name for the snapshot control file by calling cfileSetSnapshotName.
ORA-00232: snapshot control file is nonexistent, corrupt, or unreadable
原因：The snapshot control file was found to be nonexistent, corrupt, or unreadable during an invocation of cfileUseSnapshot.
解决：Call cfileMakeAndUseSnapshot again (or for the first time).
ORA-00233: copy control file is corrupt or unreadable
原因：The specified copy control file was found to be corrupt or unreadable during an invocation of cfileUseCopy.
解决：Before retrying cfileUseCopy, use the ALTER DATABASE BACKUP CONTROLFILE command and specify the same filename that was specified for cfileUseCopy.
ORA-00234: error in identifying or opening snapshot or copy control file
原因：A snapshot or copy control file of the specified name could not be found or opened during an invocation of cfileUseSnapshot, cfileMakeAndUseSnapshot, or cfileUseCopy.
解决：Re-create the snapshot or copy control file using cfileMakeAndUseSnapshot or ALTER DA TABASE BACKUP CONTROLFILE, respectively.
ORA-00235: control file fixed table inconsistent due to concurrent update
原因：Concurrent update activity on a control file caused a query on a control file fixed table to read inconsistent information.
解决：Retry the operation.
ORA-00236: snapshot operation disallowed: mounted control file is a backup
原因：Attempting to invoke cfileSetSnapshotName, cfileMakeAndUseSnapshot, or cfileUseSnapshot when the currently mounted control file is a backup control file.
解决：Mount a current control file and retry the operation.
ORA-00237: snapshot operation disallowed: control file newly created
原因：An attempt to invoke cfileMakeAndUseSnapshot with a currently mounted control file that was newly created with CREATE CONTROLFILE was made.
解决：Mount a current control file and retry the operation.
ORA-00238: operation would reuse a filename that is part of the database
原因：The filename supplied as a parameter to the ALTER DA TABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of a file that is currently part of the database.
解决：Retry the operation with a different filename.
ORA-00250: archiver not started
原因：An attempt was made to stop automatic archiving, but the archiver process was not running.
解决：No action required.
ORA-00251: LOG_ARCHIVE_DUPLEX_DEST cannot be the same destination as string string 原因：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.
解决：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
原因：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 instance death during a log switch left the log empty.
解决：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
原因：The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command was too long.
解决：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"
原因：The specified archive log location is invalid in the archive command or the LOG_ARCHIVE_DEST initialization parameter.
解决：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
原因：An error occurred during archiving.
解决：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
原因：The destination specified by an ALTER SYSTEM ARCHIVE LOG START TO command could not be translated.
解决：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.
原因：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.
解决：Check 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
原因：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 filename.
解决：Specify log by filename, by group number or by thread and sequence number.
ORA-00259: log string of open instance string (thread string) is the current log, cannot archive
原因：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.
解决：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
原因：The log sequence number supplied to the archival command does not match any of the online logs for the thread. The log might have been reused for another sequence number, it might have been dropped, the sequence number might be greater than the current log sequence number, or the thread might not have any logs.
解决：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
原因：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.
解决：Wait for the current operation to complete and try again.
ORA-00262: current log string of closed thread string cannot switch
原因：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.
解决：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
原因：An attempt was made to manually archive the unarchived logs in this thread but no logs needed archiving.
解决：No action required.
ORA-00264: no recovery required
原因：An attempt was made to perform media recovery on files that do not // need any type of recovery.
解决：Do not attempt to perform media recovery on the selected files. Check to see that the filenames were entered properly. If not, retry the command with the proper filenames.
ORA-00265: instance recovery required, cannot set ARCHIVELOG mode
原因：The database either crashed or was shutdown with the ABORT option. Media recovery cannot be enabled because the online logs may not be sufficient to recover the current datafiles.
解决：Open the database and then enter the SHUTDOWN command with the NORMAL or IMMEDIATE option.
ORA-00266: name of archived log file needed
原因：During media recovery, the name of an archived redo log file was requested, but no name was entered.
解决：Mount the correct redo log file and enter its name when it is requested.
ORA-00267: name of archived log file not needed
原因：During media recovery, the name of an archived redo log file was entered, but no name was requested.
解决：Continue media recovery, but do not enter a new log name.
ORA-00268: specified log file does not exist "string"
原因：The given redo log file does not exist.
解决：Check the spelling and capitalization of the filename and retry the command.
ORA-00269: specified log file is part of thread string not string
原因：The given redo log file is not part of the given thread
解决：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
原因：An error was encountered when either creating or opening the destination file for archiving.
解决：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
原因：An attempt was made to archive the unarchived redo log files manually, but there are no files that need to be archived.
解决：No action required.
ORA-00272: error writing archive log string
原因：An I/O error occurred while archiving a redo log file.
解决：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
原因：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.
解决：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
原因：An illegal option was specified for a recovery command.
解决：Correct the syntax and retry the command.
ORA-00275: media recovery has already been started
原因：An attempt was made to start a second media recovery operation in the same session.
解决：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
原因：The CHANGE keyword was specified on the command line, but no change number was given.
解决：Retry the command using a valid change number after the CHANGE keyword.
ORA-00277: illegal option to the UNTIL recovery flag string
原因：Only CANCEL, CHANGE and TIME can be used with the UNTIL keyword.
解决：Correct the syntax.
ORA-00278: log file "string" no longer needed for this recovery
原因：The specified redo log file is no longer needed for the current recovery.
解决：No action 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
原因：The requested log is required to proceed with recovery.
解决：Please supply the requested log with "ALTER DATABASE RECOVER LOGFILE
ORA-00280: change string for thread string is in sequence #string
原因：This message helps to locate the redo log file with the specified change number requested by other messages.
解决：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
原因：An attempt was made to use a dispatcher process for media recovery. Memory
requirements disallow this recovery method.
解决：Connect to the instance via a dedicated server process to perform media recovery.
ORA-00282: UPI string call not supported, use ALTER DATABASE RECOVER
原因：The given UPI call is no longer supported.
解决：Use the ALTER DA TABASE RECOVER command for all recovery actions.
ORA-00283: recovery session canceled due to errors
原因：An error during recovery was determined to be fatal enough to end the current recovery session.
解决：More specific messages will accompany this message. Refer to the other messages for the appropriate action.
ORA-00284: recovery session still in progress
原因：An error during recovery was determined to be minor enough to allow the current recovery session to continue.
解决：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
原因：UNTIL TIME was not followed by a string constant for the time.
解决：Enter the time enclosed in single quotation marks.
ORA-00286: no members available, or no member contains valid data
原因：None of the members of a redo log file group are available, or the available members do not contain complete data.
解决：If a member is temporarily offline, attempt to make it available. Make sure that the correct filenames 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
原因：The given change number does not appear in any of the online redo logs for the given thread.
解决：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
原因：During media recovery, a new log is not required but the continuation command is necessary to do a checkpoint and report errors.
解决：Type ALTER DATABASE RECOVER CONTINUE and recovery will resume.
ORA-00289: suggestion : string
原因：This message reports the next redo log filename 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.
解决：Consider using this filename for the next log needed for recovery.
ORA-00290: operating system archival error occurred. See error below
原因：While attempting to archive to a redo log file, the server encountered an unexpected operating system error.
解决：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
原因：A recovery command was specified incorrectly. The PARALLEL option must be followed by a numeric argument that specifies the degree of parallelism.
解决：Re-enter the command with a numeric argument specifying the degree of parallelism desired.
ORA-00292: parallel recovery feature not installed
原因：A parallel recovery was requested when the parallel recovery option is not installed.
解决：Delete the PARALLEL clause from the RECOVER command. Also, delete the RECOVERY_PARALLELISM parameter in the initialization file.
ORA-00293: control file out of sync with redo log
原因：The redo log file and control file are out of sync because a non-current controle file was specified when the instance was started.
解决：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"
原因：An invalid format specifier was found in the LOG_ARCHIVE_FORMAT initialization parameter. The only characters permitted following the % symbol are s, S, t, and T.
解决：Correct the initialization file and re-start the instance.
ORA-00295: datafile/tempfile number string is invalid, must be between 1 and string
原因：An invalid file number was specified.
解决：Specify a valid datafile or tempfile number and retry the operation.
ORA-00296: maximum number of files (string) exceeded for RECOVER DA TAFILE LIST
原因：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.
解决：Re-start the instance with a higher value for DB_FILES.
ORA-00297: must specify RECOVER DA TAFILE LIST before RECOVER DATAFILE START 原因：The RECOVER DA TAFILE 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 DA TAFILE LIST before RECOVER DATAFILE START.
解决：Contact customer support
ORA-00298: Missing or invalid attribute value
原因：A non-zero integer value is required when the following keyword attributes are specified: TIMEOUT, EXPIRE, DELAY, NEXT
解决：Correct the syntax and retry the command.
ORA-00299: must use file-level media recovery on data file string
原因：The control file does not contain an entry for this file, so block media recovery cannot be done.
解决：Restore the data file and perform file-level media recovery.
ORA-00300: illegal redo log block size string specified - exceeds limit of string
原因：The specified block size of the redo log is greater than the maximum block size for the operating system.
解决：Create the redo log on a device with a smaller block size
ORA-00301: error in adding log file "string" - file cannot be created
原因：The creation of the redo log file failed
解决：Check: 1) there is enough storage space on the device 2) the name of the file is valid 3) the device is online 4) an IO 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
原因：The maximum number of redo log files has been exceeded.
解决：Use the CREATE CONTROLFILE command with a larger value for MAXLOGFILES if the compatibility is lower than 10.2.0. Otherwise, allocate more storage space for the control file. ORA-00303: cannot process Parallel Redo
原因：A redo log containing Parallel Redo has been detected. The current Oracle release cannot process this format of redo.
解决：Use a later release that supports Parallel Redo. to process this log.
ORA-00304: requested INSTANCE_NUMBER is busy
原因：An instance tried to start by using a value of the initialization parameter INSTANCE_NUMBER that is already in use.
解决：Either a) specify another INSTANCE_NUMBER, b) shut down the running instance with this number c) wait for instance recovery to complete on the instance with this number.
ORA-00305: log string of thread string inconsistent; belongs to another database
原因：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.
解决：Specify the correct redo log file, then retry the operation.
ORA-00306: limit of string instances in this database
原因：Starting this instance would exceed the maximum number of instances allowed for this database. This message occurs only with STARTUP shared and multiple instances.
解决：You cannot start more than the lower of a) port-specific limit as to the number of instances b) the number of instances specified at create-database time
ORA-00307: requested INSTANCE_NUMBER out of range, maximum is string
原因：The initialization parameter INSTANCE_NUMBER specified a number that was out of range.
解决：Change INSTANCE_NUMBER to a valid range and restart the instance. The minimum value is one and the maximum value is the lower of the operating system-specific maximum or the MAXINSTANCES option specified in the CREATE DA TABASE statement. See also your operating system-specific Oracle documentation.
ORA-00308: cannot open archived log "string"
原因：The system cannot access a required archived redo log file.
解决：Check that the off line 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
原因：The system cannot access the archived redo log because it belongs to another database.
解决：Specify the correct redo log file, then retry the operation.
ORA-00310: archived log contains sequence string; sequence string required
原因：The archived log is out of sequence, probably because it is corrupted or the wrong redo log