Database Reference
In-Depth Information
target database Password:
connected to target database: CDB1 (DBID=800340993, not open)
auxiliary database Password:
connected to auxiliary database: CDB1 (DBID=800340993)
RMAN>
Once connected (remember to watch out for “reversed” primary and auxiliary) you can initiate the backup and
recover operation:
RMAN> recover database from service cdb1 using compressed backupset;
Starting recover at 20.09.2013 22:01
using channel ORA_DISK_1
skipping datafile 5; already restored to SCN 1735864
skipping datafile 7; already restored to SCN 1735864
skipping datafile 8; already restored to SCN 1864611
skipping datafile 9; already restored to SCN 1864611
skipping datafile 10; already restored to SCN 1864611
skipping datafile 11; already restored to SCN 1864611
channel ORA_DISK_1: starting incremental datafile backup set restore
channel ORA_DISK_1: using compressed network backup set from service cdb1
destination for restore of datafile 00001: +DATA/CDB2/DATAFILE/system.290.826664973
channel ORA_DISK_1: restore complete, elapsed time: 00:00:07
channel ORA_DISK_1: starting incremental datafile backup set restore
channel ORA_DISK_1: using compressed network backup set from service cdb1
destination for restore of datafile 00003: +DATA/CDB2/DATAFILE/sysaux.269.826664973
channel ORA_DISK_1: restore complete, elapsed time: 00:00:07
channel ORA_DISK_1: starting incremental datafile backup set restore
channel ORA_DISK_1: using compressed network backup set from service cdb1
destination for restore of datafile 00004: +DATA/CDB2/DATAFILE/undotbs1.291.826664973
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
channel ORA_DISK_1: starting incremental datafile backup set restore
channel ORA_DISK_1: using compressed network backup set from service cdb1
destination for restore of datafile 00006: +DATA/CDB2/DATAFILE/users.288.826664993
channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
starting media recovery
media recovery complete, elapsed time: 00:00:10
Finished recover at 20.09.2013 22:12
The code in bold font shows that the backup set is taken from the network. This new method is in stark contrast
to the previous method where you needed to create an incremental backup from a specific SCN, transfer it to the
standby database host and apply it. The option to compress the backupsets helps conserve bandwidth. Using multiple
channels and the section size clause should make the restore a lot quicker.
Instead of recovering the whole database you can limit the scope to data files, tablespaces, and control files; both
the “restore” and “recover” command have been enhanced to use the “from service” clause.
 
Search WWH ::




Custom Search