In all replications, source must be an Oracle database. Thus, two-way replication with MySQL is not supported.
All target tables must be stored in InnoDB engine, as Dbvisit Replicate depends on correct transaction handling (such as rollback) to reliably restart after a shutdown or failure. The internal tables are stored in InnoDB engine as well. Currently, no DDL replication is supported for MySQL.
...
The following example shows Oracle to MySQL replication. In this example, Oracle and MySQL are running on a single server.
Environment: Virtualbox using Pre-Built Developer VMs (for Oracle VM VirtualBox)
Template name: Database App Development VM
Oracle Linux 5 (32bit)
Oracle RDBMS 11gR2
MySQL Server 5.0.77
MySQL is not installed on the pre-built VM, but this can be installed with:
...
To check if all target tables are stored in InnoDB:
| No Format |
|---|
mysql> SELECT TABLE_NAME, ENGINE FROM information_schema.TABLES where TABLE_SCHEMA = 'YOUR_SCHEMA'; |
To convert the table to InnoDB:
| No Format |
|---|
mysql> ALTER TABLE <table_name> ENGINE=INNODB; |
Currently, no DDL replication is supported for MySQL.
For Dbvisit Replicate to connect to a MySQL database, a MySQL client installation is required. A MySQL client installation is required for:
- Server that runs the setup wizard
- Server that runs the MINE process
- Server that runs the Dbvisit Replicate command console
| Note |
|---|
|