Recovery of lost data files and control files of Rman backup

About Recovery with a Backup Control File
If All copies of the current control file is lost or damaged, then you must restore and mount a backup control file. You must then run the RECOVER command, even if no data files has been restored, and open the database with the Resetlogs option. If Some copies of the current control file is usable, however, then can follow the procedure in "responding to th e Loss of a subset of the current Control Files "and avoid the recovery and resetlogs operation. When RMAN was connected to a recovery catalog, the recovery procedure with a backup control file was identical to recovery W ITH a current control file. The RMAN metadata missing from the backup control file was available from the recovery catalog. The only exception are if the database name is not a unique in the catalog, in which case you must use SET DBID command befor e Restoring the control file.
1. Start RMAN and connect to a target database.
2. Start the target instance without mounting the database. Rman>startup Nomount;--control files are missing or corrupted and can only be booted to Nomount
3. Restore the control file
rman> SET DBID 320066378; # (Optional) If The database name is not unique and you need to specify the DBID
Rman> RUN
{
SET controlfile autobackup FORMAT for DEVICE TYPE DISK to ' Autobackup_format ';
RESTORE controlfile from Autobackup;--recovery of control files from automated backups
}
4. Start the target instance with mounting the database. Rman>startup MOUNT;--The control file has been restored, can mount data file

5. Restore the data files; Rman>restore DATABASE; --restore/recover corrupted data file
6. Recover the database; Rman>recover DATABASE;
7. Open the database with RESETLOGS option; rman> ALTER DATABASE OPEN resetlogs; --Open the database in Resetlog mode

Recovery of lost data files and control files of Rman backup