How to configure the source config file when replicating to a multi-node RAC target
Target RAC configuration question
Assuming that the target RAC system will be utilized, as intended, to be able to failover to the available node(s) should something happen to the active node that has been configured using a single virtual hostname.
1. The source config file should point to the route of the virtual hostname used on the target.
Example of the config file on source assuming that "MyVirtualhostname" is the virtual hostname:
datasource:o.{source SID}
#source tables target tables routing map
splex.demo_src splex.demo_dest MyVirtualhostname@o.SPLEXRAC
------------------------------------------------------------------------------------------------------
Starting with SharePlex 8.6, the login credentials of SharePlex user are written to and stored in the file named connections.yaml located in /vardir/data subdirectory of SharePlex (where vardir refers to the Variable directory of SharePlex). Here is a sample entry:
alvsupu07 # cat connections.yaml
o.SYAM:
password: 5787d4def4
user: SHA86
In the above, the first line has SID info. The second line has encrypted password and the third line has the name of the SharePlex user that makes connections to the database.
It is necessary to use on the target a common tns_alias for all nodes in the $ORACLE_HOME/network/admin/tnsnames.ora file, which must exist on all nodes or on the shared file system.
Example of target's tnsnames.ora
SPLEXRAC =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = MyRACNODE1)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = MyRACNODE2)(PORT = 1521))
(LOAD_BALANCE = off)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = {service name})
)
)
Where:
"SPLEXRAC"= is the common tns_alias
"MyRACNODE1"= virtual hostname of node 1
"MyRACNODE2"= virtual hostname of node 2
Example of target's /etc/hosts file on the shared file system on all nodes:
10.1.1.xx MyVirtualhostname
10.1.1.xx MyRACNODE1
10.1.1.xx MyRACNODE2
Example of target's paramdb file splex login parameters created during ora_setup:
In this example, ora_setup was ran for a splex schema user named splex2100 with {password}@SPLEXRAC
Here are the SharePlex login credential parameter entries in the paramdb:
SP_ORD_LOGIN_O.SPLEXRAC "689fd983ba1a54bec85c062884d7129a04f9294ac854327ff7"
SP_ORD_OWNER_O.SPLEXRAC "splex2100"
