We're here to help!

Dbvisit Replicate Functionality


Dbvisit Replicate supports the following functionality.

Functionality included:

  • Full 1-way replication (master to slave).
  • Full 2-way replication (master to master or active - active). Oracle to Oracle only.
  • Full 3-tier architecture which includes the offloading of the MINE process to another server (using the FETCHER process).
  • Replication of whole databases, schemas, tables or columns.
  • Multiple MINE, APPLY and FETCHER processes in the same replication.
  • Full logging and tracing.
  • Automatic setup of network transportation parameters depending on WAN or LAN network.
  • Network encryption and security using 128bit CAST5 encryption
  • Full ASM support (for ASM 10.2. or higher, ASM 10.1. is not supported)
  • ASM bequeathed connections (without listener)
  • Oracle RAC support.
  • Optimistic commit. Dbvisit Replicate (both MINE and APPLY) does not wait for the commit to start replicating. This ensures there is minimal lag in large transactions and there is no need to hold inflight transactions in queues or memory. 
  • Event Streaming, CDC/Audit to capture changes in source system to enable real time loading of data warehousing or BI. This loads a Dbvisit Replicate created staging table with old and new values plus all the auditing information such as transaction id, changed date, logon user, operation, machine name etc.
  • Parallel APPLY threads for increased performance.
  • Easy to use Setup wizard.
  • One to many support.
  • PL/SQL replication.
  • MySQL target databases.
  • MS SQL Server target databases.
  • Tibero target databases.
  • Postgres target databases.
  • Google SQL target databases.
  • CSV as a target.
  • Hadoop (HDFS) as a target.
  • Kafka as a target.
  • Windows service. On Windows Dbvisit Replicate runs as a service.
  • Managing of the PLOG and log files. Deletes obsolete PLOGs and log files. (With FETCHER, deletes obsolete redo logs delivered to MINE as well.)
  • Notifications and full alerting when thresholds are exceeded or errors occur.
  • SNMP integration to allow for integration with existing monitoring infrastructure.
  • Automatic support packages created to easily send information to Dbvisit support.


Have more questions? Submit a request


  • Avatar


    Our database is running in standalone. We will be planning to implement replication of the database. Due to reduce accessing the production database. We want to access reporting and other purposes from replication database.
    1) How it works?
    2) Shall we need to create separate database for replication?
    3) During the primary db down shall we access replication (Backup database)?
    4) Do we need to but separate licence?

    Please advice.