Control File and SPFILE Autobackup command struck

Question

O.S Version:
Linux Version "Red Hat Enterprise Linux Server release 6.2 (Santiago)
Linux version 2.6.32-220.13.1.el6.x86_64 ([email protected]) (gcc version 4.4.6 20110731 (Red Hat 4.4.6-3) (GCC) ) #1 SMP Thu Mar 29 11:46:40 EDT 2012
2.6.18-308.16.1.el5  x86_64
Tape Archiver : HP Data Protector
Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
Problem :
In one of our environment,  OEM grid 11g scheduled Level 0 backup struck at the Control File and SPFILE Autobackup.
RMAN Script:
run {
2> backup format '<%d_%s:%t:%p:%f>.df' incremental level 0 cumulative database;
3> sql 'alter system archive log current';
4> backup format '<%d_%s:%t:%p>.al' archivelog all not backed up;
5> }
RMAN Configuration
RMAN> show all;
RMAN configuration parameters for database with db_unique_name TestDB are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 45 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO 'TestDB_%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'TestDB_%F';
CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 4 BACKUP TYPE TO BACKUPSET;
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS  'SBT_LIBRARY=/opt/omni/lib/libob2oracle8_64bit.so,ENV=(OB2BARTYPE=Oracle8,OB2APPNAME=TestDB,OB2BARLIST=Siv_ORA_TESTSrvr1_TestDB_DB,OB2BARHOSTNAME=TESTSrvr1)';
CONFIGURE MAXSETSIZE TO UNLIMITED;
CONFIGURE ENCRYPTION FOR DATABASE OFF;
CONFIGURE ENCRYPTION ALGORITHM 'AES128';
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '+DG_TestDB_UAT_DATA_01/TestDB/TEMPFILE/snapcf_TestDB.f';
RMAN Log:
1.    Backup started at 07-SEP-2013 07:09:46
     Finished backup at 07-SEP-2013 07:16:38
Wherein the Control file backup started at 07-SEP-2013 07:16:38 failed at 09/07/2013 12:44:38.  It kept struck for  5 Hours.
Starting backup at 07-SEP-2013 07:09:46
allocated channel: ORA_SBT_TAPE_1
channel ORA_SBT_TAPE_1: SID=250 instance=TestDB device type=SBT_TAPE
channel ORA_SBT_TAPE_1: Data Protector A.06.20/370
allocated channel: ORA_SBT_TAPE_2
Finished backup at 07-SEP-2013 07:16:38
Starting Control File and SPFILE Autobackup at 07-SEP-2013 07:16:38
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of Control File and SPFILE Autobackup command on ORA_SBT_TAPE_1 channel at 09/07/2013 12:44:38
ORA-19506: failed to create sequential file, name="TestDB_c-2078060264-20130907-ff", parms=""
ORA-27028: skgfqcre: sbtbackup returned error
ORA-19511: Error received from media manager layer, error text:
   Vendor specific error: Cannot find requested element ERR(-2)
ORACLE error from recovery catalog database: ORA-03113: end-of-file on communication channel
Process ID: 2045
Session ID: 89 Serial number: 36509
RMAN> delete noprompt archivelog all backed up 1 times to sbt;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 09/07/2013 13:00:07
RMAN-06004: ORACLE error from recovery catalog database: ORA-03114: not connected to ORACLE
RMAN> **end-of-file**
Why does the RMAN Backup struck at Controlfile , SPFile autobackup?

Answer 1

Hello;
I believe the issue is caused by your media management software. You should contact your media management vendor.
Try the same operation to disk and I bet it works.
Best Regards
mseberg