Version End of Life. 7 June 2019
Release 5.3.0 is an important feature release that contains some key new functionality for replication. In particular:
JSON data type column extraction support for MySQL 5.7 and higher.
Generated column extraction support for MySQL 5.7 and higher.
DDL translation support for heterogeneous targets, initially support DDL translation for MySQL to MySQL, Vertica and Redshift targets.
Support for data concentration support for replication into a single target schema (with additional source schema information added to each table) for both HPE Vertica and Amazon Redshift targets.
Rebranded and updated support for Oracle extraction with the Oracle Redo Reader, including improvements to offboard deployment, more configuration options, and support for the deployment and installation of multiple offboard replication services within a single replicator.
This release also contains a number of important bug fixes and minor improvements to the product.
The way that information is logged has been improved so that it should be easier to identify and find errors and the causes of errors when looking at the logs. To achieve this, logging is now provided into an additional file, one for each component, and the new files contain only errors at the WARNING or ERROR levels. The new file is
replicator-user.log. The original file,
All log files have been updated to ensure that where relevant the service name for the corresponding entry is included. This should further help to identify and pinpoint issues by making it clearer what service triggered a particular logging event.
Issues: CT-30, CT-69
Due to a MySQL bug, the way that JSON and generated columns is represented within MySQL binary log, it is possible for the size of the data, and the reported size re different and this could cause data corruption To account for this behavior and to prevent data inconsistencies, the replicator can be configured to either ignore, warn, or stop, if the mismatch occurs.
This can be set by modifying the property replicator.extractor.dbms.json_length_mismatch_policy.
Until this problem is addressed within MySQL, tpm (in [Tungsten Replicator 2.1 Manual]) will still generate a warning about the issue which can be ignored during installation by using the
--skip-validation-check=MySQLGeneratedColumnCheck(in [Tungsten Replicator 2.1 Manual]).
For more information on the effects of the bug, see MySQL Bug #88791.
Issues: CT-5, CT-468
The tpm (in [Tungsten Replicator 2.1 Manual]) command has been updated to correctly operate with CentOS 7 and higher. Due to an underlying change in the way IP configuration information was sourced, the extraction of the IP address information has been updated to use the ip addr command.
The THL retention setting is now checked in more detail during
installation. When the
--thl-log-retention (in [Tungsten Replicator 2.1 Manual]) is
configured when extracting from MySQL, the value is compared to
the binary log expiry setting in MySQL
If the value is less, then a warning is produced to highlight
the potential for loss of data.
A new option,
--oracle-redo-temp-tablespace (in [Tungsten Replicator 6.0 Manual])
has been added to configure the temporary tablespace within
Oracle redo reader extractor deployments.
The sizes outputs for the thl list (in [Tungsten Replicator 2.1 Manual]) command,
-sizes (in [Tungsten Replicator 5.2 Manual]) or
-sizesdetail (in [Tungsten Replicator 5.2 Manual]) command now
additionally output summary information for the selected THL
Total ROW chunks: 8 with 7 updated rows (50%) Total STATEMENT chunks: 8 with 2552 bytes (50%) 16 events processed
A new option has also been added,
-sizessummary (in [Tungsten Clustering for MySQL 5.3 Manual]), that only
outputs the summary information.
For more information, see thl list -sizessummary Command.
A new filter has been added,
rowadddbname (in [Tungsten Clustering for MySQL 5.3 Manual]),
which adds the source database name and optional database hash
to every incoming row of data. This can be used to help identify
source information when concentrating information into a single
An issue has been identified with the way certain operating systems now configure their open files limits, which can upset the checks within tpm (in [Tungsten Replicator 2.1 Manual]) that determine the open files limits configured for MySQL. To ensure that the open files limit has been set correctly, check the configuration of the service:
Copy the system configuration:
sudo cp /lib/systemd/system/mysql.service /etc/systemd/system/shell>
sudo vim /etc/systemd/system/mysql.service
Add the following line to the end of the copied file:
Reload the systemctl daemon:
sudo systemctl daemon-reload
service mysql restart
That configures everything properly and MySQL should now take
note of the
When using tpm diag (in [Tungsten Replicator 2.1 Manual]) on a MySQL deployment,
the MySQL error log would not be identified and included
properly if the default
datadir option was
Installation when enabling security through SSL could fail intermittently during installation because the certificates would fail to get copied to the required directory during the installation process.
The Net::SSH libraries used by tpm (in [Tungsten Replicator 2.1 Manual]) have been
updated to reflect the deprecation of
Using a complex password, particularly one with single or double quotes, when specifying a password for tpm (in [Tungsten Replicator 2.1 Manual]), could cause checks and the installation to raise errors or fail, although the actual configuration would work properly. The problem was limited to internal checks by tpm (in [Tungsten Replicator 2.1 Manual]) only.