This section gives an overview of how Dbvisit Replicate works and the components and architecture of Dbvisit Replicate.
Dbvisit Replicate does not use Logminer, Oracle triggers or database queues for replication. Dbvisit Replicate uses its own internal log mining technology to capture the changes as they are written to the redo logs (or archived redo logs). As the changes appear in the redo log, they are written to an external file called a PLOG and transferred in real time to the target server to be applied to the target database.
For an introduction into the basic Dbvisit Replicate commands, please see here.