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

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 correct file or reset logs.

ORA-00340: IO error processing online log string of thread string

ORA-00340: IO error processing online log string of thread string

Cause: An IO error occurred on the named online log.

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

ORA-00339: archived log does not contain any redo

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-00338: log string of thread string is more recent than control file

ORA-00338: log string of thread string is more recent than control file

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-00337: log file string does not exist and no size specified

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-00336: log file size string blocks is less than minimum string blocks

ORA-00336: log file size string blocks is less than minimum string blocks

Cause: The log file size as specified in create database is too small.

Action: Increase the log file size.

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

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

Cause: Reporting filename for details of another error

Action: See associated error messages

ORA-00334: archived log: string

ORA-00334: archived log: string

Cause: Reporting filename for details of another error

Action: See associated error messages

ORA-00333: redo log read error block string count string

ORA-00333: redo log read error block string count string

Cause: An IO error occurred while reading the log described in the accompanying error.

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

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

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-00331: log version string incompatible with ORACLE version string

ORA-00331: log version string incompatible with ORACLE version string

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

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

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

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-00329: archived log begins at change string, need change string

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-00328: archived log ends at change string, need later change string

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. Can not use the log for applying redo.

Action: Find correct archived log.

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

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 operator or operating system error.

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

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

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. Can not yet use the log for applying redo.

Action: Find correct archived log.

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

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

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

Action: Find correct archived log.

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

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 a untranslated name that yields a shorter translated name.

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

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

Cause: Attempt to open 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 then retry open.

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

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

Cause: Check of log file header at database open found that an online log appears to be an incorrectly restored backup.

Action: Restore correct file or reset logs.

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

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

Cause: Cannot write to the log file.

Action: Restore the access to the file.

ORA-00320: cannot read file header from log string of thread string

ORA-00320: cannot read file header from log string of thread string

Cause: The file is not available.

Action: Restore the log file.

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

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

Cause: Check of log file header at database open found that an online log has log reset data that is different from the control file. The log is probably an incorrectly restored backup.

Action: Restore correct file or reset logs.

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

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

Cause: On header read the file size indicated in the control file did not match the file size contained in the log file.

Action: Restore correct file or reset logs.

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

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.

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

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 correct version of log or reset logs.

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

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 correct version of log or reset logs.

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

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 correct version of log or reset logs.

ORA-00313: open failed for members of log group string of thread string

ORA-00313: open failed for members of log group string of thread string

Cause: The online log cannot be opened. May not be able to find file.

Action: See accompanying errors and make log available.

ORA-00312: online log string thread string: string

ORA-00312: online log string thread string: string

Cause: This message reports the filename for details of another message.

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

ORA-00311: cannot read header from archived log

ORA-00311: cannot read header from archived log

Cause: An I or 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-00310: archived log contains sequence string; sequence string required

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 filename was specified

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

ORA-00309: log belongs to wrong database

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, then retry the operation.

ORA-00308: cannot open archived log string

ORA-00308: cannot open archived log string

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

Action: 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-00307: requested INSTANCE_NUMBER out of range, maximum is string

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 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-00306: limit of string instances in this database

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 a) port-specific limit as to the number of instances b) the number of instances specified at create-database time

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

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, then retry the operation.

ORA-00304: requested INSTANCE_NUMBER is busy

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 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-00303: cannot process Parallel Redo

ORA-00303: cannot process Parallel Redo

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

Action: Use a later release that supports Parallel Redo. to process this log.

ORA-00302: limit of string logs exceeded

ORA-00302: limit of string logs exceeded

Cause: The maximum number of redo log files has been exceeded.

Action: 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-00301: error in adding log file string - file cannot be created

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

Cause: The creation of the redo log file failed

Action: 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-00300: illegal redo log block size string specified - exceeds limit of string

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-00299: must use file-level media recovery on data file string

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

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

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

ORA-00298: Missing or invalid attribute value

ORA-00298: Missing or invalid attribute value

Cause: A non-zero integer value is required when the following keyword attributes are specified: TIMEOUT, EXPIRE, DELAY, NEXT

Action: Correct the syntax and retry the command.

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

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 customer support

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

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: Re-start the instance with a higher value for DB_FILES.

ORA-00295: datafile or tempfile number string is invalid, must be between 1 and string

ORA-00295: datafile or tempfile number string is invalid, must be between 1 and string

Cause: An invalid file number was specified.

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

ORA-00294: invalid archivelog format specifier string

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 following the % symbol are s, S, t, and T.

Action: Correct the initialization file and re-start the instance.

ORA-00293: control file out of sync with redo log

ORA-00293: control file out of sync with redo log

Cause: The redo log file and control file are out of sync because a non-current controle 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-00292: parallel recovery feature not installed

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-00291: numeric value required for PARALLEL option

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-00290: operating system archival error occurred. See error below

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-00289: suggestion : string

ORA-00289: suggestion : string

Cause: 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.

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

ORA-00288: to continue recovery type ALTER DATABASE RECOVER CONTINUE

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-00287: specified change number string not found in thread string

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-00286: no members available, or no member contains valid data

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 filenames are being used, especially if the redo log file is being accessed from a remote location.

ORA-00285: TIME not given as a string constant

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-00284: recovery session still in progress

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-00283: recovery session canceled due to errors

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-00282: UPI string call not supported, use ALTER DATABASE RECOVER

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.