Page Comparison

The mine process reads the Oracle online redo logs at the source database in real time. The mine process converts information from the Oracle redo log into a Dbvisit Replicate internal format called a PLOG (parsed log). When the information required is no longer in the redo logs, Dbvisit Replicate will automatically switch to the archive logs and switch back to the redo logs when it has caught up. Redo and archive logs using filesystem and ASM are supported. There can be more than one Mine process. Each Mine process will have a unique name which is determined by the user. Example: MINE, MINE2, etc.

The apply process takes the PLOG (created by the mine process) and converts this information into SQL which can be run against the target database. There can be more than one Apply process. Each Apply process will have a unique name which is determined by the user. Example: APPLY, APPLY2, etc.

Fetcher is an optional component. It can be used to offload the mining of the source database to another server. It reads online and archive redo logs at the source database and ships them to the mine process. There can be more than one Fetcher process. Each Fetcher process will have a unique name which is determined by the user. Example: FETCHER, FETCHER2, etc.

Mine reads oracle online redo logs and creates PLOGs (parsed logs). These logs contain parsed information and are filtered to contain information about replicated tables only. PLOGs are binary logs specific to Dbvisit Replicate. The PLOGs are transferred to the target server where they are used by the apply process. PLOGs are platform-independent.