Fwd: Dataguard setup at DR site
- From: Kumar Madduri <ksmadduri@xxxxxxxxx>
- To: Oracle-L@xxxxxxxxxxxxx
- Date: Sat, 25 Apr 2009 13:36:58 -0700
---------- Forwarded message ----------
From: Kumar Madduri <ksmadduri@xxxxxxxxx>
Date: Sat, Apr 25, 2009 at 1:13 PM
Subject: Re: Dataguard setup at DR site
To: asif_oracle@xxxxxxxxx
Cc: Oracle-L@xxxxxxxxxxxxx
Thank you Asif.
I read about cascading databases. But my question was, does it really
matter how the original standby is constructed (in my case I am not
using DG to build the standby). Even in this case can I cascade from
my standby to my DR standby (which I am planning to set it up using
DG). Theoritically it should be fine.
In that case, can I disable force loggin on production and enable
force logging on standby only. That way I would minimize any
performance impact.
So primary no force logging > standby (using old method of applying
redo) has force logging . THis is used as source for standby on DR
site (which will use DR).
Thank you
- Kumar
On Sat, Apr 25, 2009 at 1:03 PM, Asif Momen <asif_oracle@xxxxxxxxx> wrote:
> Dear Kumar,
>
>>> Is it possible to use the cascade standby approach in this scenario?
>
> Yes, you can have cascaded physical standby databases (I think you can go up
> to 9 cascaded standby databases)
>
>>> Based on the real world experience, how much of a performance impact
>>> would it be if force logging is enabled?
>
> The answer is, "it really depends". In an OLTP environment you would gain
> little to no whereas in a data warehouse env you may have huge gains.
> You may have nologging operations performed on the primary yet keeping your
> standby database in sync.
>
> http://download.oracle.com/docs/cd/B19306_01/server.102/b14239/scenarios.htm#i1015738
>
>
> Regards
>
> Asif Momen
> http://momendba.blogspot.com
>
>
> --- On Sat, 4/25/09, Kumar Madduri <ksmadduri@xxxxxxxxx> wrote:
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
