Re: archive_lag_target with real time apply for data guard

  • From: kathryn axelrod <kat.axe@xxxxxxxxx>
  • To: "oracle.blog3@xxxxxxxxx" <oracle.blog3@xxxxxxxxx>
  • Date: Sun, 20 Dec 2015 16:02:08 -0800

No.


On Sunday, December 20, 2015, max scalf <oracle.blog3@xxxxxxxxx> wrote:

I am not using real time query only the real time apply, that is count as
active data guard?

On Sunday, December 20, 2015, max scalf <oracle.blog3@xxxxxxxxx
<javascript:_e(%7B%7D,'cvml','oracle.blog3@xxxxxxxxx');>> wrote:

Hello mladen,

I am not opening database in read only mode, only using "using current
logfile"...are you saying using that counts against active data guard? I
thought real time apply was free/included feature of enterprise edition...

On Sunday, December 20, 2015, Mladen Gogala <gogala.mladen@xxxxxxxxx>
wrote:

On 12/20/2015 01:48 PM, max scalf wrote:

Hello list,

We are in process of setting up data guard and one of the thing i was
thinking was to set "archive_lag_target" to 1800 seconds, so that i do not
loose my redo data on the standby site if there was a failure on primary,
but then it also got me thinking, I am using real time apply(this is
specific to 11g system). From what i understand about real-time apply is
"it allows Data Guard to recover redo data from the current standby redo
log as it is being filled by the RFS process", if that is the case why
would i need to set archive_lag_target as my data is being pushed out
anyways ??

thoughts ??


Hi Max!
Real-time apply is so-called "active data guard", which allows you to
query the standby DB in read only mode. Very useful for reporting. Beware
that loading data in GTT's does not work with the Active DG. Also, beware
that active DG is not free, there is a license fee.

--
Mladen Gogala
Oracle DBAhttp://mgogala.freehostia.com


Other related posts: