Standby controlfile SCN ahead of datafile SCN

Question

Hello,
Is there any quick fix to the scenario where the standby side controlfile SCN has gone ahead of the datafile SCN. All the archives are getting shipped to the standby side, but any attempt to start the MRP fails with -
Recovery interrupted!
Standby recovery stopped due to failure in applying recovery marker (opcode 17.4).
Datafiles are recovered to a consistent state at change 12679713219897 but controlfile is ahead at change 12679713219906.
DB (stand-alone): 11.2.0.2
Platform: Sun SPARC
Thanks
aBBy

Answer 1

Is there any quick fix to the scenario where the standby side controlfile SCN has gone ahead of the datafile SCN. All the archives are getting shipped to the standby side, but any attempt to start the MRP fails with -
Recovery interrupted!
Standby recovery stopped due to failure in applying recovery marker (opcode 17.4).
Datafiles are recovered to a consistent state at change 12679713219897 but controlfile is ahead at change 12679713219906.
Are you trying to perform Manual recovery from SQL? like recover standby database?
Even if controlfile is new and datafiles are older, still you should able to perform recovery , But this will be a valid database to open when SCN's are in SYNC.
SO perform recovery automated and then check synchronization.
SQL> alter database recover managed standby database disconnect from session;
Refer alert log file until it waits as " Media recovery waiting for thread# <no> sequence# <>"
Then, check SYNC as follows
Primary:-
SQL> select thread#, max(sequence#) from v$archived_log group by thread#;
Standby:-
SQL> select thread#, max(sequence#) from v$archived_log group by thread#;
SQL> select thread#, max(sequence#) from v$archived_log where applied='YES' group by thread#;
Also you can try option of recreating standby controlfile as below from primary
SQL> alter database create standby controlfile as 'loation';
& restore it in standby database.