Home » Server Options » Data Guard » Failover didn't quite work... what am I missing?
Failover didn't quite work... what am I missing? [message #130974] Wed, 03 August 2005 11:56 Go to next message
eAddict
Messages: 12
Registered: May 2005
Location: St Louis, MO
Junior Member
I wanted to test the standby as a primary so I did the following. This is a TEST environment so I had to kludge a few things.

1. On the PRIMARY
alter system set log_archive_dest_state_2='defer';
2. On the STANDBY
Modified the /etc/hosts to invalidate the primary address
to simulate a fail of the primary
3. On the STANDBY
alter database set standby database to maximize performance;
alter database recover managed standby database finish skip standby logfile;
alter database commit to switchover to primary;

Now on my NEW PRIMARY I get:
SQL> select switchover_status
2 from v$database;

SWITCHOVER_STATUS
------------------
SESSIONS ACTIVE

And in the alert log:
Wed Aug 3 11:55:23 2005
RFS: Possible network disconnect with primary database
RFS: Destination database mount ID mismatch [0x528f2395:0x5290b4a8]
RFS: Not using real application clusters

What did I miss? Thanks!
Vince
Re: Failover didn't quite work... what am I missing? [message #131357 is a reply to message #130974] Fri, 05 August 2005 09:37 Go to previous message
eAddict
Messages: 12
Registered: May 2005
Location: St Louis, MO
Junior Member
Fixed: Seems when the unix admin simulated a 'crash' by making the IP invalid for the primary server so the standby couldn't see it - he forgot to do it the other way. So the real primary server kept trying to send archive logs thus starting an RFS process. Once I put the send archive logs into defer the RFS process died and the standby came up OK.
Previous Topic: physical standby and redos log
Next Topic: Unable to create stby database through data guard.
Goto Forum:
  


Current Time: Fri Dec 03 23:37:40 CST 2021