...
- In all replications, source must be an Oracle database. Thus, two-way replication with MySQL and SQL Server as target is not supported.
- DDL replication is not supported for MySQL and SQL Server as target. The one DDL command that is supported is TRUNCATE.
- Datatypes must be mapped between Oracle to MySQL/SQL Server otherwise replication may fail. Example: timestamp datatype of Oracle is not available in SQL Server and MySQL (unless >= version 5.6.4).
- Deferrable constraints do not work on MySQL and SQL Server. If you have them on the Oracle side you should disable them.
| No Format |
|---|
Note that even though DDL replication is not supported from Oracle to MySQL/SQL Server with Dbvisit Replicate, the setup wizard can generate target table creation scripts if the DDL-ONLY/DDL_FILE options are selected. The default datatype mappings are broadly compatible, but the APPLY.sh script should be carefully reviewed to ensure that the desired level of precision is in place in your environment, before it is run. Note also that unsupported datatypes will not be excluded from this script, but will generate errors at the prepare phase if the IGNORE_APPLY_DDL_DIFFERENCES parameter is set to YES (the default is NO). |
| Anchor | ||||
|---|---|---|---|---|
|
...