DATAGUARD with RAC - Implementing RAC database services on standby instances
edited Jan 9, 2012 9:05AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 6 comments
Hello everybody,
I'm currently testing RAC with DATAGUARD in a symetric configuration (2 PRIMARY nodes and 2 PHYSICAL STANDBY nodes) on an Exadata x2-2 machine.
Here's my configuration:
I have a primary database on a RAC with 2 instances : P01x1i1 and P01x1i2 on exa1 with db_unique_name : P01x1
On exa2, i have the PHYSICAL STANDBY instances : P01x2i1 and P01x2i2, with db_unique_name : P01x2
All the instances are working, the redo logs are shipped and applied on the standby database (it's ok for the thread1 and 2)
I have implemented a DATAGUARD BROKER successfully..
I'm currently testing RAC with DATAGUARD in a symetric configuration (2 PRIMARY nodes and 2 PHYSICAL STANDBY nodes) on an Exadata x2-2 machine.
Here's my configuration:
I have a primary database on a RAC with 2 instances : P01x1i1 and P01x1i2 on exa1 with db_unique_name : P01x1
On exa2, i have the PHYSICAL STANDBY instances : P01x2i1 and P01x2i2, with db_unique_name : P01x2
All the instances are working, the redo logs are shipped and applied on the standby database (it's ok for the thread1 and 2)
I have implemented a DATAGUARD BROKER successfully..
0