Re: Recreate standby controlfile for DB that uses OMF and ASM

From: fairlie rego <>
Date: Thu, 7 Jan 2010 22:17:16 -0800 (PST)
Message-ID: <>

Hi Yong,

After you restore the standby controlfile you need to catalog all datafiles and then do a switch to copy  so that Oracle automatically switches all file names....

Hope that helps... 

There is a note written by Larry Carpenter on Metalink which details this... Let me know if you want me to dig it out for you...

Fairlie Rego
Senior Oracle Consultant
M: +61 402 792 405

From: Yong Huang <>
Sent: Fri, 8 January, 2010 9:59:55 AM
Subject: Recreate standby controlfile for DB that uses OMF and ASM

Oracle Both primary and standby use ASM and OMF. Parameter 
db_create_file_dest is set to +DATA. They're running fine. Suppose I 
want to recreate the controlfile on standby from primary (for some 
reason). On primary I create a standby controlfile. On standby I 
startup nomount and run RMAN command: restore controlfile from 
'/tmp/newcontrolfile_ftped_over'. This will wipe out the datafile 
file# and name mapping. For instance, the system datafile on primary is


but the file on standby is (as viewed in asmcmd)


(db_file_name_convert is 'mydb','mydbsb')

For this file, I probably can fix it by alter database rename file 
'...123...' to '...234...'. But if the mapping is not clear, there's 
no way to fix. Am I correct? Before overwriting the standby 
controlfile, I didn't save the output of v$datafile that has file# 
and name.


See what's on at the movies in your area. Find out now:

Received on Fri Jan 08 2010 - 00:17:16 CST

Original text of this message