ORA-01207: file is more recent than controlfile – old controlfile

1) dump controlfile to trace

SQL> alter database backup controlfile to trace as '/home/oracle/controlfile.sql';

2) startup database nomount

SQL> startup nomount

3) create the control file

SQL> @/home/oracle/controlfile.sql
Control file created.

SQL> recover database using backup controlfile;

SQL> recover database using backup controlfile ;
ORA-00279: change 1904510 generated at 12/11/2020 11:12:13 needed for thread 1
ORA-00289: suggestion : +DATA
ORA-00280: change 1904510 for thread 1 is in sequence #1453

Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
+DATA/MSDB/onlinelog/group_1.224.492141654
ORA-00310: archived log contains sequence 24; sequence 1453 required
ORA-00334: archived log: '+DATA/MSDB/onlinelog/group_1.224.492141654'

Follow these Steps if you have to recreate the Physical Standby Controlfile:

1. Stop Managed Recovery Process on the Standby Database (if still running):

SQL> alter database recover managed standby database cancel;

2. Shutdown the Standby Database:

SQL> shutdown immediate;

3. Connect to the Primary Database as SYS:

SQL> connect sys/<Password>@<Primary> as sysdba

4. Create a new Physical Standby Controlfile from the Primary:

SQL> alter database create standby controlfile as '<File-Specification>';

5. Copy the new created Standby Controlfile to the Standby Database using OS-Tools (eg. cp or ftp) and replace the current Standby Controlfile with the new created one.

6. Mount the Standby Database with the new Standby Controlfile:

Oracle 8i and 9i (8.x – 9.x):

SQL> startup nomount
SQL> alter database mount standby database;

Oracle 10g and 11g (10.x – 11.x):

SQL> startup mount

7. If the File-Structure is different between Primary and Standby Database,  you could either rename the File-Location(s) in the new Standby Controlfile:

SQL> alter database rename file '<old Filespecification or file#>' to '<new Filespecification>';