This section gives an overview of how Dbvisit Replicate works and the components and architecture of Dbvisit Replicate.
Dbvisit Replicate does not use Logminor, Oracle triggers or database queues for the 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 are appearing in the redo log, they are being written to an external file called a plog and transferred real time to the target server to be applied.
For an introduction into the basic Dbvisit Replicate commands, please see here.