There are occasions when Oracle Export/Import is run in a replication environment. This solution delves on whether Shareplex will capture actions of Oracle Export/Import on source/target respectively.
When Export is run from the source database, Shareplex will not capture its actions. This is regardless of whether the Export is run in conventional mode or in DIRECT mode. The reason being the actions of Oracle Export are not logged in the redologs. The only difference between these two modes of Export is that in case of DIRECT mode the SQL layer is bypassed.
When Import is run on the target database, it can be done in NOLOGGING or LOGGING mode. In case of former, Shareplex will not be affected at all. If the LOGGING mode is used and if there is a reverse config emanating from the target (which can also be termed as secondary), then the Capture process on the secondary will gather changes resulting from the actions of Import. In this case it may be desired to keep Shareplex's Export process stopped on secondary and remove the messages accumulated in Export queue at a later time with help of Support.