RMAN Parameter configuration errors

Question

I am trying to run the following script to set configuration parameters for rman:
rman <<!!
connect rcvcat rman/${RMAN_PWD}@${RMANCAT}
connect target /
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 15 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/u03/app/oracle
/backups/RMAN/${SID}/%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
CONFIGURE CHANNEL 1 DEVICE TYPE DISK FORMAT '/u03/app/oracle/backups/RMAN/${SID}
/backup_db_%d_S_%s_P_%p_T_%t' MAXPIECESIZE 1024m;
CONFIGURE CHANNEL 2 DEVICE TYPE DISK FORMAT '/u03/app/oracle/backups/RMAN/${SID}
/backup_db_%d_S_%s_P_%p_T_%t' MAXPIECESIZE 1024m;
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/flash_recovery_area/${SI
D}/snapcf_ev.f';
for some reason I get the errors...
for CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01005: syntax error: found "backup": expecting one of: ";"
RMAN-01007: at line 1 column 42 file: standard input
and for CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
RMAN>
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00558: error encountered while parsing input commands
RMAN-01005: syntax error: found "identifier": expecting one of: "backup"
RMAN-01008: the bad identifier was: DELETION
RMAN-01007: at line 1 column 22 file: standard input
I can't find anything wrong with the syntax in the script, but I'm fairly new to this stuff so I could just be missing something. Does anyone know what could be causing these errors?

Answer 1

I just realized that I was running this script against 9i instances. The script is meant to be run against 10g instances and worked fine when I did so. I guess I'll have to adjust the script accordingly for 9i.