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... Ta Fairlie Rego Senior Oracle Consultant http://el-caro.blogspot.com/ M: +61 402 792 405 ________________________________ From: Yong Huang <yong321@xxxxxxxxx> To: oracle-l@xxxxxxxxxxxxx Sent: Fri, 8 January, 2010 9:59:55 AM Subject: Recreate standby controlfile for DB that uses OMF and ASM Oracle 10.2.0.4. 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 +DATA/mydb/datafile/system.123.4567890 but the file on standby is (as viewed in asmcmd) +DATA/mydbsb/datafile/system.234.5678901 (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. -- //www.freelists.org/webpage/oracle-l __________________________________________________________________________________ See what's on at the movies in your area. Find out now: http://au.movies.yahoo.com/session-times/