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.
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.
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
Cause: The archived log is corrupted or for another thread. Can not use the log for applying redo. Action: Find correct archived log.
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.
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.
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…
Cause: The archived log is not the correct log. A later log is needed. Action: Restore the correct log file.
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.
Cause: The archived log is out of sequence, probably because it is corrupted or the wrong redo log filename was specified during recovery. Action: Specify the correct redo log file; then retry the ope