ORA-00200 Control file could not be created
Cause: It was not possible to create the control file. Action: Check that there is sufficient disk space and no conflicts in filenames and try to create the control file again.
Cause: It was not possible to create the control file. Action: Check that there is sufficient disk space and no conflicts in filenames and try to create the control file again.
Cause: Even though no parameter file was specified, the instance was started with all default values. Action: None.
Cause: The value of LARGE_POOL_SIZE is less than the value of LARGE_POOL_MIN_ALLOC. Action: Increase the value of LARGE_POOL_SIZE past the value of LARGE_POOL_MIN_ALLOC.
Cause: Attempting to do an OPEN RESETLOGS with a file that will be lost because it is offline. The file was not taken offline with the FOR DROP option. Action: Either bring the file online and recover it, or take it offline with the FOR DROP option.
Cause: Attempting to do a RESETLOGS open with a file entry in the control file that was originally created after the UNTIL time of the incomplete recovery. Allowing such an entry may hide the version of the file that is needed at this time. The file number may be in use for a different file…
Cause: The files named in the accompanying errors are backups that were made before a tablespace point in time recovery of this tablespace. They cannot be recovered to a time after the point in time recovery. Action: Restore more recent backups and recover them.
Cause: The command specifies adding more data files than can be done in one command. It is necessary to fit all the file names into one log entry, but that would make the entry too large. Action: If this is a CREATE TABLESPACE command, create with fewer files then add the other files later. If…
Cause: One or more of the files in an end backup command failed. Some other files given in the same command may have succeeded. Action: See the accompanying error messages for the reason the backups could not be ended. Any files not listed in the error messages were successful.
Cause: An attempt to make a tablespace read only found that one of its files is offline. Action: Bring the file online and retry this command.
Cause: The archived log is not the correct log. An earlier log is needed. Action: Restore the correct log file.