Performing Incomplete Recovery - RMAN Recipes for Oracle Database 12c - page 378

Here is some sample output:

OPEN_MODE CONTROL
-------------------- -------
READ WRITE CURRENT

Using Backup Control File
Our recommended approach is to first restore the control file that was backed up at the same time your noarchivelog
mode database was backed up. This way the control file has an SCN that is consistent with the data file SCNs. After
you restore the control file, you can then restore the data files and open your database with the open resetlogs
command. For example:

$ rman target /
RMAN> startup nomount;
RMAN> restore controlfile from autobackup;
RMAN> alter database mount;
RMAN> restore database;
RMAN> alter database open resetlogs;

You should see the following message after opening your database with the resetlogs option:

Statement processed

■ in this scenario, if you don't restore the control file, then you won't be able to open your database. This is
because the control file needs to be in sync with the data files.

Note

Using Current Control File
If you don't restore your control file from the backup, you will have to perform a few extra steps. This example does not
restore the control file (uses current control file) and uses SQL*Plus to cancel out of the recovery session:

$ rman target /
RMAN> startup mount;
RMAN> restore database;
RMAN> alter database open resetlogs;

At this point, you'll get an error message indicating that the resetlogs option is valid only after an incomplete
database recovery:

ORA-01139: RESETLOGS option only valid after an incomplete database recovery

Perform the following steps from SQL*Plus to open your database:

SQL> recover database until cancel;