Re: Question: Rman duplication - requries _all_ backup sets?

Personally, I find it rather incomprehensible that the backup set needs to be on the auxiliary db's filesystem, AND that the process requires access to the original data on the target db's server as well. But, I'm just chasing the carrot here, so I'll jump through whatever hoops I have to to make it all work.

I'm testing a theory: I _think_ I can simply transfer the most recent set, and just 'touch' all the remaining files which RMAN purports to want. I'm assuming that RMAN is working through the list of backups in the catalog (or the control file, in my case) and just making sure they exist on the auxiliary node. I may be able to fool it into thinking all the backup set files are there, so long as it doesn't try to verify their contents. I just tried this once and it seemed to work; I'm doing it again to confirm.

I'm on AIX, so registry tweaks won't help just now - but I will be doing some tests in duplicating from AIX to Windows: I gather that RMAN does handle the 'endian' value of the data files of the various OS's, so I expect I can make it work. I'm moving from 8i to 10G, so the next step will be to see how/if I can use RMAN get an 8i db on AIX to a 10G Windows server. Not yet sure how the conversion/upgrade process will work, but I'll find out soon.

Thanks... Received on Tue Oct 11 2005 - 16:14:41 CDT