1.12. Tungsten Replicator 5.0.0 GA (7 December 2015)

Version End of Life. 30 June 2018

VMware Continuent for Replication 5.0.0 is a major release that incorporates the following changes:

  • The software release has been renamed. For most users of VMware Continuent for Replication, the filename will start with vmware-continuent-replication. If you are using an Oracle DBMS as the source and have purchased support for the latest version, the filename will start with vmware-continuent-replication-oracle-source.

    The documentation has not been updated to reflect this change. While reading these examples you will see references to tungsten-replicator which will apply to your software release.

  • New Oracle Extraction module that reads the Oracle Redo logs provided faster, more compatible, and more efficient method for extracting data from Oracle databases. For more information, see Oracle Replication using Redo Reader.

  • Security, including file permissions and TLS/SSL is now enabled by default. For more information, see Deployment Security.

  • License keys are now required during installation. For more information, see Deploy License Keys.

  • Support for RHEL 7 and CentOS 7.

  • Basic support for MySQL 5.7.

  • Cleaner and simpler directory layout.

Upgrading from previous versions should be fully tested before attempted in a production environment. The changes listed below affect tpm (in [Tungsten Replicator 2.1 Manual]) output and the requirements for operation.

Improvements, new features and functionality

  • Installation and Deployment

    • During installation, tpm (in [Tungsten Replicator 2.1 Manual]) writes the configuration log to /tmp/tungsten-configure.log. If the file exists, but is owned by a separate user the operation will fail with a Permission Denied error. The operation has now been updated to create a directory within /tmp (in [Tungsten Replicator 2.1 Manual]) with the name of the current user where the configuration log will be stored. For example, if the user is tungsten, the log will be written to /tmp/tungsten/tungsten-configure.log.

      Issues: CONT-1402

Bug Fixes

  • Installation and Deployment

    • During installation, a failed installation by tpm (in [Tungsten Replicator 2.1 Manual]), running tpm uninstall could also fail. The command now correctly uninstalls even a partial installation.

      Issues: CONT-1359

Tungsten Replicator 5.0.0 Includes the following changes made in Tungsten Replicator 5.0.0

Behavior Changes

The following changes have been made to Release Notes and may affect existing scripts and integration tools. Any scripts or environment which make use of these tools should check and update for the new configuration:

  • The Bristlecone load generator toolkit is no longer included with Release Notes by default.

    Issues: CONT-903

  • The scripts previously located within the scripts directory have now been relocated to the standard bin directory. This does not affect their availability if the env.sh (in [Tungsten Replicator 2.1 Manual]) script has been used to update your path. This includes, but is not limited to, the following commands:

    • ebs_snapshot.sh

    • file_copy_snapshot.sh

    • multi_trepctl

    • tungsten_get_position

    • tungsten_provision_slave

    • tungsten_provision_thl

    • tungsten_read_master_events

    • tungsten_set_position

    • xtrabackup.sh

    • xtrabackup_to_slave

    Issues: CONT-904

  • The backup (in [Tungsten Replicator 2.1 Manual]) and restore (in [Tungsten Replicator 2.1 Manual]) functionality in trepctl (in [Tungsten Replicator 2.1 Manual]) has been deprecated and will be removed in a future release.

    Issues: CONT-906

  • The location of the JavaScript filters has been moved to new location in keeping with the rest of the configuration:

    • samples/extensions/javascript has moved to support/filters-javascript

    • samples/scripts/javascript-advanced has moved to support/filters-javascript

    The use of these filters has not changed but the default location for some filter configuration files has moved to support/filters-config. Check your current configuration before upgrading.

    Issues: CONT-908

  • The ddlscan (in [Tungsten Replicator 2.1 Manual]) templates have been moved to the support/ddlscan directory.

    Issues: CONT-909

  • The Vertica applier should write exceptions to a temporary file during replication.

    The applier statements will include the EXCEPTIONS attribute in each statement to assist in debugging. Review the replicator log or trepctl status (in [Tungsten Replicator 2.1 Manual]) output for more details.

    Issues: CONT-1169

Known Issues

The following issues may affect the operation of Continuent Tungsten and should be taken into account when deploying or updating to this release.

  • Core Replicator

    • The replicator can hit a MySQL lock wait timeout when processing large transactions.

      Issues: CONT-1106

    • The replicator can run into OutOfMemory when handling very large Row-Based replication events. This can be avoided by setting --optimize-row-events=false (in [Tungsten Replicator 2.1 Manual]).

      Issues: CONT-1115

    • The replicator can fail during LOAD DATA commands or Vertica loading if the system permissions are not set correctly. If this is encountered, make sure the MySQL or Vertica system users are a member of the Tungsten system group. The issue may also be avoided by removing system file protections with --file-protection-level=none (in [Tungsten Replicator 5.0 Manual]).

      Issues: CONT-1460

Improvements, new features and functionality

  • Command-line Tools

    • The dsctl (in [Continuent Tungsten 4.0 Manual]) has been updated to provide help output when specifically requested with the -h or -help options.

      Issues: CONT-1003

      For more information, see dsctl help Command.

Bug Fixes

  • Core Replicator

    • A master replicator could fail to finish extracting a fragmented transaction if disconnected during processing.

      Issues: CONT-1163

    • A slave replicator could fail to come ONLINE (in [Tungsten Replicator 2.1 Manual]) if the last THL file is empty.

      Issues: CONT-1164

    • The replicator applier and filters may fail with ORA-955 because the replicator did not check for metadata tables using uppercase table names.

      Issues: CONT-1375