brain dead
- From: Niall Litchfield <niall.litchfield@xxxxxxxxx>
- To: oracle-l <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 22 Jan 2009 17:48:35 +0000
So I'm revisiting the MAA whitepapers
http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10g_RACPrimaryRACPhysicalStandby.pdf
with
a view to getting my old notes on how to setup dataguard properly in line
for RAC
I'm finding that the OracleNet config documentation is a bit light. Given a
primary called CHICAGO and a standby called BOSTON, GLOBAL_DBNAME is
CHIGACO.DOMAIN.COM they say that we should do the following
at the primary site 1
1) set db_unique_name to CHICAGO1
2) add a tnsnames entry for BOSTON
3) set service_names = CHICAGO1
at the standby site 1
1) set db_unique_name to BOSTON1
2) add a tnsnames entry for CHICAGO
3) set service_names = BOSTON1
I reckon that leaves the listener at the primary knowing about a service of
chicago1 and at the standby a service of boston1 - similary for the second
nodes. Wouldn't that mean the client tnsnames would need to be looking for a
different service depending on which listener they contacted? That seems
wrong.
they also talk about setting the LOCAL_LISTENER to LISTENERS_CHIGACO and
LISTENERS_BOSTON but don't mention those tnsnames at all - I assume they are
just load balanced tnsnames entries for all the listeners in the local
cluster?
Am I missing something - before I try to fire up 4 VMs to test this out?
If anyone has a complete set of sqlnet config files they'd be willing to
share off list (and sanitised for machines obviously) that would probably
help.
--
Niall Litchfield
Oracle DBA
http://www.orawin.info
fighting a horrible, horrible cold and wanting to sleep.
Other related posts:
