Setting up a physical standby on a server with a different structure

Question

I am having a few issues trying to set up a physical standby database.
The primary database has a different naming structure than the standby and they are at different sites.
Physical is /var/hpsrp/ctrorp03/oradata/u0x/<DB_NAME>/<DB_UNIQUE_NAME> and standby is /var/hpsrp/drforp03/oradata/u0x/<DB_NAME>/<DB_UNIQUE_NAME>.
I have set db_file_name_convert to '<PRIMARY PATH>', '<STANDBY PATH>' times the number of paths as pairs.
I have created a blank database for standby and having taken a full backup of primary with control file and standby control file.
Now I hit the issues:
The DB incarnation numbers are different.
When I try and do a normal restore e.g. set dbid, restore controlfile; mount; it fails as it is trying to find files in the primary structure and not standby structure.
When I try renaming via set newname or auxname it can't find files to restore I guess due to the incarnation id's.
If I set the incarnation id and try to restore backup it fails as the incarnation id's don't match.
I have tried looking through various forums and the documentation but can't find a solution, probably can't see the wood for the trees though as there is so much.
Has anyone done this type of setup before and can give me some advice?

Answer 1

Thanks for you replies I will try and give more information on both.
srsatya :- Version is 11.2 the controlfile I tried to restore was the one created by the backup not the standby should I be putting the standby in place then before I do the restore? If so just a replacement for the current controlfile by carefully replace at an OS level or by mimicing the controlfile to be restored from autobackup?
CKPT:- Think I tried that but I have been going around in so many circles may have mucked something up.
RMAN> set dbid=2261148474 (The PRIMARY Incarnation number)
executing command: SET DBID
RMAN> alter database mount;
using target database control file instead of recovery catalog
database mounted
RMAN> run
2> { 
3> allocate channel c1 device type disk;
4> SET NEWNAME FOR DATAFILE 1 TO '/var/hpsrp/drforp03/oradata/u01/SAPDS/DRFSAPDS/system01.dbf';
5> SET NEWNAME FOR DATAFILE 2 TO '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf';
6> SET NEWNAME FOR DATAFILE 3 TO '/var/hpsrp/drforp03/oradata/u01/SAPDS/DRFSAPDS/undotbs01.dbf';
7> SET NEWNAME FOR DATAFILE 4 TO '/var/hpsrp/drforp03/oradata/u01/SAPDS/DRFSAPDS/users01.dbf';
8> SET NEWNAME FOR DATAFILE 5 TO '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/IPSCMS01.dbf';
9> SET NEWNAME FOR DATAFILE 6 TO '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/IPSA01.dbf';
10> SET NEWNAME FOR DATAFILE 7 TO '/var/hpsrp/drforp03/oradata/u02/SAPDS/DRFSAPDS/DSCR01.dbf';
11> SET NEWNAME FOR DATAFILE 8 TO '/var/hpsrp/drforp03/oradata/u03/SAPDS/DRFSAPDS/ISCR01.dbf';
12> SET NEWNAME FOR DATAFILE 9 TO '/var/hpsrp/ctrorp03/oradata/u05/SAPDS/CTRSAPDS/DSLR_DEV01.dbf';
13> SET NEWNAME FOR DATAFILE 10 TO '/var/hpsrp/ctrorp03/oradata/u05/SAPDS/CTRSAPDS/undotbs02.dbf';
14>
15> RESTORE DATABASE;
16> SWITCH DATAFILE ALL;
17> RECOVER DATABASE;
18> }
allocated channel: c1
channel c1: SID=165 device type=DISK
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 28-JUN-12
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 06/28/2012 10:21:13
RMAN-06189: current DBID 2261148474 does not match target mounted database (2261834728)
RMAN> exit
Recovery Manager complete.
drfora04 ora_srp3 $ rman
Recovery Manager: Release 11.2.0.1.0 - Production on Thu Jun 28 10:22:16 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
RMAN> connect target /
connected to target database: SAPDS (DBID=2261834728, not open)
RMAN> run
2> { 
3> allocate channel c1 device type disk;
4> SET NEWNAME FOR DATAFILE 1 TO '/var/hpsrp/drforp03/oradata/u01/SAPDS/DRFSAPDS/system01.dbf';
5> SET NEWNAME FOR DATAFILE 2 TO '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/sysaux01.dbf';
6> SET NEWNAME FOR DATAFILE 3 TO '/var/hpsrp/drforp03/oradata/u01/SAPDS/DRFSAPDS/undotbs01.dbf';
7> SET NEWNAME FOR DATAFILE 4 TO '/var/hpsrp/drforp03/oradata/u01/SAPDS/DRFSAPDS/users01.dbf';
8> SET NEWNAME FOR DATAFILE 5 TO '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/IPSCMS01.dbf';
9> SET NEWNAME FOR DATAFILE 6 TO '/var/hpsrp/drforp03/oradata/u04/SAPDS/DRFSAPDS/IPSA01.dbf';
10> SET NEWNAME FOR DATAFILE 7 TO '/var/hpsrp/drforp03/oradata/u02/SAPDS/DRFSAPDS/DSCR01.dbf';
11> SET NEWNAME FOR DATAFILE 8 TO '/var/hpsrp/drforp03/oradata/u03/SAPDS/DRFSAPDS/ISCR01.dbf';
12> SET NEWNAME FOR DATAFILE 9 TO '/var/hpsrp/ctrorp03/oradata/u05/SAPDS/CTRSAPDS/DSLR_DEV01.dbf';
13> SET NEWNAME FOR DATAFILE 10 TO '/var/hpsrp/ctrorp03/oradata/u05/SAPDS/CTRSAPDS/undotbs02.dbf';
14>
15> RESTORE DATABASE;
16> SWITCH DATAFILE ALL;
17> RECOVER DATABASE;
18> }
using target database control file instead of recovery catalog
allocated channel: c1
channel c1: SID=165 device type=DISK
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 28-JUN-12
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 06/28/2012 10:22:26
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
RMAN>
Edited by: gzmzpz on 28-Jun-2012 04:56