RE: duplicate command to clone database to another host

Whether you need an until time or not depends on when the last RMAN backup of the archivelogs has taken place.

If there has been a log switch since the last RMAN archivelog backup then you will get the missing log file scenario. So a lot depends on timing and the frequency of log switches within the database.

When we do a duplicate restore we run an archivelog backup first. If that is not possible we enter the log sequence number instead (or a time)

   duplicate target database to ${Auxiliary_Database}
### until scn 9999999999999
### until sequence 100 thread 1

-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Paula_Stankus_at_doh.state.fl.us
Sent: 24 May 2005 20:37
To: rgramolini_at_tax.state.vt.us; all_about_oracle_at_hotpop.com; oracle-l_at_freelists.org
Subject: RE: duplicate command to clone database to another host

Thanks Ruth,

I have actually accomplished a duplication before by using a full backup. So I am not sure why incremental level 0 is necessary. I do a full database backup which apparently gets the controlfile, I then archivelog current all, then backup the archives and remove archives from the file system so that seems to match what you are doing.

I think it is the until time that I needed and how to find out the exactly correct one and thank you sooo much for the rman sql to see and the advice on setting the until time (plus one second). I will try that and let you know.

Thanks again Ruth.

You're the best!

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