Re: Oct. PSU / RMAN Error

From: Mladen Gogala <gogala.mladen_at_gmail.com>
Date: Tue, 4 Dec 2018 20:59:33 -0500
Message-ID: <88093b78-c23c-0ac3-9ad9-b18c8bbb2006_at_gmail.com>



Hi Scott,

You can use a script to delete obsolete backup to disk. The script would look like this:

[oracle_at_ora122 ~]$ rman target /

Recovery Manager: Release 12.2.0.1.0 - Production on Tue Dec 4 20:51:23 2018

Copyright (c) 1982, 2017, Oracle and/or its affiliates.  All rights reserved.

connected to target database: O122 (DBID=1534876540)

RMAN> delete obsolete device type disk;

using target database control file instead of recovery catalog RMAN retention policy will be applied to the command RMAN retention policy is set to redundancy 1 allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=330 device type=DISK no obsolete backups found

RMAN> Of course, that applies if you have disk backup. You can find out about that by listing backups like this:

RMAN> list backup of database summary device type disk;

specification does not match any backup in the repository

RMAN> This actually an Oracle problem, caused by applying July 2018 PSU. Also, you can save your disk backups by using something like this

connect  target /

run {

allocate channel t1 device type sbt
parms="SBT_LIBRARY=/opt/commvault/Base/libobk.so,BLKSIZE=1048576";

backup backupset all;

}

That will find all existing backup sets on disk and save them to tape.

Regards

On 11/28/18 7:51 AM, Scott Canaan wrote:
>
> 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_at_rit.edu <mailto:srcdco_at_rit.edu> | 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_at_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 <srcdco_at_rit.edu
> <mailto:srcdco_at_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: (585) 475-7886 | f: (585) 475-7520
>
> srcdco_at_rit.edu <mailto:srcdco_at_rit.edu> | 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.
>

-- 
Mladen Gogala
Database Consultant
Tel: (347) 321-1217


--
http://www.freelists.org/webpage/oracle-l
Received on Wed Dec 05 2018 - 02:59:33 CET

Original text of this message