...
The Dbvisit Replicate architecture is a very flexible architecture and consists of a 2- or 3-tier architecture. The architecture components are as follows:
- Mine MINE process, which runs against the source database and "mines" the redo logs for changed data.
- Apply APPLY process, which runs against the target database and applies SQL to the target database.
- Fetcher FETCHER process (optional), which runs against the source database and send archive and online redo logs to mineMINE.
Please see Solutions Diagrams for different flexible configurations and solutions.
...
The 2-tier architecture is the default architecture and consists of the following 2 processes:
- Mine MINE process
- Apply APPLY process
Dbvisit Replicate 3 tier architecture
The optional Fetcher FETCHER process can be used to offload the mine MINE process to another server (downstream mineMINE). The processes in the 3-tier architecture are:
- Fetcher FETCHER process
- Mine MINE process
- Apply APPLY process
All 3 processes can be run on different operating systems and are platform independent.
The direct impact of the fetcher FETCHER process on the source database is negligible, as it just stores small amount of state data and simple queries regarding current state of archive and online redo logs are issued against this database.
...
All the above processes can be on the same server, or on different servers. Dbvisit Replicate uses fast Oracle Call Interface (OCI) for direct connections to the database. The Fetcher FETCHER process is an optional process and is not shown in above diagram.
...
All the above processes can be on the same server, or on different servers. The Fetcher FETCHER process is an optional process and is not shown in above diagram.
Multiple MineMINE, Apply APPLY and Fetcher FETCHER processes are possible for the same replication, enabling simple to complex replication topologies.
...