I 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 220.127.116.11 with traces. This was fixed with the July 2018 RU for Oracle 18.104.22.168. 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 22.214.171.124 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.
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: 126.96.36.199.180717 (28163133) 28163190; OCW JUL 2018 RELEASE UPDATE 188.8.131.52.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
- MOS Note: 2428682.1 – RMAN Backup Gives RMAN-06091: No Channel Allocated For Maintenance (of An Appropriate Type) After Applying July 184.108.40.206.180717 (DBPSU/BP/RU)
- Bug 28391990 – RMAN-06091: NO CHANNEL ALLOCATED FOR MAINTENANCE
- RMAN Backup generates traces in Oracle 220.127.116.11
- FloraB’s Blog Post: Issues encountered after applying the July 2018 18.104.22.168 BP
Addition Sep 3, 2018
Thanks for the hint to Kay Liesenfeld: The issue is in 22.214.171.124 and 126.96.36.199 as well. You may have recognized this from the MOS note’s title pointing to 188.8.131.52. I haven’t. Sorry – and thanks for the hint, Kay!