NOTE:
When an Oracle format of the backup file is manually defined or changed
by editing the RMAN script, any user-defined combination of the Oracle
substitution variables can be added to the %s:%t:%p substitution variables
and DB_NAME, which are obligatory.
• The RMAN current controlfile command.
Example of the RMAN script
The following is an example of the RMAN script section as created by Data Protector
based on the Blank Oracle Backup template, after the whole database selection:
run {
allocate channel 'dev_0' type 'sbt_tape' parms
'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DIPSI,OB2BARLIST=New1)';
allocate channel 'dev_1' type 'sbt_tape' parms
'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DIPSI,OB2BARLIST=New1)';
allocate channel 'dev_2' type 'sbt_tape' parms
'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=DIPSI,OB2BARLIST=New1)';
backup incremental level <incr_level>
format 'New1<DIPSI_%s:%t:%p>.dbf'
database
;
backup format 'New1<DIPSI_%s:%t:%p>.dbf' archivelog all;
backup format 'New1<DIPSI_%s:%t:%p>.dbf' current controlfile
;
}
Creating copies of backed up objects
Oracle duplex mode
Oracle supports the duplex mode, which allows you to create copies of every backed
up object to a separate backup device. To enable the duplex feature, perform the
following steps:
Integration guide for Oracle and SAP
73
Need help?
Do you have a question about the Data Protector A.06.11 and is the answer not in the manual?
Questions and answers