RMAN Backup Gives RMAN-06091: No Channel Allocated for Maintenance

RMAN Backup Gives RMAN-06091: No Channel Allocated for MaintenanceI really don’t want to turn this blog into an accumulation of issues and flaws. But as I explained many times before, the blog for me is also a way to dump information I likely will need the sooner or later again.

Recently I blogged about another RMAN issue in Oracle 12.2.0.1 with traces. This was fixed with the July 2018 RU for Oracle 12.2.0.1. But the issue below about which Piero Ferraz from Brazil alerted me (thanks!!!), happens in exactly this RU.

RMAN Backup Gives RMAN-06091: No Channel Allocated for Maintenance

This issue gets introduced with the July 2018 RU for Oracle 12.2.0.1 and is in Oracle 18.3.0 as well. It is fixed generically in Oracle 19c but you will need to apply a one-off fix right now if you get hit by this issue.

In MOS Note: 2428682.1 – RMAN Backup Gives RMAN-06091: No Channel Allocated For Maintenance (of An Appropriate Type) After Applying July 12.1.0.2.180717 (DBPSU/BP/RU) you’ll find this “explanation”:

After applying July 2018 (DBPSU/BP/RU) Patch RMAN script may fail with ” RMAN-06091: NO CHANNEL ALLOCATED FOR MAINTENANCE (OF AN APPROPRIATE TYPE) “

 
RMAN-8031: released channel: t1
RMAN-571: ===========================================================
RMAN-569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-571: ===========================================================
RMAN-3002: failure of delete command at 07/24/2018 08:26:03
RMAN-6091: no channel allocated for maintenance (of an appropriate type)

The issue got logged as Bug 28391990 but the fix got superseded by Bug 28432129 which has then the complete patch. You can download patch 28432129 from MOS.

Basically the issue happens during deletion of archivelog or datafile copies. Or when you do a crosscheck. A disk channel is expected. And if no disk channel is defined, it fails. The fix allows other channels to be used for the deletion as well as far as my understanding goes.

Piero sent me his output:

opat lspatches

28163133; Database Jul 2018 Release Update: 12.2.0.1.180717 (28163133)
28163190; OCW JUL 2018 RELEASE UPDATE 12.2.0.1.180717 (28163190)

sent command to channel: c1

sent command to channel: c1

sent command to channel: c1

sent command to channel: c1

released channel: c1
RMAN-00571: ====================================================== =============
RMAN-00569: ============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ====================================================== =============
RMAN-03002: failure of crosscheck command at 07/30/2018 19:33:48
RMAN-06091: no channel allocated for maintenance (of an appropriate type)

Recovery Manager complete.
no rows selected
no rows selected
no rows selected
no rows selected

Important Links

Addition Sep 3, 2018

Thanks for the hint to Kay Liesenfeld: The issue is in 12.1.0.2 and 11.2.0.4 as well. You may have recognized this from the MOS note’s title pointing to 12.1.0.2. I haven’t. Sorry – and thanks for the hint, Kay!

–Mike

 

8 thoughts on “RMAN Backup Gives RMAN-06091: No Channel Allocated for Maintenance

  1. Hey Mike,

    there is the same issue with 12.1. and 11.2.0.4. databases and PSU/RU July 2018.

    Regards
    Kay.

  2. Ooops, still not fixed.
    Installed 12.2.0.1 vanilla, then Jul 2018 RU. In Aix.
    Tried cold backup, same problem.
    Anyways, not a biggie. The event avoid the issue, good enough for me.

  3. Hello Mike,
    simple question in this context: in the README of patch 28432129 they say ‘RAC Rolling Installable’ but when I proceeded as normal and performed “opatch apply” on our RAC opatch neither recognized that it’s a RAC nor asked me to stop the instance (“Is the local system ready for patching?”. As the result the patch was ‘successfully’ applied on only one node with running services for this Oracle home. Im sure this patch contains really minor changes so there is no problem at all but I’m in doubt if my patch procedure was wrong or is the README of this patch incorrect?

    Thx & regards
    Axel D.

  4. we need to add the tape channel and the disk channel. (if TAPE is defined as DEFAULT ! )

    allocate channel for maintenance type ‘SBT_TAPE’ PARMS=”SBT_LIBRARY=/opt/commvault/Base/libobk.so,BLKSIZE=262144,ENV=(CV_mmsApiVsn=2,CV_channelPar=ch1)” TRACE 0;
    — before ——
    RMAN> delete obsolete;

    RMAN-Aufbewahrungs-Policy wird f▒r den Befehl angewendet
    RMAN-Aufbewahrungs-Policy ist auf ein Recovery-Fenster von 14 Tagen festgelegt
    Die folgenden veralteten Backups und Kopien werden gel▒scht:
    Typ Schl▒ssel Abschlusszeit Dateiname/Handle
    ——————– —— —————— ——————–
    Backupset 560 2018-12-27 16:02:23
    Backup-Piece 673 2018-12-27 16:02:23 +BKUP/IFPRD_HA1/AUTOBACKUP/2018_12_27/s_995990541.1543.995990543
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: Fehler bei Befehl delete bei 01/11/2019 20:17:43
    RMAN-06091: Kein Kanal f▒r Wartung (entsprechenden Typs) zugewiesen

    —— After ————

    allocate channel for maintenance device type disk;
    delete obsolete;
    RMAN-Aufbewahrungs-Policy wird f▒r den Befehl angewendet
    RMAN-Aufbewahrungs-Policy ist auf ein Recovery-Fenster von 14 Tagen festgelegt
    Die folgenden veralteten Backups und Kopien werden gel▒scht:
    Typ Schl▒ssel Abschlusszeit Dateiname/Handle
    ——————– —— —————— ——————–
    Backupset 560 2018-12-27 16:02:23
    Backup-Piece 673 2018-12-27 16:02:23 +BKUP/IFPRD_HA1/AUTOBACKUP/2018_12_27/s_995990541.1543.995990543

    M▒chten Sie die obigen Objekte wirklich l▒schen (geben Sie YES oder NO ein)? YES
    Backup Piece gel▒scht
    Backup-Piece Handle=+BKUP/IFPRD_HA1/AUTOBACKUP/2018_12_27/s_995990541.1543.995990543, RECID=1, STAMP=995990541
    1 Objekte gel▒scht

    I hope it helps. ( it is a German DB but the messages are pretty much explanatory themselves )

Leave a Reply

Your email address will not be published. Required fields are marked *

* Checkbox to comply with GDPR is required

*

I agree

This site uses Akismet to reduce spam. Learn how your comment data is processed.