• Add an additional allocate channel command for each node.
• Add a command to connect to each instance. The connection parameters should
be given as username/passwd@INSTANCE.
For example, if you are using two nodes, the backup specification might look as
follows:
run {
allocate channel 'dev_0' type 'sbt_tape' parms
'SBT_LIBRARY=Path_to_Data_Protector_MML,
ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DB_NAME,OB2BARLIST=RAC_arch)'
connect username/passwd@INSTANCE_1;
allocate channel 'dev_2' type 'sbt_tape' parms
'SBT_LIBRARY=Path_to_Data_Protector_MML,
ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DB_NAME,OB2BARLIST=RAC_arch)'
connect username/passwd@INSTANCE_2;
backup
format 'RAC_arch<QU_%s:%t:%p>.dbf'
archivelog all;
}
Problem
The Recovery Catalog was lost and the control file cannot be restored from Data
Protector managed backup
The Recovery Catalog was not used, the RMAN autobackup feature was not used,
and the control file cannot be restored from Data Protector managed backup. A valid
control file backup exists on tape.
Action
• Restore the control file from RMAN backup set, mount and restore the database,
and perform database recovery:
run {
allocate channel 'dev_0' type 'sbt_tape' parms
'SBT_LIBRARY=Path_to_Data_Protector_MML';
restore controlfile from 'backup piece handle';
sql 'alter database mount';
set until time 'MMM DD YY HH24:MM:SS';
restore database;
recover database;
sql 'alter database open resetlogs';
release channel 'dev_0';
}
Data Protector Oracle ZDB integration160
To Next Page
Loading...
Need help?
General