ORA-16432
inconsistent set of logs applied at a standby database
Cause
Redo apply stopped because it detected an inconsistency in the progression of the SCNs. If this database is a bystander standby database, this is most likely due to a failover operation in which incompatible logs were applied from the old and new primary databases.
Action
Determine the STANDBY_BECAME_PRIMARY_SCN by selecting it from V$DATABASE on the new primary database. Then, flashback the target database to this SCN and use RMAN to delete all archive logs at or beyond this SCN. Finally, fetch all terminal end of redo (EOR) logs corresponding to the failover operation from the new primary and register all these logs at the target database. Restart redo apply.
ORA-16432
inconsistent set of logs applied at a standby database
Cause
Redo apply stopped because it detected an inconsistency in the progression of the SCNs. If this database is a bystander standby database, this is most likely due to a failover operation in which incompatible logs were applied from the old and new primary databases.
Action
Determine the STANDBY_BECAME_PRIMARY_SCN by selecting it from V$DATABASE on the new primary database. Then, flashback the target database to this SCN and use RMAN to delete all archive logs at or beyond this SCN. Finally, fetch all terminal end of redo (EOR) logs corresponding to the failover operation from the new primary and register all these logs at the target database. Restart redo apply.
ORA-16432
inconsistent set of logs applied at a standby database
Cause
Redo apply stopped because it detected an inconsistency in the progression of the SCNs. If this database is a bystander standby database, this is most likely due to a failover operation in which incompatible logs were applied from the old and new primary databases.
Action
Determine the STANDBY_BECAME_PRIMARY_SCN by selecting it from V$DATABASE on the new primary database. Then, flashback the target database to this SCN and use RMAN to delete all archive logs at or beyond this SCN. Finally, fetch all terminal end of redo (EOR) logs corresponding to the failover operation from the new primary and register all these logs at the target database. Restart redo apply.
