Hi All,
I'm currently in the middle of a tar with Oracle about duplicating without
set until time/scn According to the doc's it must be possible but when
trying I get an error message about an archive log file that it needs but
is not yet there.
Any of you duplicating without set untill
Jack,
Of course you can duplicate a db using RMAN without using the
'set until time' feature.
Are u sure all the archived logs which have been backed up by RMAN
are present i.e. none of the logs have been accidentally deleted ??
RMAN will use the archived logs to apply the changes and open the
My experience has been that RMAN will try to restore the database right up to the
current point-in-time of the production database. So if you are on a remote system,
it will be looking for data in the current redo logs (or logs that were archived since
the backup), which it can't access.
I think your theory is correct. I have the same experience, I have to
use SET UNTIL, otherwise RMAN complains about the archivelogs. Oracle
8.1.7 on IBM AIX.
Robin
Jay Hostetter wrote:
My experience has been that RMAN will try to restore the database right up to the
current point-in-time of
Make sure you build the controlfiles on the clone with noarchivelog. That
will keep you from having the problem of set until time.
Ruth
- Original Message -
To: Multiple recipients of list ORACLE-L [EMAIL PROTECTED]
Sent: Friday, April 12, 2002 11:59 AM
I think your theory is correct.
Ruth,
When I startup nomount my clone, no files exist, except the init.ora. I then
duplicate using:
run {
set until time to_date('040120020214','mmddhh24mi');
allocate auxiliary channel ch1 type disk;
set newname for datafile 1 to '/u03/oradata/BSCSD/system01.dbf';
...yadda yadda...
I always rebuild the controlfiles for the clone and make it noarchivelog. I
am still on 8.0.6.3 so I can't duplicate the database, I have to fool rman
be renaming the clone to the orginal and restore. First I so a backup
controlfile to trace on the clone, then I set name to the orginal and make
