It is important that the % parameters are configured in exactly this sequence:

<DBNAME_%s:%t:%p:X>.df

DBNAME is ORACL in the example above and X is the last data file id—so 1, 10, 6 or 7 in the given example.

For incremental level you may choose any valid rman incremental level, whereas incremental level 0 is a full backup.

Now save the file and close the text editor.

Create the script in rman and store the content in the catalog

The contents of the script file now need to be loaded into the recovery catalog and stored as an rman script.

Start rman and connect to both the catalog and also the target database:

RMAN> CONNECT CATALOG rman/xxx@RCVCAT

connected to recovery catalog database

RMAN> CONNECT TARGET /

connected to target database: ORACL (DBID=3273914744)

Be sure to adapt the username, password, and database ID for the recovery catalog to your settings.

Create the script and load the contents of the text file in the catalog by using the CREATE SCRIPT statement and paste the content of the text file line by line into the command prompt (unfortunately the ‘FROM FILE’ syntax is not available in Oracle 9i):

RMAN> CREATE SCRIPT 'backup_datafiles' 2> {

3> backup incremental level 0

4> (datafile 9,3,1 channel dev_0 filesperset 3 format 'oracle backup specification<ORACL_%s:%t:%p:1>.df')

5> (datafile 2,4,10 channel dev_1 filesperset 3 format 'oracle backup specification<ORACL_%s:%t:%p:10>.df')

6> (datafile 5,6 channel dev_2 filesperset 2 format 'oracle backup specification<ORACL_%s:%t:%p:6>.df')

7> (datafile 8,7 channel dev_3 filesperset 2 format 'oracle backup specification<ORACL_%s:%t:%p:7>.df');

8> }

created script backup_datafiles

Be sure that the script name (here: ‘backup_datafiles’) matches the one specified in the Data Protector GUI. After the creation of the script in the recovery catalog exit rman.

If necessary the script can later be replaced / deleted in rman using the commands ‘REPLACE SCRIPT’ and ‘DELETE SCRIPT’ (please check the rman documentation for reference)

17