Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

Oracle Data Guard Switchover

Posted on 2011-09-12
8
Medium Priority
?
514 Views
Last Modified: 2012-06-27
I have a multiple point question looking for confirmation of the research I've done.  I am about to do a switchover from a primary db to a standby db because of updates that need to be applied to the server.  It seems that I have redo apply running on the standby.  I have also found the commands to switch the primary to standby and standby to primary.  My main concern is at this point is that once the reboot occurs and we bring up the current primary it will be the standby and this will have to be changed soon thereafter.  How do i know if the current primary will be in sync and have all current data applied before make the second switchover and if it is not how do you go about ensuring that this will happen in timely manner?  Also do I need to make sure the services currently running on the standby are running on the current primary, i.e. redo apply so that when it comes up in standby it will work correctly?

Please excuse my ignorance but I have only worked with standalone before and I'm having to learn this on the job and cannot afford to have down time due to the importance of the data being needed.
0
Comment
Question by:geleman
  • 4
  • 3
8 Comments
 
LVL 48

Expert Comment

by:schwertner
ID: 36522849
I think the only clean way to do this is to stop the primary and to switch the standby from "managed recovery mode" to normal database mode.

After that the best way will be to install standby on the place of the former primary and to direct the archived redo logs from the former standby to the former primary.

Looking in the net there are some articles that can give you details of the switchover.
0
 
LVL 35

Expert Comment

by:johnsone
ID: 36522898
Have you checked the documentation on switchovers:

http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/role_management.htm#i1033702

It is pretty detailed.

Keep in mind that a switchover and a failover are 2 different things.  We are really looking at a switchover here.  Done the way the documentation describes, there is no data loss during a switchover.  Oracle makes sure that everything is applied on both sides.  I would set it all up in a test environment to get yourself comfortable with the commands and switching back and forth.
0
 
LVL 35

Expert Comment

by:johnsone
ID: 36522912
What schwertner is describing is a failover.
0
Veeam Task Manager for Hyper-V

Task Manager for Hyper-V provides critical information that allows you to monitor Hyper-V performance by displaying real-time views of CPU and memory at the individual VM-level, so you can quickly identify which VMs are using host resources.

 

Author Comment

by:geleman
ID: 36523157
johnsone:

I can see that if doing the switchover and the server staying up how there wouldn't be any data loss be once we do the switch over we have to immediately reboot the server.  So there will be some difference between the 2 when I bring the db back up after the reboot.  How do I ensure the data is the same once I bring it back up and do the switchover again to make the original primary the primary again.  This is only a temporary situation for updates only so it will need to be switched back as soon as I know the data is updated and the same at that point.
0
 
LVL 35

Expert Comment

by:johnsone
ID: 36523241
Once you bring up the old primary (now designated a standby), you would need to start the managed recovery there and make sure that all the logs got across from the down time.  Once they were across and applied, you could do the switchover again to take things back to the way they were.
0
 

Author Comment

by:geleman
ID: 36524760
johnsone:

One last question.  If all sessions are killed and and not new logins are issued for both databases is it necessary for a switchover if there will be no new data coming?
0
 
LVL 35

Accepted Solution

by:
johnsone earned 2000 total points
ID: 36525083
That depends.  Your original question says you are doing a switchover because "updates that need to be applied to the server".  That would imply to me that the database and server need to be shut down during that time.

If you do not do a switchover, your database will not be accessible while it is down.  If you can take that kind of downtime, then leave everything down and don't do the switchover.

The switchover would only be necessary if you wanted everything to run normally during your downtime.  Of course, there is still down time to do the switchover and the to switchover again to bring it back, but that would be less than your total maintenance downtime.
0
 

Author Closing Comment

by:geleman
ID: 36525113
I appreciate all the help you answered everything I needed to know and was not sure about.  Thank you very much.
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article started out as an Experts-Exchange question, which then grew into a quick tip to go along with an IOUG presentation for the Collaborate confernce and then later grew again into a full blown article with expanded functionality and legacy…
Truncate is a DDL Command where as Delete is a DML Command. Both will delete data from table, but what is the difference between these below statements truncate table <table_name> ?? delete from <table_name> ?? The first command cannot be …
Via a live example show how to connect to RMAN, make basic configuration settings changes and then take a backup of a demo database
This video explains what a user managed backup is and shows how to take one, providing a couple of simple example scripts.

927 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question