This post is the continuation of the previous Data Guard, Physical Standby Implementation, Step by Step
This time I did focus on configuring Data Guard Broker, the Observer and implement Switchover from the Primary to the Standby and back. The step by step instructions are contained on this document: Configuration of 10g Data Guard Broker and Observer for Switchover
This configuration do require a third server to run from it the Observer process on the background. It proved to be more efficient than other hardware cluster solutions in terms of the time required to switchover, about 5 minutes.
The best solution is to upgrade the configuration to RAC + Data Guard, that provides maximum protection and availability.
Comments (7)
Great Stuff.
Just a suggestion
Go over a STEP by STEP applying a "patch or patch set" to a dataguard systems. look at metalink note : 187242. I think it is "lacking" information about systems using a DG broker..
anyway..great stuff
Posted by Patrick | October 2, 2007 5:56 PM
Posted on October 2, 2007 17:56
Nice!
Posted by mdinh | October 2, 2007 6:11 PM
Posted on October 2, 2007 18:11
Hi, thanks for sharing info on standby DGMGRL configuration, we are going to using FF feature of DG but have one security issue
to start observer we need to supply uid with sysdba and password in clear which is security concern.
any idea how can we supply encrypted password and start observer? something similar to rexp?
thanks
Manoj
Posted by Manoj Bajaj | October 11, 2007 11:45 PM
Posted on October 11, 2007 23:45
Hi,
Nice way to give understanding about DataGuard Broker. I am not much aware about the broker. so can u pl. let me know that whaterver the parameter we are setting for primary and standby database and the requried file configuration is done by SQL prompt only or with in broker this is available?
- we can use broker just for easiest way to failover and switchover...
give me some ideas...
Regards,
Suchi
Posted by suchi | October 16, 2007 8:42 AM
Posted on October 16, 2007 08:42
Thanks for a wonderful post.
I indeed used it to install my Oracle Dataguard on Solaris.
My next task is to test the switchover and failover scenarios without using the Broker. I mean just using sqlplus
Can you pls provide me with simple instructions to do these 4 scenarios
1) Switchover primary to standby and standby to primary
2) Once the scheduled maintenance on (originally) primary and now standby, Restore their original roles, i.e Make the status of the servers as it was before the switchover in step 1)
Failover scenarios
1) Failover Primary , check data appearing in Standby ( now promoted to primary)
2) Once the Dead Primary is restored, Restore their original roles, i.e Make the status of the servers as it was before the switchover in step 1)
Thanks in advance
Regards
Dharmesh
Posted by Dharmesh Shah | November 16, 2007 8:53 AM
Posted on November 16, 2007 08:53
Hi Alejandro,
I am following all the steps on this document and I would like to comment on the GLOBAL_DBNAME=whiteowl_DGMGRL setting on the LISTENER.ORA file. I tried to follow that setting but I can't get it to work, instead I used whiteowl_DGB and blackowl_XPT for the GLOBAL_DBNAME on the LISTENER.ORA and everything is working fine. Any idea why?
Thanks in advance.
Regards,
Lloyd
Posted by Lloyd Tago | February 28, 2008 4:56 PM
Posted on February 28, 2008 16:56
make sure that you login as this
DGMGRL> connect sys/@whiteowl
GLOBAL_DBNAME=whiteowl_DGMGRL setting on the LISTENER.ORA file
SERVICE_NAME = whiteowl_DGMGRL) setting on the TNSNAMES.ORA file
ALTER SYSTEM SET LOCAL_LISTENER='LISTENER_VMRACTEST' SCOPE=BOTH;
when switchover or failover to complete oeration without errors
Posted by ahmed | July 7, 2009 3:09 AM
Posted on July 7, 2009 03:09