In a broadcasting replication environment (also termed as data distribution environment) the source Shareplex instance sends data to multiple target Shareplex instances. The term port is used interchangeably for Shareplex instance. So it can be termed as one port being used for all targets. Another way to configure Shareplex would be to use multiple Shareplex instances on source (each using different port number) that correspond to various targets that receive data. In this case each target has Shareplex running on a port number that is different from the one used by the other targets. This solution explores best practice when configuring Shareplex in a data distribution topology.
General information.
The preferred approachis to use the same port for all the replication streams going tovarious targets. This is the conventional method described in Shareplex published documentation and isused by majority of customers. The following are the main advantages:
1. It is less resource intensive for the source whereby there is only one Shareplex instance and consequently fewer number of processes (Capture, Read, etc) and fewer # of queue structures.
2. Maintenance is easier. For example,to remove one table from replication,justedit the copy of the config file and activate the copy.
When replicating different tables to different targets, then either approach would be fine. One advantage of using different ports is that vardirs for these ports can resideon separate devices and reduce I/O contention. However, this advantage may not outweigh the increased resource requirement placed on the source server by way of multiple Shareplex instances.
Please refer to Shareplex Admin Guide Chapter titled Planning SharePlex Replication section titled Replication to distribute data for additional information.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center