DBVisit - solusi alternatif replikasi Oracle DB Standard

Cara cost effective untuk Anda yang memiliki Oracle DB Standard dan ingin menjalankan replikasi , bisa gunakan DBVisit.
Anda tidak harus migrasi ke Oracle DB Enterprise untuk mendapatkan Data Guard. Investasi akan lebih murah, dengan mempertahankan Oracle DB Standard dan membeli DBVisit. Perhitungan licensenya pun mudah.
Tinggal memilih, DBVisit Standby atau DBVisit Replicate.

Dbvisit Product Comparison: Standby or Replicate?

Dbvisit Standby icon Dbvisit Standby
  • Oracle Disaster Recovery solution
  • Performs physical database duplication - the secondary is exactly the same as the primary, both in terms of data and structure
  • Enables DR functions such as Graceful Switchover and Failover, along with creation of the standby database
  • Allows use of standby database in Read-Only mode (when recovery mode is turned off)

Dbvisit Replicate icon Dbvisit Replicate
  • Replicates selected Oracle database environments for the purposes of Data Migration, Reporting, ETL extract solution
  • Performs logical database replication - the target can be a subset of data, and the structure can be different
  • Enables replication between different Oracle versions and operating systems, and the target database can be non Oracle (SQL Server and MySQL).
Dbvisit Product Comparison: Standby vs Replicate
(+) Click image to expand.

Download this overview as a PDF HERE.

Further reading:

Key distinctions between physical and logical replication:

  • Physical replication is a binary copy of the primary or source database. Changes are applied at the lowest level available within the DBMS, ensuring that the target or standby database is an exact replica of the primary database, including all internal database indexes, pointers and tables.
  • A logical replicated database is an independent database that is kept in sync by a replication mechanism that applies updates at the logical level (e.g. via SQL statements). This means that while the data within a logical target database may be the same as that in the primary or source database, the internal database-level structures will be different. This may have implications for some applications, and for the usage of the logical replicated database in the event of a failure. This is important as the database must be viewed not only as a repository of application data, but also a container with its own management and administrative data. For example, if a password is changed in the source database it is not updated in the target, then when it comes to failover the system will not work because of an old password. It also means that, although internal linkages that support referential integrity may be in place in the standby database, these may be physically different than at the primary site, and as a result, may have an impact on the application (e.g. different automatically created foreign key values).
  • Physical replication is all or nothing. Either 100% of the database is replicated or nothing at all.
  • With logical replication it is possible to only replicate a subset of the database in the database (100% replication is also possible).
  • Physical replication is analogous with using a tool such as rsync to synchronize Word document, with rsync replicating the file at the binary file level.
  • A logical standby database is analogous with manually updating a Word document by scanning for changes in the source file and copying them to the right location within the standby file.