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

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.

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.