Re: RMAN Duplicate issue
Date: Thu, 20 Mar 2008 12:27:00 +0200
As was already pointed until means "up to and not including" file 1455. Since file 1455 probably contain changes from a time before your second backup, RMAN needs to go back to the previous one.
BTW, I do not see (maybe you left this out) that you do: sql 'alter system archive log current'; and backup of archive logs after this. That is needed so you will be able to restore to the time the backup ended.
Godwin vincent wrote:
> Hi all,
> I have an interesting issue with RMAN Duplicate process.
> Following is the scenario i have
> 1. I have a FULL Incremental Level 0 backup plus archive log of date
> *March 10th*.
> 2. I have taken a new FULL incremental Level 0 backup plus archive log
> today i.e.,* March 18th*.
> Following is the backup script i have used to take backups:
> *allocate channel c1 device type disk format '$HOME/testdb1_%s_%t_%U';*
> *allocate channel c2 device type disk format '$HOME/testdb1_%s_%t_%U';*
> *backup as compressed backupset incremental level 0 database plus
> *backup current controlfile format '$HOME/testdb1contro.ctl';*