This content has been marked as final. Show 8 replies
Wander(Brazil) wrote:Yes you can create standby RAC as well and you also can look option of dbvisit which provides high availability even in standard edition with low licensing prices
Ok, but i need to RAC physical standby with 2 nodes.
in detail you can go through with this link http://www.dbvisit.com/products/dbvisit_standby_database_for_oracle_disaster_recovery
Status Level: Newbie
Registered: Sep 23, 2005
Total Posts: 116
Total Questions: 21 (20 unresolved)
Location BH (Brazil)
Occupation Database Administrator
Please consider closing your old thread as answered.
Edited by: CKPT on May 21, 2013 10:11 AM
Creating a home grown solution seems simple but in practice it is not because you have to deal with all kinds of exceptions and Oracle errors that may occur. Remember this has to work when all else fails! This is the DR system of your company and the final defense line in case everything goes wrong to save the company. The most important asset of most companies today is the data within the database. Are you confident you will implement a 100% robust solution, that your fellow DBAs and Administrators are also comfortable with?
RAC introduces another complexity layer to the standby database scenario. Now you have multiple archive redo logs threads to deal with.
Basically you need to copy over archive logs from both threads on primary RAC into standby RAC.
As you have SE you need to extract archive logs from ASM into staging area, copy it over into standby RAC, copy it again into ASM (not necessary needed but useful when recovery instance will die) and run recover standby database on one node.
If you want to build RAC standby for your tests some simple scripts will do it for you. But if you are going to use in as DR solution I recommended to use
3rd party software - DbVisit.