2012-06-03 20:40 catalog start with rman backup set is directly imported into the control file

Catalog start with is a good order. With this command, you can basically stop using the catalog database. Because the previous backup set information can be re-imported into the current control file through this command, which is generally applied to rman recovery, and the control file is old or manually created (of course, such control file does not have the latest backup set information), through catalog start with, you can import the latest backup set and the list of archive log files into the control text, and then you can restore rman.

For example, copy the backup set to / data01

RMAN > startup nomount

RMAN > restore controlfile from'/ data01/testdb_CF_c-3148051840-20110813-0000; # restore control files from the control file backup set

RMAN > alter database mount

Catalog start with'/ data01/'; (be sure to end with "/", or you won't find the real path)

Run {

Allocate channel c1 type disk

Allocate channel c2 type disk

Allocate channel c3 type disk

Set newname for datafile'+ DATA/icare/datafile/system.309.717426483' to'/ backup/supt/suptdata/system.309.717426483'

Set newname for datafile'+ DATA/icare/datafile/apps_undots1.283.717426031' to'/ backup/supt/suptdata/apps_undots1.283.717426031'; set newname for datafile'+ DATA/icare/datafile/apps_ts_tx_data.273.717426033' to'/ backup/supt/suptdata/apps_ts_tx_data.273.717426033'

Set newname for datafile'+ DATA/icare/datafile/apps_ts_tx_data.275.717426033' to

Set newname for datafile'+ DATA/icare/onlinelog/group_16.265.743248917' to'/ data02/supt/suptdata/group_16.265.743248917'

Restore database force

Switch datafile all

}

If the backup set is stored in multiple paths, it can be executed multiple times

RMAN > catalog start with'/ data01/'

RMAN > catalog start with'/ data02/'

RMAN > catalog start with'/ data03/'