CATALOG START WITHYou can't even use CROSSCHECK to make it become AVAILABLE, because the new database does not have the backup record of that backup set. But 9i do have the following commands:
CATALOG BACKUPPIECE
CATALOG RECOVERY AREA
CATALOG CONTROLFILECOPYIf you don't mind to use DATAFILECOPY, then you have a chance for your new database.
CATALOG DATAFILECOPY
CATALOG ARCHIVELOG
Putting the backup set under the directory of backup destination can't make RMAN to recognize it (tested), either. But there're still exceptions.
- Without recovery catalog: You can use the control file of source database for the the auxiliary database. Then
- With recovery catalog: If the new database have its own control file, you can make it fake the source database by this:
RMAN> crosscheck backup;
Most of the backup will be EXPIRED, but your backup set will be AVAILABLE.
RMAN> set dbid <source dbid>
And connect to the catalog to ask for the backup records of source database.
RMAN> connect target / catalog cat_owner/cat_password@catdb
RMAN> crosscheck backup;