Though providing the comprehensive procedure for installing Shareplex in a RAC cluster environment is beyond the scope of Shareplex Support, the following excerpt as taken from Shareplex Installation Guide is provided for customers reference.
General information.
The following are the major requirements for using SharePlex for RAC/OPS. Additional requirements are in the SharePlex for RAC.OPS Installation and Demonstration Guide.
- SharePlex for RAC/OPS is installed into a product directory on a shared, non-raw disk that can be mounted by any cluster node as part of the failover procedure. SharePlex replicates to or from a single active node.
- A SharePlex for RAC/OPS variable-data directory is installed on the same shared non-raw disk where the product directory is installed. Using a variable-data directory on a shared disk enables the data queues and other information about the replication environment to remain available if a node fails, so that replication can resume seamlessly after failover. The shared disk must have enough free space to accommodate data accumulation as the result of replication.
- If the clustered instances have different names (ORACLE_SIDS), a TNS alias must be created for them in the tnsnames files that SharePlex for RAC/OPS can use to maintain a replication environment in the event of a failover. All nodes must have the same tns_alias name.
Important! The network and cluster configurations might be different than in the following example and, therefore,create the aliases accordingly.
For example, in a two-node cluster:
ora =
(DESCRIPTION =
(ADDRESS_LIST =
(failover=off)
(load_balance=on)
(ADDRESS = (PROTOCOL = TCP)(HOST = nova120)(PORT = 1522))
(ADDRESS = (PROTOCOL = TCP)(HOST = nova121)(PORT = 1521))
))
(CONNECT DATA =
(SERVICE_NAME = ora.external.hp.com)
)
Note: Where ora1 is the first node in the cluster and ora2 is the second node in the cluster.
ora =
(DESCRIPTION =
(ADDRESS_LIST =
(failover=on)
(load_balance=on)
(ADDRESS = (PROTOCOL = TCP)(HOST = nova121)(PORT = 1521))
(ADDRESS = (PROTOCOL = TCP)(HOST = nova120)(PORT = 1522))
))
(CONNECT DATA =
(SERVICE_NAME = ora.external.hp.com)
)
- (Version 5.x and below) If the clustered nodes have different ORACLE_HOMEs, a symbolic link must be created in the /var/adm/.splex directory to the actual ORACLE_HOME on all nodes.
- A host alias must be mapped to the floating IP address in the /etc/hosts file to establish a consistent host name across all nodes in the cluster. The alias is exported in the SharePlex user profile and used in the SharePlex configuration parameters. SharePlex for RAC/OPS is incorporated into the cluster failover package so that it migrates with the other application
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy