ORA-00266 Name of archived log file needed
Cause: During media recovery, the name of an archived redo log file was requested, but no name was entered. Action: Mount the correct redo log file and enter its name when it is requested.
Cause: During media recovery, the name of an archived redo log file was requested, but no name was entered. Action: Mount the correct redo log file and enter its name when it is requested.
Cause: An I/O error occurred while archiving a redo log file. Action: Check that the output device is still available and correct any device errors that may have occurred. Also, make certain that sufficient space for archiving is available on the output device.
Cause: The database either crashed or was shutdown with the ABORT option. Media recovery cannot be enabled because the online logs may not be sufficient to recover the current datafiles. Action: Open the database and then enter the SHUTDOWN command with the NORMAL or IMMEDIATE option.
Cause: An instance tried to start by using a value of the initialization parameter INSTANCE_NUMBER that is already in use. Action: Either a) specify another INSTANCE_NUMBER, b) shut down the running instance with this number c) wait for instance recovery to complete on the instance with this number.
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: 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.