Supplemental logging has been supported by Shareplex 5.1 and up. In fact, starting with Shareplex 6.1, the database needs to have supplemental logging enabled on source for Shareplex to run. The question may arise at times as to whether it is needed to have supplemental logging enabled on target.
N.A.
The supplemental logging only needs to be enabled on the source database. The only time it may be needed on the target (or to put it more aptly, on the secondary) is when the target happens to be a secondary node of a peer-to-peer replication or a High-Availability replication. In a cascading replication environment, the target also happens to be a source so it needs to have supplemental logging enabled. Other than these scenarios, it is not required to have supplemental logging enabled on target. Though leaving it enabled may be useful, should this target need to be converted to a source in a short notice.
To check whether supplemental logging is enabled, issue the following query:
Select supplemental_log_data_min from v$database;
If the output of the above query is YES, then the supplemental logging is enabled. If not, you can enable it by issuing the following SQL as a privileged database user, say SYSTEM or SYS:
ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
ALTER SYSTEM SWITCH LOGFILE;
