Cause: An attempt was made to archive the current log of an open thread. This is not allowed because the redo log file may still be in use for the generation of redo entries. Action: Force a log switch in the instance where the thread is open. If no instances are open, open the database…

Cause: Failed to create a control file backup because some process signaled an error during backup creation. This is likely caused by the backup target being on a local file system so it could not be accessed by other instances. It can also be caused by other I/O errors to the backup target. Any process…

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 expand control file filename section. See alert log for more details. Action: Retry the operation after increasing disk space for controlfile expansion.

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: Concurrent update activity on a control file caused a process to read inconsistent information from the control file without a lock. Action: Retry the operation.

Cause: The attempted operation cannot be executed at this time because another process currently holds the snapshot control file enqueue. Action: Retry the operation after the concurrent operation that is holding the snapshot control file enqueue terminates.

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

Cause: An invocation of CREATE DATABASE or CREATE CONTROLFILE was executed specifying a combination of parameters that would require the control file size in blocks to exceed the maximum allowable value. Action: In the case of CREATE DATABASE or CREATE CONTROLFILE, use a different combination of MAXDATAFILES, MAXLOGFILES, MAXLOGMEMBERS, MAXLOGHISTORY, and MAXINSTANCES clauses.

Cause: An Oracle7 to Oracle8 convert file contains invalid data or was created with an different version of the migration utility. This error can also be caused by incorrect ORACLE_HOME environment variable when ALTER DATABASE CONVERT command is issued. Action: Use a correct version of the convert file or regenerate it with the migration utility.…