...
| Align |
|---|
The FETCHER process is optional and is not needed when the MINE runs on the primary server. Using the FETCHER process is referred to as the Dbvisit Replicate 3 tier architecture. Dbvisit Replicate 3 tier architecture with the FETCHER processThe 3-tier architecture is used to offload the MINE process to another server (downstream MINE). The processes in the 3-tier architecture are:
All 3 processes can be run on different operating systems and are platform independent. The MINE processes imposes a certain load on the source database when parsing the redo logs (CPU and memory). This maybe around 5% and may not be desirable in certain environments. |
...
This is when the |
...
FETCHER process is very useful. It runs on the source database, reading the redo logs and sending them to |
...
MINE process, which is running on a different machine. |
...
FETCHER process does are:
|
...
|
...
All of the resource-consuming work of parsing the redo logs, writing the |
...
PLOGS and sending them to |
...
APPLY is done by the |
...
MINE process. |