Yeah, thats pretty much the problem. My plan is to generate the create
controlfile command to a sql file prior to the clone operation so that its
available when needed, rather than going through editing the trace file. I
will probably just write a shell script to call the sql file if needed, so
that if I am not available when the operation fails, I can just have
someone run the shell script rather than page me.
On Fri, Feb 16, 2018 at 3:07 PM, Norman Dunbar <oracle@xxxxxxxxxxxxxxx>
wrote:
Hi Andrew,
I have run into an occasional problem with rman > cloning, and according
to Oracle the fix is to re-create the >controlfile. I would like to automate this process.
Unfortunately, I don't have a script to generate a create controlfile
script, sorry. I thought I did have, but I looked and didn't find it. Hmm.
Did you, by any change try to clone a database when the primary had block
change tracking turned on? And when you came to open the clone, it barfed?
I've suffered from that a few times myself, I did document the workaround,
but it involved running a backup controlfile to trace, so it's not what you
want.
Good luck.
Cheers,
Norm.
--
Norman Dunbar
Dunbar IT Consultants Ltd
Registered address:
27a Lidget Hill
Pudsey
West Yorkshire
United Kingdom
LS28 7LG
Company Number: 05132767
--
//www.freelists.org/webpage/oracle-l
