RE: Duplicate from Active Database Question

No, it would not. We would just see a flood of posts where the user was crying about not being able to restore to a point in time earlier than when Oracle was actually able to copy one or more of the database data files.

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of David Barbour Sent: Friday, August 01, 2014 4:17 PM
To: Andrew Kerber
Cc: oracle-l mailing list
Subject: Re: Duplicate from Active Database Question

From the Oracle Documentation: http://docs.oracle.com/cd/B28359_01/backup.111/b28273/rcmsynta020.htm#CHDBCJFA

"When you execute DUPLICATE with FROM ACTIVE DATABASE, at least one normal target channel and at least one AUXILIARY channel are required. You cannot use the UNTIL clause when performing active database duplication. RMAN chooses a time based on when the online datafiles have been completely copied, so that the datafiles can be recovered to a consistent point in time."
It would be a nice feature to add however.

On Wed, Jul 23, 2014 at 6:01 PM, Andrew Kerber <andrew.kerber_at_gmail.com<mailto:andrew.kerber_at_gmail.com>> wrote: I would experiment with this syntax:
run {
set until time...;
duplicate target database to dest from active database; }

On Wed, Jul 23, 2014 at 5:53 PM, David Barbour <david.barbour1_at_gmail.com<mailto:david.barbour1_at_gmail.com>> wrote: Oracle 11gR2
RHEL 6.3
I've been refreshing a 14TB SAP 'sandbox' instance on our test RAC for close to a year now using RMAN "DUPLICATE TARGET DATABASE TO <SID> FROM ACTIVE DATABASE". Now the organization wants to refresh a series of SAP instances in the test environment at the same time so they'll all be in sync. The methodologies employed to this are pretty arcane. However, as part of this, we need to copy the 14TB Production instance back to test. The method for ensuring synchronization has been - and continues to be for the most part - to shutdown all the active production instances and make either a datafile backup or a clone snap. So I know that they're going to shut down the production constellation at a certain time. Normally, out test environment goes down on Friday nights for backups, so I have a window to perform an active duplicate from the running production instance back to test. What I do know is that it takes about 10 hours to do the refresh. So if I started on Friday night, it would finish in the wee hours (anything before 9AM is wee hours to me) of Saturday morning and would be out of sync with the other databases that will be shut down at 10PM on Saturday night. I could start it Saturday afternoon so it would finish in the 'dead zone', but I was wondering if anybody has tried to perform a point-in-time (future) recovery of an active duplicate. I know a recovery and a duplicate are fundamentally different, but in the duplicate from active database it applies the logs and redo to bring the copy current with the source. I have looked through the documentation and can't find any mention of using a recover clause with duplicate. Ideally I'd like to put a recover until cancel in there and apply logs until I reach the dead zone than let it finish up.

--
Andrew W. Kerber

'If at first you dont succeed, dont take up skydiving.'


--
http://www.freelists.org/webpage/oracle-l