2.16. Tungsten Replicator 6.0.4 GA (11 December 2018)

Version End of Life. 31 July 2020

Release 6.0.4 is a bugfix release.

Improvements, new features and functionality

  • Command-line Tools

    • The trepctl (in [Tungsten Replicator 6.0 Manual]) command previously required the -service (in [Tungsten Replicator 6.0 Manual]) option to be the first option on the command-line. The option can now be placed in any position on the command-line.

      Issues: CT-758

    • If no service is specified then using trepctl (in [Tungsten Replicator 6.0 Manual]) and multiple services are configured, then an error would be reported, but no list of potential services would be provided. This has been updated so that trepctl (in [Tungsten Replicator 6.0 Manual]) will output the list available services and potential commands.

      Issues: CT-759

  • Heterogeneous Replication

    • The continuent-tools-hadoop which was previously available only as a separate Github project is now included with the distribution as standard.

      Issues: CT-748

Bug Fixes

  • Installation and Deployment

    • When using tpm diag (in [Tungsten Replicator 6.0 Manual]), the command would fail to parse net-ssh options.

      Issues: CT-775

    • The Net::SSH internal options have been updated to reflect changes in the latest Net::SSH release.

      Issues: CT-781

  • Heterogeneous Replication

    • Within the Oracle to MySQL ddlscan (in [Tungsten Replicator 6.0 Manual]) templates, the TIMESTAMP datatype in Oracle has been updated to replicate into a DATETIME within MySQL.

      Issues: CT-785

  • Core Replicator

    • Changing the state machine so that RESTORING is not a substate of OFFLINE:NORMAL, but instead of OFFLINE. While a transition from OFFLINE:NORMAL:RESTORING to ONLINE was possible (which was wrong), it will not be possible to transition from OFFLINE:RESTORING to ONLINE.

      The proper sequance of events is: OFFLINE:NORMAL --restore--> OFFLINE:RESTORING --restore_complete--> OFFLINE:NORMAL

      Issues: CT-797

    • Heartbeats would be inserted into the replication flow using UTC even if the replicator had been configured to use a different timezone

      Issues: CT-803