How to continue replication to a instance with a different target ORACLE_SID after using SP_XPT_A (4213457)

Post queues have been diverted to a new machine with a different target  IP address  using the parameter SP_XPT_ALTERNATE_HOST.
On the new machine oracle instance is brought up with a new SID other than the original target SID name.
Is there a way for  shareplex to post data to this new instance?

When the post queues try to post data, they cannot find the old oracle SID, as it does not exist.

Workaround:

Create a tns alias for the new instance, with the old instance name.
When post process posts the data, the tns alias will point to the new instance.
Post process does not have a problem posting data to the new instance.
This will work well if you have a reverse configuration active as well.  

This is a temporary solution. At some point   the source configuration needs to be reactivated after it is edited with the  new target  SID name.