Cause: Cannot write to the log file. Action: Restore the access to the file.

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 operation.

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

Cause: A block header corruption or checksum error was detected on reading the control file. Action: Use the CREATE CONTROLFILE or RECOVER DATABASE USING BACKUP CONTROLFILE command.

Cause: During an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot it was detected that no filename for the snapshot control file had previously been specified. Action: Specify a name for the snapshot control file by calling cfileSetSnapshotName.

Cause: The attempted operation could not be executed at this time because this process had an alternate control file open for fixed table access. Action: Retry the operation after calling cfileUseCurrent.

Cause: The snapshot control file was found to be nonexistent, corrupt, or unreadable during an invocation of cfileUseSnapshot. Action: Call cfileMakeAndUseSnapshot again (or for the first time).

Cause: The filename supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of a file that is currently part of the database. Action: Retry the operation with a different filename.

Cause: The control file was either recently created via CREATE CONTROLFILE or an incomplete recovery has been done. Thus, the datafiles in the control file and the ones in the data dictionary may not match. Action: Open the database, then retry the operation.