Re: Rename BCT during RMAN Duplicate

From: Alfredo Abate <alfredo.abate_at_gmail.com>
Date: Sun, 28 Jun 2015 10:09:36 -0500
Message-ID: <CALrB5prhPhr6HJKOh+besKcXuvP1aOUQ5SOcnzEA6hM_jE8cLg_at_mail.gmail.com>



Ludovico Caldara just wrote a blog on this a few days ago. It might be of help/give you an idea of some options.

http://www.ludovicocaldara.net/dba/bct-duplicate-avoid-ora19755/

Regards,

Alfredo

On Sun, Jun 28, 2015 at 3:26 AM, Ramnivas Chaurasia < ramnivaschaurasia_at_gmail.com> wrote:

>
> I will try putting this parameter in RMAN script instead of init.ora next
> time I get the request and will update.
>
> Meanwhile, I tried checking for the patches related to Bug 11744544
> <https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1098638.1&id=11744544>.
> But it says the requested bug could not be displayed.
> Then I tried the workaround mentioned in Bug 10185641
> <https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1098638.1&id=10185641> (same
> as suggested by Ram) on my test DB which is running on Windows with DB
> version 11.2.0.1. It didn't give error but strangely it didn't copy the BCT
> file either. It also didn't enable the BCT on auxiliary.
> So, I will wait for the next request and will try on those DBs running on
> 11.2.0.3/4 on Solaris.
>
> Thanks,
> Ramniwas
>
> On Sun, Jun 28, 2015 at 3:43 AM, Ram Cheruvattath <
> ram.cheruvattath_at_gmail.com> wrote:
>
>> Have you tried using set db_file_name_convert inside your rman script?
>> There are some known bugs related to this.
>>
>> Ram
>>
>> *From:* Ramnivas Chaurasia <ramnivaschaurasia_at_gmail.com>
>> *Sent:* Saturday, June 27, 2015 9:57 AM
>> *To:* Steve Harville <steve.harville_at_gmail.com>
>> *Cc:* Andrew Kerber <andrew.kerber_at_gmail.com> ; ORACLE-L
>> <oracle-l_at_freelists.org>
>> *Subject:* Re: Rename BCT during RMAN Duplicate
>>
>> Hi Steve,
>>
>> Thanks, but we do not have control over source DB(Prod). We are provided
>> with the RMAN backup of source and we need to restore the same on multiple
>> DBs on target server. We can use the RMAN traditional method to avoid this
>> issue; however, we prefer DUPLICATE command to be easier. And yes, the file
>> system is ASM.
>>
>> Ramniwas,
>> On 27 Jun 2015 17:52, "Steve Harville" <steve.harville_at_gmail.com> wrote:
>>
>>> We keep the Block Change Tracking file on ASM and have a similar issue
>>> restoring to another machine with different disk groups. You can use alter
>>> database disable/enable block change tracking commands before and after the
>>> restores.
>>>
>>> On Sat, Jun 27, 2015 at 8:13 AM Andrew Kerber <andrew.kerber_at_gmail.com>
>>> wrote:
>>>
>>>> What do you mean by BCT?
>>>>
>>>> Sent from my iPad
>>>>
>>>> > On Jun 27, 2015, at 12:10 AM, Ramnivas Chaurasia <
>>>> ramnivaschaurasia_at_gmail.com> wrote:
>>>> >
>>>> > Hi,
>>>> >
>>>> > Is there any parameter to change the BCT path during RMAN duplicate
>>>> command? Or even disabling it?
>>>> >
>>>> > We generally need to restore data of a single source DB to multiple
>>>> target DBs. Target DBs are on the same server. So, if we miss renaming the
>>>> BCT file name manually after first restore on the server, the subsequent
>>>> RMAN duplicate command fails with conflicting BCT file name.
>>>> >
>>>> > So, any suggestion on renaming the BCT or disabling it, which could
>>>> be incorporated with DUPLICATE command would be highly appreciated!
>>>> >
>>>> > DB Version: 11.2.0.3 & 11.2.0.4
>>>> >
>>>> > Thanks!
>>>> > Ramniwas
>>>> --
>>>> http://www.freelists.org/webpage/oracle-l
>>>>
>>>>
>>>>
>

--
http://www.freelists.org/webpage/oracle-l
Received on Sun Jun 28 2015 - 17:09:36 CEST

Original text of this message