Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Dbvisit Replicate supports the following functionality.

Functionality included:

  • Full 1-way replication (master to slave).
  • Full 2-way replication (master to master). 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.
  • Full ASM support.
  • bequeath connection to ASM (without listener)
  • Oracle RAC support.
  • Easy to use Setup wizard.
  • MySQL target databases.
  • MS SQL Server target databases.
  • 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.
  • Full support provided. Packing of log files to easily send to support services.

Selected functionality items currently NOT supported:

  • XMLType.
  • Table cluster related DDL.
  • IOTs (index-organized tables).
  • Switchover/failover/flashback.
  • Non-standard redo log block size (including 4k on 11gR2 on Advanced Format disks).
  • NCHAR, NVARCHAR, NVARCHAR2 (character data may be corrupted due to incorrect character set handling).
  • Object datatypes (includes ADT, VARRAY, nested tables etc.).
  • Only English version is available. Different languages will be supported in the future.

Known limitations:

  1. No support for compression or encrypted data (Transparent Data Encryption TDE).
  2. Dbvisit Replicate relies on the target database client settings for handling of NLS issues. For an Oracle target database, set the NLS_LANG environment variable to "AMERICAN_AMERICA.source_db_charset". The AMERICAN_AMERICA part ensures unified number and date formats and specifying the source database charset ensures that the client libraries handle any non-ASCII characters properly.
  • No labels