The scenario goes like this:
The instance was in nomount stage and was unable to mount the database.
Checked the uptime, and found that the server was rebooted some 5 minutes ago, and the instance tried to come up automatically but failed to mount the database.
Checked the alert log and found the following error:
ORA-214 signaled during: ALTER DATABASE MOUNT…
Made a quick searched about ORA-00214 and it was about mismatched control files. It was probably due to the fact that control files got out of sync as the not-so-graceful reboot of the server was done without first cleanly shutting down the database.
This is what doc says:
ORA-00214: control file “string” version string inconsistent with file “string” version string.
Cause: An inconsistent set of control files, datafiles/logfiles, and redo files was used.
Action: Use a consistent set of control files, datafiles/logfiles, and redo log files. That is, all the files must be for the same database and from the same time period.
checked the locations of control files:
SQL> select instance_name,status from v$instance;
SQL> show parameter control_files
NAME TYPE VALUE
—- —- —-
control_files string /u01/app/oracle/oradata/ORCL/control01.ctl, /u01/app/oracle/oradata/ORCL/control02.ctl,/data/oradata/ORCL/control03.ctl
Checked which control files are different. Here having odd numbers of control files is a life saver, because we have a good chance of finding the even number of control files that match and can determine which one is the one gone awry.[oracle@mytest ORCL]$ diff /u01/app/oracle/oradata/ORCL/control01.ctl /u01/app/oracle/oradata/ORCL/control02.ctl [oracle@mytest ORCL]$ diff /u01/app/oracle/oradata/ORCL/control01.ctl /data/oradata/ORCL/control03.ctl
Binary files /u01/app/oracle/oradata/ORCL/control01.ctl and /data/oradata/ORCL/control03.ctl differ [oracle@mytest ORCL]$ diff /u01/app/oracle/oradata/ORCL/control02.ctl /data/oradata/ORCL/control03.ctl
Binary files /u01/app/oracle/oradata/ORCL/control02.ctl and /data/oradata/ORCL/control03.ctl differ
Confirmed yes, the control03.ctl is the bad one.
Shutdown the instance.
Replace the bad control03.ctl with the good copy from either control01.ctl or control02.ctl, and then start the instance.
It should be all good.
Interested in working with Fahd? Schedule a tech call.