The following warnings appear when attempting to abort/purge a config file that is a part of SharePlex instance containing multiple active config file:
sp_ctrl >abort config <config_file_name>
WARNING! Issuing ABORT/PURGE CONFIG for this configuration will cause data loss for other active configurations on this system if you have not implemented named queues. To prevent this, use named export queues to separate the data.
Please refer to the Release Notes for Version 2.0.2 for instructions.
Are you sure you want to abort config? (N)
Named Export queues are not used in a SharePlex instance containing multiple datasources.
Modify the active config files one by one to have them use named Export queues for their objects. Do this one by one as:
1. Make a copy of the first active config file, edit its entries to have the objects route thru named Export queues and activate the copy.
2. Repeat the steps for other active config files.
From this time on it is safe to use abort config or purge config on the config files involved in replication in this SharePlex instance.
This kind of setup was obscure even though it existed since the inception of SharePlex. The reasons were, even though it offered resource conservation, the maintenance proved to be very cumbersome. With the advent of Pluggable Database in Oracle 12c, where there can be numerous Oracle instances (datasources) per SharePlex instance, this type of configuration is very convenient and not cumbersome. In fact it will be more cumbersome to have one SharePlex instance configured for an Oracle instance in a PDB environment.
