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

From: Upendra N <>
Date: Thu, 7 Jan 2010 18:14:03 -0500
Message-ID: <BLU129-W282624DC70AEC0686947AED8710_at_phx.gbl>

Are you running the database in logical or physical standby? If you are running physical standby, I'd think the file names and the path should match unless you have the file_name_convert specified.


> Date: Thu, 7 Jan 2010 14:59:55 -0800
> From:
> Subject: Recreate standby controlfile for DB that uses OMF and ASM
> To:
> 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
> +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.
> --

Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
Received on Thu Jan 07 2010 - 17:14:03 CST

Original text of this message