Recovering Databases with RMAN - OCP: Oracle Database 12c Administrator Certified Professional - page 227

Now all you need to do is shut down and start up the database (assuming further
restore and/or recovery operations are not required) or use the STARTUP FORCE command,
as shown here:
RMAN> startup force
Oracle instance started
database mounted
database opened
Total System Global Area 397557760 bytes
Fixed Size 1333452 bytes
Variable Size 335546164 bytes
Database Buffers 54525952 bytes
Redo Buffers 6152192 bytes
Just to summarize the steps needed to perform this recovery, here they are:
1. Issue the STARTUP NOMOUNT command to start up the database from RMAN.
2. Issue the CREATE PFILE FROM MEMORY command from SQL*Plus or using the SQL
RMAN command.
3. Edit the pfile so that it contains the correct setting for the parameter DB_RECOVERY_
FILE_DEST and the parameter DB_RECOVERY_FILE_DEST_SIZE .
4. Shut down and restart the database instance using the newly created pfile.
5. Use the RESTORE SPFILE FROM AUTOBACKUP command to restore the spfile.
6. Restart the database using the STARTUP FORCE command.
Restoring the Spfile When Not Using the FRA
If you are not using the FRA, the procedure to restore the spfile from an autobackup is
actually slightly easier. First, you have already started the database instance. You will have
to set two RMAN parameters. The first parameter identifies the DBID of the database (dis-
cussed earlier in this chapter). You use the SET DBID command to do this, as shown here:
RMAN> Set dbid= 437680418
executing command: SET DBID
Now you need to use the SET command with the CONTROLFILE AUTOBACKUP FORMAT
parameter to indicate where the control-file autobackups can be found, as shown here:
RMAN> SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO
2> 'c:\oracle\controlfilebackup\%F';
executing command: SET CONTROLFILE AUTOBACKUP FORMAT
using target database control file instead of recovery catalog