Creating a Reporting Configuration with a Data Pump on an Intermediary System
You can use an intermediary system as a transfer point between the source and target systems. In this configuration, a data pump on the source system sends captured data to a remote trail on the intermediary system. A data pump on the intermediary system reads the trail and sends the data to a remote trail on the target. A Replicat on the target reads the remote trail and applies the data to the target database.
Figure 10-3 Configuration Elements for Replication through an Intermediary System

Description of "Figure 10-3 Configuration Elements for Replication through an Intermediary System"
When considering this topology, take note of the following:
-
This configuration is practical if the source and target systems are in different networks and there is no direct connection between them. You can transfer the data through an intermediary system that can connect to both systems.
-
This configuration can be used to add storage flexibility to compensate for deficiences on the source or target.
-
This configuration can be used to perform data filtering and conversion if the character sets on all systems are identical. If character sets differ, the data pump cannot perform conversion between character sets, and you must configure Replicat to perform the conversion and transformation on the target.
-
This configuration is a form of cascaded replication. However, in this configuration, data is not applied to a database on the intermediary system. See Creating a Cascading Reporting Configuration to include a database on the intermediary system in the Oracle GoldenGate configuration.