Failedover Primary creeping to archive a log file which somehow left because of disk full condition
edited Nov 26, 2009 10:22PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 3 commentsAnswered
We have one Primary (A) and one Standby database (B) DataGuard setup.
now when B was operating in standby mode, it was failing to archive a particular logfile (#1771) coming from A because of disk full condition. User ignored disk full error and did failover immediate to B. Failover succeeded.
Now B has become Primary; this database is working fine. However, B is still getting that old archival error (as below for #1771). Local archival is working fine and sequence number has progressed to 2178. Still, database is looking for archiving 1771.
How can i get rid of this problem, alert logfile is full of the entries like:
now when B was operating in standby mode, it was failing to archive a particular logfile (#1771) coming from A because of disk full condition. User ignored disk full error and did failover immediate to B. Failover succeeded.
Now B has become Primary; this database is working fine. However, B is still getting that old archival error (as below for #1771). Local archival is working fine and sequence number has progressed to 2178. Still, database is looking for archiving 1771.
How can i get rid of this problem, alert logfile is full of the entries like:
0