Review the following replication considerations for MySQL sources:
Data Replication supports MySQL source databases on Linux and Windows operating systems only.
Data Replication supports MySQL source databases that use the InnoDB storage engine only.
Data Replication supports InnoDB tablespace encryption of source tablespaces and Transparent Data Encryption (TDE) of InnoDB source tables.
The following Data Replication features are not supported for MySQL sources:
Bidirectional replication
Importing or exporting Sync Point values
Managing open transactions from the Data Replication Console or Server Manger CLI
Data Replication cannot replicate data from MySQL source tables that have columns with spatial datatypes such as GEOMETRY.
Data Replication cannot replicate data from MySQL source columns that have the JSON datatype. However, Data Replication can replicate data from source tables that include columns with the JSON datatype, as long as these columns are not mapped in the replication configuration.
If an Extractor task runs on Red Hat Linux 6.5, it cannot extract change data from a remote MySQL database server. However, if an Extractor task runs on Red Hat Linux 7.0 or later, it can extract data from a remote MySQL database server provided that you specify the lib64 directory before the $DBSYNC_HOME/support directory in the LD_LIBRARY_PATH environment variable.
Data Replication captures change events from MySQL binary log files. Do not delete the binary log files until the Extractor has completed log file processing. When the Extractor shuts down, it reports the last log coordinates processed.
After you run replication tasks for MySQL sources, Informatica recommends that you do not change the base name of the binary log files or change the name or location of the directory that contains the log files as specified on the
Extract Range
tab. If you must change the base log file name or change the binary log directory name or location, perform the following actions:
Ensure that the change data in the binary log has been extracted, across all configurations with the MySQL source for which the binary log name will be changed.
Stop all extraction tasks.
To change the base name of the log files, rename the existing log files that were generated with the previous base name.
To change the directory name or location, copy the existing binary log files to the new directory.
From the
Extract Range
tab, edit the base name or directory in the
Base Bin Log File Name
field, for each configuration that includes the MySQL source to which the changes apply.