With properly maintained coorespondence "rapidclone" can be used on all tiers to keep the software and configuration in sync. Jerry Ireland and I are presenting a paper about this at Collaborate 09 (but we are not addressing the mechanics of the standby database itself at all) Fortunately since the standby keeps the same database name and the host name dependencies for each tier are translated in the rapidclone process the only catch is to make sure you don't overwrite the destination database that is your standby in the rapidclone process. So the short answer to your question is that the "rapidclone" processes allow you to keep the standby site matching the primary by proper use of "preclone" and later "autoconfig." (For dinosaurs it used to be much easier before name dependencies were allowed to be scattered myriad places beginning about 1995 with the changes announced at the Nashville OAUG meeting that nearly caused a riot. Those who realized that this was the start of an endless treadmill of forced incremental patching ala the large corporation convicted of anti-trust violations were pretty upset. When the presenter responded to a question about cloning with "Why would you want to clone an installation?" that is when the near riot ensued. Not a red letter day in the history or Oracle Applications.) _____ From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Kumar Madduri Sent: Thursday, March 26, 2009 7:31 PM To: Oracle-L@xxxxxxxxxxxxx Subject: Re: standby at remote site Clarification: In case of oracle applications, the additional steps would be to configure these middle tiers to point to the new "primary" by running autoconfig by changing the context_file for db related entries to the new "primary". Are there any other changes? But this assumes that your application tiers are not on the standby site. But if the application tiers are on the standby site as well. How do you manage the appl_top and other code trees. Similar to Data guard for db tier, how is the app tier synched other than a periodic rsync from primary to standby site. Is this the only way or is there any other way to achieve this as well? Thank you - Kumar On Thu, Mar 26, 2009 at 2:58 PM, Jack van Zanen <jack@xxxxxxxxxxxx> wrote: Hi Also gives the opportunity to run the Standby on primary an hour or so behind in the apply so you can easily recover when a user goes "Oops, silly me just deleted the record without the where clause and now table is empty. Let's phone our DBA and see if he can save my butt" Jack 2009/3/27 Niall Litchfield <niall.litchfield@xxxxxxxxx> In addition to jason's remarks i'd add that you'll want to be clear about how switchover and failover will happen and how the choice of new primary is made. Then test at least switchover and resultant application and interface etc performance. On 3/26/09, Jason Heinrich <jheinrichdba@xxxxxxxxx> wrote: > This is a fairly common DR scenario. I would just make sure that you have > sufficient bandwidth between the sites to ship the logs. See > http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10gR2_DataGu ardNetworkBestPractices.pdffor > some tips on optimizing the redo transport. > > -- > Jason Heinrich > > > On Thu, Mar 26, 2009 at 11:08 AM, Kumar Madduri <ksmadduri@xxxxxxxxx> wrote: > >> Hi List: >> We have a standby here but we want to create an additional standby at a >> remote location. So 2 standbys. One is in the same location (not the same >> server) another in a remote location- this would be the DR site. Wanted >> to >> get the experience of the list and any areas to watch out for in this kind >> of setup. >> >> Primary is 2 node rac. Standy is single instance; DB is on 10.2.0.4 >> >> Thank you >> Kumar >> > -- Sent from Google Mail for mobile | mobile.google.com <http://mobile.google.com/> Niall Litchfield Oracle DBA http://www.orawin.info <http://www.orawin.info/> -- //www.freelists.org/webpage/oracle-l -- Jack van Zanen ------------------------- This e-mail and any attachments may contain confidential material for the sole use of the intended recipient. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of this e-mail or any attachment is prohibited. If you have received this e-mail in error, please contact the sender and delete all copies. Thank you for your cooperation