Chat now with support
Chat with Support

SharePlex 9.2.4 - Installation and Setup for Oracle on RDS

Network checklist

Requirement Completed? (Y/N)

Add SharePlex users and groups to the nameserver.

If you are installing SharePlex in a network managed by a nameserver such as NIS or NISPLUS, do the following before you install SharePlex:

  • Add SharePlex users to the nameserver.
  • Add the SharePlex groups to the nameserver.

The SharePlex security groups spadmin (administrator), spopr (operator), and spview (viewer) control access to SharePlex processes. Add each SharePlex user to one of these groups on the nameserver. For more information, see Assign SharePlex users to security groups.

To add the user groups:

  1. For NIS add the groups to the group.byname and group.bygid maps. For NISPLUS, add them to the group.org_dir table.
  2. Add the SharePlex Administrator user to the spadmin group on the nameserver.
  3. Create the spadmin group in the /etc/group file (on Unix and Linux) or the User Accounts control panel (Windows), and then add the SharePlex Administrator user to the group.

To add SharePlex groups to the local system after you install SharePlex, see Assign SharePlex users to security groups.

 

Ensure that SharePlex can resolve host names.

If you find that SharePlex cannot connect to a host, try mapping the host name to an alphanumeric alias in the following locations:

  • Network: The NIS and DNS servers
  • Unix and Linux: Local /etc/hosts file
  • Windows: Local hosts file

In these files, put each entry on an individual line. The following is an example, where sysA and sysB are aliases:

111.22.33.44   sysA.company.com   sysA   # source system
55.66.77.88    sysB.company.com   sysB   # target system

 

Resolve to the right network card

If you have multiple network cards on Windows, you must set the SP_SYS_HOST_NAME environment variable to the network card name or IP address that you want SharePlex to use as the local host. Otherwise, if the server reboots after the SharePlex configuration is activated, the IP address may bind to a different network card from the one that is bound in the replication configuration.

For more information about SharePlex environment parameters and how to set them, see the SharePlex Reference Guide.

 

Allow access to Amazon EC2 instance

For an EC2 instance, make certain that the appropriate network group is set up to allow access to EC2 instances.

 

Verify the SharePlex port number.

By default SharePlex uses the port number 2100 (hex equivalent is 834) for both TCP/IP and UDP. If port 2100 is available to SharePlex, no further action is needed. You will need to enter the SharePlex port number during the installation procedure, at which time you can specify a different port number if needed.

Important! The SharePlex port number must be the same one on all machines in the replication configuration so that they can communicate through TCP/IP connections. Make certain the SharePlex port number is open for both TCP/IP and UDP on the firewall.

 

Verify TCP/IP settings

SharePlex replicates over any TCP/IP network connection. Typically, if all of the tables in a database are being replicated, SharePlex replicates about 33 percent of the redo log volume, the remainder being mostly maintenance data used by the Oracle software. The following is a formula for determining bandwidth.

(size of a redo log) x (number of log switches in 1 hour) x 1/3 = volume of data per hour

For example, if the redo logs are 20 MB in size, and they switch six times an hour, SharePlex will replicate approximately 40 MB each hour:

20 x 6 x 1/3 = 40 MB/hour

 

VerifyTCP protocol

SharePlex has been tested on IP v6 networks, but it is impossible to test all scenarios. See the System Requirements in the SharePlex Release Notes for more informationon.

 
Related Documents