mine are similar to previous poster (this is 9i) -
run {
allocate channel t1 type 'sbt_tape';
allocate channel t2 type 'sbt_tape';
allocate channel t3 type 'sbt_tape';
resync catalog;
# Backup the Database, control file, archivelogs, then deletes 1 copy of archive logs.
backup full database plus archivelog delete input;
release channel t1;
release channel t2;
release channel t3;
}
Now we have 2 concurrent archivelog destinations, so each time the archivelog delete is done it deletes a log from either location, then next time it runs it will delete the same archlog from other destination. I've been watching this since back in 8i and it's still not 100% accurate, ie it will always leave the odd straggler behind now and then. no big deal though.
in 8i we did this -
run {
allocate channel t1 type 'sbt_tape';
allocate channel t2 type 'sbt_tape';
allocate channel t3 type 'sbt_tape';
resync catalog;
change archivelog all crosscheck;
# Backup the Database
backup incremental level 0 database;
sql 'alter system archive log current';
# Backup Archive Logs
backup archivelog until time 'SYSDATE' delete input;
# Backup the control file.
backup current controlfile;
release channel t1;
release channel t2;
release channel t3;
}