Cause: An inconsistent set of control files, datafiles/logfiles, and redo files was used. Action: Use a consistant set of control files, datafiles/logfiles, and redo log files. That is, all the files must be for the same database and from the same time period.

Cause: The mount ID in the control file is not the same as the mount ID in the control file used by the first instance to mount this database. The control files are for the same database but they are not the same files. Most likely one instance is using a backup control file. Action:…

Cause: A disk I/O failure was detected on reading the control file. Action: Check if the disk is online, if it is not, bring it online and try a warm start again. If it is online, then you need to recover the disk.

Cause: The control file created by release 8.0.2 was missing some record types. These record types are automatically added by resizing the control file during mount. The resize has failed. Action: Look in the alert log for the reason that the resize has failed. If indicated in the alert log, give the control file more…

Cause: Failed to create a control file backup because concurrent control file backup operation was in progress. Action: Retry backup creation later.

Cause: Attempting to invoke cfileSetSnapshotName, cfileMakeAndUseSnapshot, or cfileUseSnapshot when the currently mounted control file is a backup control file. Action: Mount a current control file and 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 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…

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.

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.