Backup and Recovery - Expert Consolidation in Oracle Database 12c - page 404

Using the exact same script as in the sidebar you can restore and recover your database. The remainder of the
section will walk you through the output. First the database must be shut down and started into mount state:
[oracle@server1 ~]$ rman target sys@cdb1 catalog rco@rcat_pdb @recover.rman
[...]
RMAN> shutdown immediate;
2> startup mount;
3> restore database;
4> recover database;
5> alter database open;
database closed
database dismounted
Oracle instance shut down
connected to target database (not started)
Oracle instance started
database mounted
Total System Global Area 1603411968 bytes
Fixed Size 2288872 bytes
Variable Size 520094488 bytes
Database Buffers 1073741824 bytes
Redo Buffers 7286784 bytes
Once it is mounted, the restore part of the scripts is executed. In the example the global RMAN settings defined
4 parallel RMAN channels.
Starting restore at 22.09.2013 21:16
[...]
channel ORA_DISK_3: restored backup piece 1
channel ORA_DISK_3: restore complete, elapsed time: 00:01:06
Finished restore at 22.09.2013 21:17
Once the database has been restored, it will be recovered and opened:
Starting recover at 22.09.2013 21:17
using channel ORA_DISK_1
using channel ORA_DISK_2
[...]
media recovery complete, elapsed time: 00:00:07
Finished recover at 22.09.2013 21:17
Finally the database is opened and ready for service again.
An incomplete recovery of the database is possible as well, in which case you need to wrap your commands into
a so-called “run block”. The run block creates a context and the scope for operations to happen together. Consider
the following example of an incomplete recovery of a CDB:
run {
set until time="to_date('22.09.2013 21:00:00','dd.mm.yyyy hh24:mi:ss')";
restore database;