Oct. PSU / RMAN Error

[Scott Canaan]

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: [phone] | f: [phone]
***@rit.edu<mailto:***@rit.edu> | c: [phone]

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.

[Leng]

Scott,

Just the errorneoous line is not enough to work with.

Please share:

1) Rman> show all;
2) command
3) full log
4) are you using a recovery catalog?


Cheers,
Leng

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.
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: [phone] | f: [phone]
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.

["MacGregor, Ian A." (Redacted sender "ian" for DMARC)]

This is a problem with purging backups written to tape. Searching in the

06091 error will give the workaround and also point to overlay patches. We were hit by this as well.


Ian A. MacGregor
SLAC National Accelerator Laboratory
Computing Division
To offer the best IT service at the lab and be the IT provider of choice.
________________________________
From: oracle-l-***@freelists.org <oracle-l-***@freelists.org> on behalf of Leng <***@gmail.com>
Sent: Tuesday, November 27, 2018 1:51:12 PM
To: ***@rit.edu
Cc: oracle-***@freelists.org
Subject: Re: Oct. PSU / RMAN Error

Scott,

Just the errorneoous line is not enough to work with.

Please share:

1) Rman> show all;
2) command
3) full log
4) are you using a recovery catalog?


Cheers,
Leng

On 28 Nov 2018, at 8:25 am, Scott Canaan <***@rit.edu<mailto:***@rit.edu>> 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: [phone] | f: [phone]

***@rit.edu<mailto:***@rit.edu> | c: [phone]


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.

[Pecoraro, Michael]

Scott,

Since applying the July 2018 CPU, we have received the RMAN-06091 error when attempting to delete obsolete backups when there is a mix of obsolete backups of both DISK and SBT_TAPE device types. All is well if we have obsolete backups of only one device type, DISK or SBT_TAPE.

We had hoped for a fix in the Oct 2018 or Jan 2019 CPU. However, it appears that may not happen. Per MOS Doc ID 2428682.1, and info received when a colleague opened an SR on the issue, the current patches do not resolve the issue in all cases. Therefore, we plan to explicitly allocate the maintenance channels for the DISK and SBT_TAPE device types in the "delete obsolete" run block of our backup script. That is the recommended solution we received from Oracle Support. We hope to have that implemented this week. I can update you if you are interested.

Mike

---
Michael J Pecoraro
University at Buffalo
***@buffalo.edu<mailto:***@buffalo.edu>


On Tue, 2018-11-27 at 21:25 +0000, Scott Canaan 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: [phone] | f: [phone]
***@rit.edu<mailto:***@rit.edu> | c: [phone]

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.

[Arun Chugh]

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;

Post by Scott Canaan
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.
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: [phone] | f: [phone]
*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.

[Scott Canaan]

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: [phone] | f: [phone]
***@rit.edu<mailto:***@rit.edu> | c: [phone]

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:***@gmail.com]
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 <***@rit.edu<mailto:***@rit.edu> 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: [phone] | f: [phone]
***@rit.edu<mailto:***@rit.edu> | c: [phone]
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.

[Arun Chugh]

If possible you can do one thing disable the delete archivelog or backup
from commvault, place one script for doing the same by using workaround.

Post by Scott Canaan
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: [phone] | f: [phone]
*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.
*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;
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.
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: [phone] | f: [phone]
*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.

[Jose Rodriguez]

AFAIK, Commvault allows some level of customisation if you have access to
the console.
http://documentation.commvault.com/commvault/v11/article?p=20433.htm

Maybe this is not your case?

[image: Pythian] <http://www.pythian.com/>
*Jose Rodriguez* | Oracle Database Consultant | [image: LinkedIn]
<https://www.linkedin.com/company/pythian>
*t* [phone] <+1+613+565+8696> *ext.* 1393
*m* [phone] <+34+607+55+49+91>
***@pythian.com
*www.pythian.com* <https://www.pythian.com/>
[image: Pythian] <https://www.pythian.com/email-footer-click>

Post by Scott Canaan
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: [phone] | f: [phone]
*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.
*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;
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.
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: [phone] | f: [phone]
*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.

[Mladen Gogala]

This post might be inappropriate. Click to display it.

[Scott Canaan]

This post might be inappropriate. Click to display it.