Error Code: [18:183] Description: Failed with Oracle DB/RMAN error [RMAN-03002: failure of delete command at mm/dd/yyyy 14:35:15 RMAN-06091: no channel allocated for maintenance (of an appropriate type) ] Source: <client name>, Process: ClOraAgent
Ora DBA gave the following lines to be added to script, but still it not helped
allocate channel for maintenance type 'SBT_TAPE';
allocate channel for maintenance type disk;
Other instance archive log from other hosts are using same schedule where the scripts are placed in, they running fine. but this instance
Best answer by InnoV8
Known oracle issue and Information on the oracle patch as follows, which is available from the Oracle Metalink site.
Issue is reported in Bug 28391990. Which has been Superseded by Fix in Bug 28432129 Bug 28432129 - RMAN-06091: no channel allocated for maintenance (of an appropriate type) after installing July 2018 (DBPSU/BP/RU) ( Doc ID 28432129.8 ) and RMAN Backup Gives RMAN-06091: No Channel Allocated For Maintenance (of An Appropriate Type) After Applying July (DBPSU/BP/RU) on 11.2.0.4 /12.1.0.2/12.2 and 18.2 ( Doc ID 2428682.1 ) You need to apply patch for bug 28432129 or install bundle patch: 11.2.0.4.181016 (Oct 2018) Bundle Patch
This is also documented from https://documentation.commvault.com/v11/expert/troubleshooting_backups_oracle_agent.html Section ==> RMAN-3002: failure of delete command or RMAN-6091: no channel allocated for maintenance
As a work around which is also mentioned from Oracle support end side, you can use customized script at the schedule policy level and take out the delete command outside the run block but it will be at customer risk, Example
From:
run { setlimit channel ch1 maxopenfiles 8; sql "alter system archive log current"; backup filesperset = 32 format='xxxxxx_%d_%U' (archivelog all ); delete noprompt archivelog until time = 'sysdate-2' backed up 1 times to sbt ; } exit;
To:
run { setlimit channel ch1 maxopenfiles 8; sql "alter system archive log current"; backup filesperset = 32 format='xxxxxx_%d_%U' (archivelog all ); } delete noprompt archivelog until time = 'sysdate-2' backed up 1 times to sbt ; exit;
Known oracle issue and Information on the oracle patch as follows, which is available from the Oracle Metalink site.
Issue is reported in Bug 28391990. Which has been Superseded by Fix in Bug 28432129 Bug 28432129 - RMAN-06091: no channel allocated for maintenance (of an appropriate type) after installing July 2018 (DBPSU/BP/RU) ( Doc ID 28432129.8 ) and RMAN Backup Gives RMAN-06091: No Channel Allocated For Maintenance (of An Appropriate Type) After Applying July (DBPSU/BP/RU) on 11.2.0.4 /12.1.0.2/12.2 and 18.2 ( Doc ID 2428682.1 ) You need to apply patch for bug 28432129 or install bundle patch: 11.2.0.4.181016 (Oct 2018) Bundle Patch
This is also documented from https://documentation.commvault.com/v11/expert/troubleshooting_backups_oracle_agent.html Section ==> RMAN-3002: failure of delete command or RMAN-6091: no channel allocated for maintenance
As a work around which is also mentioned from Oracle support end side, you can use customized script at the schedule policy level and take out the delete command outside the run block but it will be at customer risk, Example
From:
run { setlimit channel ch1 maxopenfiles 8; sql "alter system archive log current"; backup filesperset = 32 format='xxxxxx_%d_%U' (archivelog all ); delete noprompt archivelog until time = 'sysdate-2' backed up 1 times to sbt ; } exit;
To:
run { setlimit channel ch1 maxopenfiles 8; sql "alter system archive log current"; backup filesperset = 32 format='xxxxxx_%d_%U' (archivelog all ); } delete noprompt archivelog until time = 'sysdate-2' backed up 1 times to sbt ; exit;
