ORA-01207 old control File complete solution

This error is one of the most common errors in Oracle DB, causing many reasons, but the main reason is that the database server suddenly drops power and then restarts the start database error.
The reason for this problem is that the control file records the DB information is too old, causing the database to start detection inconsistent.
The control file records all the information of the whole database, including data files, log files and so on.

So why is it that the database information that controls the file record is too old for a simple reason: according to the Oracle DB operation principle, the database will update the control files continuously during the operation due to the checkpoint, while the database will update the contents of the control files during shutdown and restart. However, a sudden drop of power from the database server can cause the current DB information to not be updated to the control file in a timely manner, and this error occurs when the Oracle detects that the control file and other file information are consistent.

Solution:
1. Sql>alter database backup Controlfile to trace as ' c:\RebuildCtl.sql ';
The database has changed.

2. Sql>shutdown immediate If the database is open, close
ORA-01109: Database not open
Database has been unloaded

3. Sql>startup Nomount;
The ORACLE routine has started.
Total System Global area 105979576 bytes
Fixed Size 454328 bytes
Variable Size 79691776 bytes
Database buffers 25165824 bytes
Redo buffers 667648 bytes

4. Open according to the prompts, edit the C:\RebuildCtl.sql file generated in step 1th as follows;
# The following commands'll create a new control file and use it
# to open the database.
# Data used by the recovery manager would be lost. Additional logs May
# is required for media recovery of offline data files. Use this
# only if the "current version of" All online logs are available.
#STARTUP Nomount
CREATE controlfile Reuse DATABASE "ORCL" Noresetlogs Noarchivelog
---SET STANDBY to maximize performance
Maxlogfiles 5
Maxlogmembers 3
Maxdatafiles 100
Maxinstances 1
Maxloghistory 226
LOGFILE
GROUP 1 ' D:\ORACLE\ORADATA\ORCL\REDO01. LOG ' SIZE 100M,
GROUP 2 ' D:\ORACLE\ORADATA\ORCL\REDO02. LOG ' SIZE 100M,
GROUP 3 ' D:\ORACLE\ORADATA\ORCL\REDO03. LOG ' SIZE 100M
--STANDBY LOGFILE
DataFile
' D:\ORACLE\ORADATA\ORCL\SYSTEM01. DBF ',
' D:\ORACLE\ORADATA\ORCL\UNDOTBS01. DBF ',
' D:\ORACLE\ORADATA\ORCL\INDX01. DBF ',
' D:\ORACLE\ORADATA\ORCL\TOOLS01. DBF ',
' D:\ORACLE\ORADATA\ORCL\USERS01. DBF '
CHARACTER SET Us7ascii
;
# Recovery is required if any of the datafiles are restored backups,
# or if the last shutdown is not normal or immediate.

RECOVER DATABASE

# Database can now is opened normally.

ALTER DATABASE OPEN;

# Commands to add tempfiles to temporary tablespaces.
# Online Tempfiles have complete space information.
# Other tempfiles may require adjustment.

ALTER tablespace TEMP ADD tempfile ' D:\ORACLE\ORADATA\ORCL\TEMP01. DBF ' reuse;

# End of Tempfile additions.

5. Run the SQL file above,

Sql> @c:\rebuildctl.sql

Complete the Rebuild control file,

Successfully opened the database.