The error does make it pretty clear that there was either a channel failure or that the backup pieces are missing.... RF Robert G. Freeman Oracle Press Author Principle Engineer/Team Manager The Church of Jesus Christ of Latter-Day Saints Collaborate '07 Come join my APEX University Session and Join me to talk about Evolutionary Database Development!! The LDS Church is Hiring DBAs! Contact me if you are interested! -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Jared Still Sent: Tuesday, March 20, 2007 6:35 PM To: Fuad Arshad Cc: Allen, Brandon; Oracle-L Freelists Subject: Re: RMAN recovery from tape with automatic channels I suspect it is an issue with the Veritas MML. There are other issues with this setup as well. For instance, ALLOCATE CHANNEL does not work with the PARMS argument. This is in a lab environment, and NBU will be upgraded to 6.0 later this week. A rerun of the test may clear it up. On 3/20/07, Fuad Arshad <fuadar@xxxxxxxxx> wrote: weird i just tested this . i do have recovery catalog but for purposes of this discussion i think that should'nt matter legato and oracle 9.2.0.8 new RMAN configuration parameters: CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE'; new RMAN configuration parameters are successfully stored starting full resync of recovery catalog full resync complete RMAN> run { 2> backup datafile 10; 3> } Starting backup at 20-MAR-07 allocated channel: ORA_SBT_TAPE_1 channel ORA_SBT_TAPE_1: sid=1073 devtype=SBT_TAPE channel ORA_SBT_TAPE_1: NMO v4.2.0.0 channel ORA_SBT_TAPE_1: starting full datafile backupset channel ORA_SBT_TAPE_1: specifying datafile(s) in backupset ********************** channel ORA_SBT_TAPE_1: starting piece 1 at 20-MAR-07 user interrupt received Finished backup at 20-MAR-07 ----- Original Message ---- From: Jared Still < jkstill@xxxxxxxxx> To: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx> Cc: Oracle-L Freelists < oracle-l@xxxxxxxxxxxxx> Sent: Tuesday, March 20, 2007 4:33:27 PM Subject: Re: RMAN recovery from tape with automatic channels I knew I should have included SHOW ALL The default device is set to SBT RMAN configuration parameters are: CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 5 DAYS; CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE'; CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2; CONFIGURE DEVICE TYPE DISK PARALLELISM 1; # default CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' MAXOPENFILES 8; CONFIGURE MAXSETSIZE TO UNLIMITED; # default CONFIGURE SNAPSHOT CONTROLFILE NAME TO 'D:\ORACLE\ORA92\DATABASE\SNCFTL01.ORA'; # default RMAN> On 3/20/07, Allen, Brandon < Brandon.Allen@xxxxxxxxxxx> wrote: Not sure if this has anything to do with it, but is your default device type also 'SBT_TAPE'? RMAN> show default device type; RMAN configuration parameters are: CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE'; Regards, Brandon Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it. -- Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist -- Jared Still Certifiable Oracle DBA and Part Time Perl Evangelist