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