Hi,

I used the following script to do a full backup of our database.

run {

allocate channel t1 type disk;
allocate channel t2 type disk;
allocate channel t3 type disk;
allocate channel t4 type disk;
allocate channel t5 type disk;
allocate channel t6 type disk;
allocate channel t7 type disk;
allocate channel t8 type disk;





backup
incremental level = 0

format '/redo_log_archive/rmantest2/madden_VIPUKE1_FULL_%t_%s_%p'
(datafile 2,3,4,5,6,7,8,9,10,57 channel t1 tag=DF1)
(datafile 12,42,14,15,16,17,18,21 channel t2 tag=DF2)
(datafile 22,23,24,25,26,27,28,29,30 channel t3 tag=DF3)
(datafile 31,32,33,34,35,36,37,38,39,40 channel t4 tag=DF4)
(datafile 19,41,13,43,44,45,46,47,48,49,50 channel t5 tag=DF5)
(datafile 1,11,51,52,53,54,55,58,59 channel t6 tag=DF6)
(datafile 20 channel t7 tag=DF7)
(datafile 56 channel t8 tag=DF8);

backup current controlfile tag = 'database backup1';

release channel t1;
release channel t2;
release channel t3;
release channel t4;
release channel t5;
release channel t6;
release channel t7;
release channel t8;

}

This works fine, however we have noticed certain quirks.
Taking for example the datafiles allocoated for channel t1, RMAN intialling inputs the 9 datafiles, backs these datafiles and closes the channel. It then 'realises' it still has datafile 57 to back up, so it reopens channel t1 and backups up the missing datafile. RMAN did this for a number of the channels. Any input on why this happens?

Thanks,
Chucks_k