Backup of controlfile and controlfile autobackup are not the same thing. Prior to restoring and reading the database controlfile (nomount), RMAN doesn't know anything about RMAN backups. This is were autobackup comes into play because it uses a special format that RMAN will search for based on filename and location. In order to do so, you need to restore the spfile first, for exampe:
- RMAN> set DBID 843703910
- RMAN> startup nomount
- RMAN> restore spfile from autobackup
- db_recovery_file_dest='/u03/fast_recovery_area' db_name='ORCL2';
- RMAN> startup force nomount
- RMAN> restore controlfile from autobackup;
- RMAN> startup force mount
- RMAN> restore database;
- RMAN> recover database;
Using the "startup nomount" command, the Oracle instance creates the necessary processes and memory structures, but does not access the database control file and has no knowledge about the database data files. Once the spfile has been restored, we can start the database instance with the appropriate parameters and continue with restoring the database control and data files.
Thanks for your reply. However I would suggest you read my original post again thoroughly. Based on the update you have posted, I cannot believe you have read it. You also seem to assume (Wrongly, I have been working as an Oracle DBA for many years) that people using this community need educating on how RMAN and Oracle works. If you are going to respond please do so only in relation to the specific issue that was posted, otherwise it will be of no use to people.
The "restore controlfile from autobackup" with no other specifications like recovery area or setting DBID will only work as is when using a RMAN Catalog.
For non-catalog restore :
1) you can either "restore spfile from <backuppiece_where_autobackup_of_controlfile_is>"
2) Set DBID first and then "restore controlfile from autobackup".
Take a look here for more information
Thanks for your reply.
Prior to attempting 'restore spfile from autobackup', a connection is made to the RMAN recovery catalog database, and the database ID is also set, so this is not the issue. We still get the following error:
RMAN-06172: no autobackup found or specified handle is not a valid copy or piece.