Primary DB slow down when redo transport services starts
edited Jul 22, 2013 6:58AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 2 commentsAnswered
Dear All,
We are running data guard set up with one physical standby database, primary is also single instance db. Unfortunately our standby database remains down due to some reasons for couple of days, hence lag behind the primary database. Now whenever I start standby database, listener and media recovery, application users starts complaining about slow database performance. Data guard is not configured with broker.
I don't want to take incremental backup from primary and restore it on standby to resolve archivelog gap. Can anyone please tell me how to recover from this situation?
Operating System: RHEL 5.3
Database: 11gr2 11.2.0.2.0 (64-bit)
We are running data guard set up with one physical standby database, primary is also single instance db. Unfortunately our standby database remains down due to some reasons for couple of days, hence lag behind the primary database. Now whenever I start standby database, listener and media recovery, application users starts complaining about slow database performance. Data guard is not configured with broker.
I don't want to take incremental backup from primary and restore it on standby to resolve archivelog gap. Can anyone please tell me how to recover from this situation?
Operating System: RHEL 5.3
Database: 11gr2 11.2.0.2.0 (64-bit)
0