White Paper

Script Summary
Now you should have one rman script in the Data Protector GUI and one external script saved in the
recovery catalog similar to the example below:
Rman Script (Changes from default are marked red)
run {
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO
'%F';
allocate channel 'dev_0' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=ORACL,OB2BARLIST=oracle backup
specification)';
allocate channel 'dev_1' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=ORACL,OB2BARLIST=oracle backup
specification)';
allocate channel 'dev_2' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=ORACL,OB2BARLIST=oracle backup
specification)';
allocate channel 'dev_3' type 'sbt_tape'
parms 'ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=ORACL,OB2BARLIST=oracle backup
specification)';
EXECUTE SCRIPT 'backup_datafiles';
sql 'alter system archive log current';
backup
format 'oracle backup specification<ORACL_%s:%t:%p>.al'
archivelog all;
backup
format 'oracle backup specification<ORACL_%s:%t:%p>.dbf'
recovery area;
backup
format 'oracle backup specification<ORACL_%s:%t:%p:1>.cntrl'
current controlfile;
}
External script (in the recovery catalog—named backup_datafiles):
{
backup incremental level 0
(datafile 9,3,1 channel dev_0 filesperset 3 format 'oracle backup
specification<ORACL_%s:%t:%p:1>.df')
(datafile 2,4,10 channel dev_1 filesperset 3 format 'oracle backup
specification<ORACL_%s:%t:%p:10>.df')
(datafile 5,6 channel dev_2 filesperset 2 format 'oracle backup
specification<ORACL_%s:%t:%p:6>.df')
(datafile 8,7 channel dev_3 filesperset 2 format 'oracle backup
specification<ORACL_%s:%t:%p:7>.df');
}
Limitations for Oracle 9i
This configuration for Oracle 9i has some limitations that include the following:
• If a data file is added or removed, the external script needs to be edited
• The incremental level of the backup can no longer be chosen in the Data Protector GUI, but only
configured in the external script
18