Though this type of configuration is rarely used, it is possible to have a single Shareplex instance replicate data from two source SIDs to one or more targets. The disadvantage here is the complexity involved in controlling two source data streams using a single Shareplex instance. Perhaps an easier way is to create separate Shareplex instances to handle different source SIDs.
Here is the procedure to implement the above:
1. Install Shareplex and apply the patch.
2. Set appropriate value for ORACLE_HOME and ORACLE_SID besides the SP_COP_TPORT, SP_COP_UPORT and SP_SYS_VARDIR when running ora_setup for the first SID.
3. Set appropriate value for ORACLE_HOME and ORACLE_SID besides the SP_COP_TPORT, SP_COP_UPORT and SP_SYS_VARDIR when running ora_setup for the second SID (assuming that only ORACLE_HOME and ORACLE_SID may have changed in the second step).
4. Start Shareplex.
5. Activate the first config file that has the datasource pointing to the first SID.
6. Activate the second config file that has the datasource pointing to the second SID.
7. At this point if you issue "list config", you will see two active config file. Also, "status" will show you two Capture processes and "qstatus" will show you two Capture queue.
