On 12/21/2015 09:26 AM, Mark W. Farnham wrote:
Active data guard switches on real time apply. (Because it needs to be up to
date to fulfill the feature description.)
Switching on real time apply does not switch on active data guard. (And serves
maximum protection without adding to license fees.)
Your observation was accurate, but in this instance the application of converse
logic was in error. The license fees possible in audit due to accidental
temporary usage of a feature tend to make us justifiably paranoid about this
stuff.
mwf
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On
Behalf Of Mladen Gogala
Sent: Monday, December 21, 2015 1:54 AM
To: kathryn axelrod; oracle.blog3@xxxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: archive_lag_target with real time apply for data guard
On 12/20/2015 07:01 PM, kathryn axelrod wrote:
You are correct; real time apply is a free feature of ee data guard.I am not quite sure about that. Whenever I opened the standby in read-only mode, "real time apply"
It simply changes the process from waiting for actual archive logs to
sending 'in real time' using redo logs.I
went from "NO" to "YES". Standby was in the maximum performance mode, with DG broker
configured.
--
Mladen Gogala
Oracle DBA
http://mgogala.freehostia.com
--
//www.freelists.org/webpage/oracle-l
