...
The Dbvisit Replicate architecture is a very flexible architecture and consists of a 2- or 3-tier architecture. The architecture components are as follows:1. Fetcher process (optional)
- Mine process, which runs against the source database
...
- .
...
- Apply process, which runs against the
...
- target database.
...
- Fetcher process (optional), which runs against the
...
- source database and send archive and online redo logs to mine.
Dbvisit Replicate 2 tier architecture
The 2-tier architecture is the default architecture and consists of the following 2 processes:1. Mine
- Mine process
...
- Apply process
Dbvisit Replicate 3 tier architecture
The 3-tier architecture is used to offload the mine process to another server (downstream mine). The processes in the 3-tier architecture are:1. Fetcher
- Fetcher process
...
- Mine process
...
- Apply process
All 3 processes can be run on different operating systems and are platform independent.
The direct impact of the 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.
...
The Dbvisit Replicate two-way architecture is an essence a duplication of the one-way architecture. Each replication from a source to target is a one-way process, but because the replication is going both ways, it is a two x one-way process with the source and target reversed for each process (an inner one-way loop and an one-way outer loop).
Dbvisit Replicate ensures that data that is mined on one database and then replicated to the target database, is not mined again on the target database and replicated back as this would cause an infinite feedback loop.
Dbvisit Replicate does not use intermediate queues or messaging to facilitate the replication.
...