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

Cause: The database ID in the control file is not the same as the database ID in the control file used by the first instance to mount this database. Most likely one of the mounts used the wrong control file or there are two databases with the same name. Action: Check that the control file…

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…