Cause: Cannot open the control file. Action: Check to make sure the control file exists and is not locked by some other program.

Cause: The archiver process received an error while trying to archive a redo log. If the problem is not resolved soon, the database will stop executing transactions. The most likely cause of this message is the destination device is out of space to store the redo log file. Action: Check archiver trace file for a…

Cause: Failed to create a new filename record entry in the control file because the maximum allowed filename records have been allocated and are in use. Action: Free up controlfile filename section entries by dropping unwanted tablespaces/datafiles/redofiles.

Cause: The current process did not release the control file enqueue within the maximum allowed time. Action: Reissue any commands that failed and contact Oracle Support Services with the incident information.

Cause: An attempt to invoke cfileMakeAndUseSnapshot with a currently mounted control file that was newly created with CREATE CONTROLFILE was made. Action: Mount a current control file and retry the operation.

Cause: A snapshot or copy control file of the specified name could not be found or opened during an invocation of cfileUseSnapshot, cfileMakeAndUseSnapshot, or cfileUseCopy. Action: Re-create the snapshot or copy control file using cfileMakeAndUseSnapshot or ALTER DATABASE BACKUP CONTROLFILE, respectively.

Cause: An attempt was made to expand or shrink the control file by calling cfileResizeSection using an invalid value for the RECORD_TYPE parameter. Action: Use a value for the RECORD_TYPE parameter that specifies a valid record type other than type 0 (valid range is 1-16).

Cause: The block size as stored in the control file header is different from the value of the initialization parameter DB_BLOCK_SIZE. This might be due to an incorrect setting of DB_BLOCK_SIZE, or else might indicate that the control file has either been corrupted or belongs to a different database. Action: Restore a good copy of…

Cause: A disk I/O failure was detected on writing 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: To reuse a control file, it must be the same size as the one previously used. Action: Either do not specify REUSE, or specify a matching combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses in the CREATE DATABASE or CREATE CONTROLFILE statement.