It is important that the % parameters are configured in exactly this sequence:
For Archivelog <DBNAME_%s:%t:%p>.al
For Controlfile <DBNAME_%s:%t:%p:1>.cntrl
DBNAME is ORACL in the example above and should match your database name.
Configure the controlfile autobackup
The backup must include the controlfile backup. This can be configured within Oracle RMAN configuration as a default option or by adding the following two RMAN statements right at the beginning:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO '%F';
Note:
It is mandatory to enable the auto backup of the controlfile. If not enabled, Oracle will automatically include the SPFILE in the backup which leads to a format error as the “%f” parameter is not supported for the SPFILE.
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)';
…
Replace the database backup statement
As the %f parameter is not available in Oracle 9i, the distribution of the data files to the allocated channels needs to be done manually. To do this, it is necessary to store the backup statement for the data files in an external script because the Data Protector parser is not able to parse the required changes. Extract the database backup statement marked in red and save it to a temporary location like a text file.
…
backup incremental level <incr_level>
format 'oracle backup specification<ORACL_%s:%t:%p>.dbf' database;
...
Replace this backup statement by a call to an external script which will be created later. The following examples assume that a recovery catalog for the target database is available and already configured.
If no recovery catalog is available, please refer to the Oracle 9i configuration without a recovery catalog
…
EXECUTE SCRIPT 'backup_datafiles';
...
14