I cant use set incarnation since db A cant be touched, by now. Jared, db A was refreshed and a separated db for rman catalog is configured. I have verified orphaned backups and path of incarnation, I can restore db A to previous incarnation and then make the clone but as I stated before, db A is under usage at this moment. Seems to be the only solution, so I need to wait for user's confirmation to proceed. Its pretty peculiar how this gets so complicated by RMAN when using a normal hotbackup would allow to make the clone in less than 20min. (34G) ________________________________ From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Jared Still Sent: Lunes, 03 de Mayo de 2010 03:16 p.m. To: Aragon, Gabriel (GE, Corporate, consultant) Cc: oracle list Subject: Re: RMAN: Clone db from a previous resetlogs backup On Mon, May 3, 2010 at 12:26 PM, Aragon, Gabriel (GE, Corporate, consultant) <gabriel.aragon@xxxxxx> wrote: 2. Sunday 2nd, Db A was refreshed from db X. First thoughts: 1) What does step 2 really mean? How was it refreshed? Were the control files overwritten? 2) If an RMAN catalog repository is used (separate database for RMAN catalog) then question 1 becomes less important. If the control files were overwritten, and the answer to #2 is false, it should still be possible to restore form dbA at T1 if the backup files are available on disk, though it will be more difficult. Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist Oracle Blog: http://jkstill.blogspot.com Home Page: http://jaredstill.com