Thank you all. That is what i thinking but wanted to make sure my
assumption was correct.
On Mon, Jun 8, 2015 at 10:01 AM, Stefan Koehler <contact@xxxxxxxx> wrote:
Hi Max,
1. Does it request all the logs from the current primary to make it insync
Yes, it does by default. However if you don't want to use the "archive log
approach" (which can be very time consuming and hard in handling depending
on your amount of redo), you can use incremental backups to roll forward
your standby database:
http://docs.oracle.com/cd/E11882_01/server.112/e41134/rman.htm#SBYDB00759
2. how does it deal with let's say I have backed up my archive logswith rman in my now primary so the database do not hang, how do we deal with
that?In such a situation backups and deletion of archive logs on primary would
only be possible, if you set the hidden parameter
"_deferred_log_dest_is_valid" to FALSE. For more details - please check
out MOS ID #1380368.1. However if you have set this parameter to FALSE and
deleted the archive logs on primary, you can also restore them directly to
standby (by using RMAN catalog) and then proceed as usual.
Best Regards
Stefan Koehler
Freelance Oracle performance consultant and researcher
Homepage: http://www.soocs.de
Twitter: @OracleSK
max scalf <oracle.blog3@xxxxxxxxx> hat am 8. Juni 2015 um 16:47geschrieben:
my primary site down for hardware maintenance, I am assuming I would do a
Hello list,
I have one other question related to this. Let's say if I want to take
switchover first and then take down old primary. My question is whenthe original primary comes back up (let's say after 6 hours) and we have a
big
gap now.sync
1. Does it request all the logs from the current primary to make it in
2. how does it deal with let's say I have backed up my archive logswith rman in my now primary so the database do not hang, how do we deal with
that?
