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 \ 原因： 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
第16页
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 \
原因： 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 \DATABASE RECOVER LOGFILE
原因： 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
第17页
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 DATABASE 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
第18页
原因： 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 \
原因： 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 DATAFILE 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\解决： Re-start the instance with a higher value for DB_FILES.
ORA-00297: must specify RECOVER DATAFILE LIST before RECOVER DATAFILE START 原因： 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. 解决： 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
第19页
ORA-00301: error in adding log file \ 原因： 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 DATABASE statement. See also your operating system-specific Oracle documentation. ORA-00308: cannot open archived log \
原因： 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
第20页