Data Guard propagation from PA-RISC to Itanium

[joseph pareti]

The customer has a primary/physical standby environment for pruduction. The production database is running on HP-UX PA Risc, the standby is running on HP-UX Itanium, both in RDBMS 9.2.0.8.
The stand by is a PHY replication from PA-RISC to Itanium. In the Itanium side they stop the Managed recovery and create a new control file to build a new DB (new instance name) based on the "old" physical stand by replication. This process has been successfully used for replication from production to test for other projects in a 100% PA-RISC environment. However, in the mixed environment(IPF/PA) they hit a problem. The error message is something like "database name XXXXX in file header does not match given name of XXXXX". So the header file is corrupted.

My understanding is that this cannot be possibly an issue with Integrity because the data is compatible, so it must be with Oracle. Oracle support, however advises *not* to use the control file method, but rather to failover the copy; however the customer's method does work on PA-RISC...

[joseph pareti]

let me just add a clarification to the previous post: the last sentence should read:

Oracle support, however advises *not* to use the control file method to change a PHY to primary, but rather to failover the copy, and then use thenid-utility to change the database name after the failover. However the customer's method (based on the control file) does work on PA-RISC...

[patrik rybar_1]

just change the dbname in the init file