This document describes pros and cons of using different ports on source systems involved in replication for centralized reporting.
N.A.
When configuring Shareplex for centralized reporting by adding a new source to an existing source-target pair, users can follow one of the two routes:
A. Using the same port # for the new Shareplex source.
In this case one only needs to install Shareplex and create a config file on the new source and activate it. The target will have appropriate named Post queues created automatically corresponding to this new source. On target all shareplex processes (old and new) will still be under one sp_cop since shareplex is only using one port # for all sources and the target.
B. Using a new port # for the new Shareplex source.
In this case Shareplex must be started on the new source using a new port #, new SP_SYS_VARDIR and a new config file. This will also involve creating a corresponding Shareplex instance on the existing target using the new port # corresponding to the new source, whereby the target will have more than one vardir. The user will also need to run ora_setup on the existing target for this new vardir. Once that is done, activate the config.
The two approaches are described briefly in Admin Guide Chapter titled "Preparing for SharePlex Replication" sections "Establishing replication for centralized reporting (standard method)" and "Establishing replication for centralized reporting using multiple sp_cop processes". This solution delves on advantages of each approach.
A. Using the same port # for the new Shareplex source.
1. It is easy to configure since you need not create another instance on the existing target.
2. It is less resource intensive on the existing target in terms of the disk space required and the memory usage due to less # of processes involved.
3. It is easy to monitor the target Shareplex since only one Shareplex instance is involved.
B. Using new port # for the new Shareplex source.
1. It is easier to engage in any maintenance work involving one source target pair since one can stop replication for that pair without affecting the other pair.
2. Disk and semaphore contention can be controlled on the target when following this approach.
So the matter is one of the individual preferences based on one's needs.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center