Configuring primary for a failover (alternate) remote destination
edited Aug 6, 2012 2:08AM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 2 commentsAnswered
I have a situation where I
want to configure primary database (11.2) with 2 remote destinations.
dest_2 is the default and points to a standby on host_2. However, I also
want the primary db to continue transporting redo to dest_3 on node_3
when node_2 is taken down (planned or unplanned).
My research led me to 2 ways to doing this ...
1) Configure the ALTERNATE attribute of dest_2 to point to dest_3.
2) Configure tnsnames client-side failover on primary host to point to 2 nodes (node_2 and node_3).
Have you done this before. If yes, please provide real-life experience on how you implemented it?
Thank you.
My research led me to 2 ways to doing this ...
1) Configure the ALTERNATE attribute of dest_2 to point to dest_3.
2) Configure tnsnames client-side failover on primary host to point to 2 nodes (node_2 and node_3).
Have you done this before. If yes, please provide real-life experience on how you implemented it?
Thank you.
0