Consider a solution that uses Materialized View Logs in a way that was not intended by Oracle. The idea is to implement fast refresh MV capability for Oracle source and non-Oracle target. I have tested this approach to confirm that it works but I am concerned about long-term consequences of this unintended and unsupported usage.
MY_TAB is the Oracle (11.2) table that I want to mirror in another non-Oracle RDBMS.
The refresh of the target table is applied by an external process invoked by Oracle procedure in the source database. That process accepts the data set extracted from the MV Log, and applies changes to the target. Upon successful execution processed changes are deleted from the MV Log.
MLOG$_MY_TAB is the MV Log for MY_TAB created as: