Unexpected standby redo log generated during failover.
edited Jul 29, 2009 11:29PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 3 commentsAnswered ✓
Customer's data guard is configured as physical standby database.
When we failover the standby database to primary database, an unexpected standby redo log was
generated although we have created 4 groups of standby redo logs.
The alert.log files shows:
============================
RFS[6]: Possible network disconnect with primary database
Aborting archivelog file creation: /ora/PROD/archivelog/POTM/POTM_1_5524_687453733.arc
If this a network disconnect, then this archivelog will be fetched again
by GAP resolution mechanism.
Wed Jul 22 11:10:17 2009
alter database set standby database to maximize performance
Wed Jul 22 11:10:17 2009
Completed: alter database set standby database to maximize performance
Wed Jul 22 11:12:43 2009
alter database recover managed standby database finish force
generated although we have created 4 groups of standby redo logs.
The alert.log files shows:
============================
RFS[6]: Possible network disconnect with primary database
Aborting archivelog file creation: /ora/PROD/archivelog/POTM/POTM_1_5524_687453733.arc
If this a network disconnect, then this archivelog will be fetched again
by GAP resolution mechanism.
Wed Jul 22 11:10:17 2009
alter database set standby database to maximize performance
Wed Jul 22 11:10:17 2009
Completed: alter database set standby database to maximize performance
Wed Jul 22 11:12:43 2009
alter database recover managed standby database finish force
0