Unfortunately, we can’t use the workaround as the backups are run through
CommVault, which generates the RMAN script. We can’t change that.
Scott Canaan ‘88
Sr Database Administrator
Information & Technology Services
Finance & Administration
Rochester Institute of Technology
o: (585) 475-7886 | f: (585) 475-7520
srcdco@xxxxxxx<mailto:srcdco@xxxxxxx> | c: (585) 339-8659
CONFIDENTIALITY NOTE: The information transmitted, including attachments, is
intended only for the person(s) or entity to which it is addressed and may
contain confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon this
information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and
destroy any copies of this information.
From: Arun Chugh [mailto:arun.chugh1610@xxxxxxxxx]
Sent: Tuesday, November 27, 2018 11:43 PM
To: Scott Canaan
Cc: Oracle Mailing List
Subject: Re: Oct. PSU / RMAN Error
Also encountered the same issue after applying july, 18 patch on both oracle
11g and 12c, so then while searching for the error then got to know it is a
bug hit as well as oracle provided the workaround for the same.
We have implemented the workaround 2 month back and it is working fine for us.
Solution-
Remove the delete command from the run block.
Outside the run block, mention the below command followed by delete one-
Allocate maintenance channel for device type disk / tape;
Delete noprompt archivelog until backup 2 times;
On Wed, Nov 28, 2018, 02:59 Scott Canaan <srcdco@xxxxxxx<mailto:srcdco@xxxxxxx>
wrote:
I just installed the Oct. PSU in my Oracle 12.1.0.2 Oracle Home. The next RMAN
hot backup failed with the same issue that occurred with the July PSU, which we
backed out and didn’t apply. There was supposed to be a fix for this, which I
assumed would be included with the Oct. PSU.
Because of this issue, we didn’t apply the July PSU, but our internal security
office is insisting we have to apply this one. If we do, we won’t be able to
back up any of our production databases, as they are all hot backups.
I have opened an SR with Oracle, but was wondering if anyone else has run into
this issue and, if so, did you get a patch from Oracle to fix it? I’ve been
looking for a patch online and on Oracle’s site all afternoon, with no success.
The error is:
released channel: ch1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 11/27/2018 09:38:40
RMAN-06091: no channel allocated for maintenance (of an appropriate type)
RMAN>
Scott Canaan ‘88
Sr Database Administrator
Information & Technology Services
Finance & Administration
Rochester Institute of Technology
o: (585) 475-7886 | f: (585) 475-7520
srcdco@xxxxxxx<mailto:srcdco@xxxxxxx> | c: (585) 339-8659
CONFIDENTIALITY NOTE: The information transmitted, including attachments, is
intended only for the person(s) or entity to which it is addressed and may
contain confidential and/or privileged material. Any review, retransmission,
dissemination or other use of, or taking of any action in reliance upon this
information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and
destroy any copies of this information.