Re: Rename BCT during RMAN Duplicate

From: Ram Cheruvattath <>
Date: Sat, 27 Jun 2015 18:13:01 -0400
Message-ID: <91F8E3C7363E43AF9FB0E9E1F0176E19_at_RAMPC>

Have you tried using set db_file_name_convert inside your rman script? There are some known bugs related to this.


From: Ramnivas Chaurasia
Sent: Saturday, June 27, 2015 9:57 AM
To: Steve Harville
Cc: Andrew Kerber ; ORACLE-L
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.


On 27 Jun 2015 17:52, "Steve Harville" <> 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 <> wrote:

    What do you mean by BCT?

    Sent from my iPad

> On Jun 27, 2015, at 12:10 AM, Ramnivas Chaurasia <> 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: &
> Thanks!
> Ramniwas


Received on Sun Jun 28 2015 - 00:13:01 CEST

Original text of this message