Source Shareplex not sending data to target Shareplex after a new config is activated (4330827)

a. You activated a new config (on the top of the currently active config) that contained an additional target to which some messages are to be routed. However you find that the messages never reach the new target but instead reach the original target which was not the intended recipient. Moreover they also error out as the SID mentioned in the new messages does not exist on the original target as follows:

04/03/08 22:36 Process exited sp_opst_mt  (for o.iqmtg-o.RACOPDB_SPLEX queue va1group1) [pid = 2771] - exit(1)
[-153196864] 04/03/08 22:36 Error: 15001 - No such database as "RACOPDB_SPLEX" in /etc/oratab [sp_opst_mt (for o.iqmtg-o.RACOPDB_SPLEX queue va1group1)/2771]
[-153196864] 04/03/08 22:36 Warning: Failed to set ORACLE_SID/ORACLE_HOME [sp_opst_mt(pdb)/2771]
[-153196864] 04/03/08 22:36 Notice: Can't find home for Oracle SID RACOPDB_SPLEX [sp_opst_mt(pdb)/2771]
04/03/08 22:36 Process launched: sp_opst_mt (for o.iqmtg-o

b. In another scenario, the config was activated on a source but the messages never reach the target but are instead accumulated on source.

Messages routed or attempted to be routed to some invalid target

In both of these situation, the first instinct is to see if there are any network issues or configuration errors for defining hostname, IP address, etc.  But another thing that one may want to look into is to see if there is any value set for the parameter SP_XPT_ALTERNATE_HOST, and to unset it if it was left in a set state inadvertently. This can be verified by issuing "list param modified" or "list param all export" from sp_ctrl on source. By default the parameter is to have a NULL value. The parameter is meant to change the target host conveniently without having to make drastic changes to the active configuration. It may contain some residual value from the past and this may be interfering with the process that sends messages to the correct target host, since the messages are sent to the host with IP value contained in the parameter. To make the change:

a. sp_ctrl>stop export (then issue 'status' to make sure that it is 'stopped by user' and not 'stopping')
b. sp_ctrl>reset param SP_XPT_ALTERNATE_HOST
c. sp_ctrl>start export

These steps should allow messages to flow to the intended target(s).

Here is the description of the parameter:

SP_XPT_ALTERNATE_HOST

This parameter provides an alternate target IP address when you need to connect to a different target machine. The SP_XPT_ALTERNATE HOST parameter allows you  to change your target host without shutting down your active configuration and thus losing your data. The parameter can be used any time you want to change  your target from the one specified in the current active configuration file.

For example, if you are having difficulties with your predefined target host, you can set the parameter to the IP address of your alternate target machine,  stop the Export process and then restart it.