Hi Ram,
For nightly direct-path loads you have the choice of logging (no nologging
operations and force logging to be sure) or sync after the load (12.2 ADG
makes it easy:
https://blog.dbi-services.com/12cr2-recover-nonlogged-blocks-after-nologging-in-data-guard/).
If you have an idea about the volume, you can simulate on your network with
oratcptest (see
https://dbamarco.wordpress.com/2016/11/25/benchmarking-data-guard-throughput/
)
Franck.
On Sun, Nov 24, 2019 at 1:42 AM Chris Taylor <
christopherdtaylor1994@xxxxxxxxx> wrote:
To setup dataguard, I believe the primary must use force logging, so the
direct I serts will still be logged even if the objects have nologging
specified.
So, you may take a bit on the primary if you're not logging everything
currently because it will have to be logged to support DG. Unless, I'm
badly mistaken .
Chris
On Sat, Nov 23, 2019, 4:00 PM Ram Raman <veeeraman@xxxxxxxxx> wrote:
All,
We are looking into data guard as one of the HA/DR solutions for a big
data warehouse of several TBs in size. (will have more information about
the DW once I gain access to it). 98% or more of the data is fed into the
DW DB using nightly feeds. Given that, if we use data guard solution I am
wondering how the syncing between the primary and standy will happen. I am
also thinking that during the load process, the data will be loaded using
direct load option; this looks like the logs shipped from primary wont be
of much use at the standby.
Do the listers use data guard with a data warehouse env? Can they share
their experiences? Any good paper on that. Thanks.
Ram.
--
