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
you are using an Oracle DBMS as the source and have
purchased support for the latest version, the filename will
The documentation has not been updated to reflect this
change. While reading these examples you will see references
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 Section 5.1, “Oracle Replication using Redo Reader”.
Security, including file permissions and TLS/SSL is now enabled by default. For more information, see Section 7.5, “Deployment Security”.
License keys are now required during installation. For more information, see Section 2.4, “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 output and the requirements for operation.
The following changes have been made to Continuent Replicator 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:
Tungsten Replicator now requires license keys in order to operate.
License keys are provided to all customers with an active support contract. Login to my.vmware.com to identify your support contract and the associated license keys. After collecting the license keys, they should be placed into
/opt/continuentpath should be replaced with your value for
--install-directory. Place each license on a new line in the file and make sure it is readable by the tungsten system user.
If you are testing VMware Continuent or don't have your license key, talk with your sales contact for assistance. You may enable a trial-mode by using the license key
TRIAL. This will not affect the runtime operation of VMware Continuent but may impact your ability to get rapid support.
The tpm script will display a warning if license keys are not provided or if the provided license keys are not valid.
Tungsten Replicator now enables security by default. Security includes:
Authentication between command-line tools (trepctl) and background services.
SSL/TLS between command-line tools and background services.
SSL/TLS between Tungsten Replicator and datasources.
File permissions and access by all components.
The security changes require a certificate file to be generated prior to operation. The tpm command can do that during upgrade if you are using a staging directory. Alternatively, you can create the certificate and update your configuration with the corresponding argument. This is required if you are installing from an INI file. See Section 7.5.4, “Installing from a Staging Host with Manually Generated Certificates” or Section 7.5.5, “Installing via INI File with Manually Generated Certificates” for more information. This functionality may be disabled by adding
--disable-security-controlsto your configuration.staging-shell>
./tools/tpm update --replace-tls-certificate
For more information, see Section 7.5, “Deployment Security”.
For compatibility with MySQL 5.7, the tpm command will now check for the
super_read_onlysetting and warn if this setting is enabled.
For compatibility with MySQL 5.7, the tpm command will use the
authentication_stringfield for validating passwords.
For compatibility with MySQL 5.7, the tpm command will now ignore the
During some tpm commands, the script will check to see if the release notes have been reviewed and accepted. This may be done by running tools/accept_release_notes from the staging directory. The script will display the information and prompt the user for acceptance. A hidden file will be created on the staging server to mark the release notes have been accepted and the warning will not be displayed.
This process may be automated by calling tools/accept_release_notes -y prior to installation. The script will mark the release notes as accepted and the warning will not be displayed.
During installation, tpm 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 with the name of the current user
where the configuration log will be stored. For example, if the
tungsten, the log will be written to
During installation, a failed installation by tpm, running tpm uninstall could also fail. The command now correctly uninstalls even a partial installation.
The replication user (configured with
--replication-user) has the
The user should not contain data that will be replicated to other hosts.
If the user contains replicated data and filters are used, the results of replication cannot be guaranteed.
A different replication user must be used for each service extracting from the same Oracle Database.
The following changes have been made to Tungsten Replicator 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 scripts previously located within the
scriptsdirectory have now been relocated to the standard
bindirectory. This does not affect their availability if the
env.shscript has been used to update your path. This includes, but is not limited to, the following commands:
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.
The ddlscan templates have been moved to the
The applier statements will include the
EXCEPTIONSattribute in each statement to assist in debugging. Review the replicator log or trepctl status output for more details.
The following issues may affect the operation of Tungsten Replication and should be taken into account when deploying or updating to this release.
The replicator can run into OutOfMemory when handling very large Row-Based replication events. This can be avoided by setting
The replicator can fail during
LOAD DATAcommands 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
A slave replicator could fail to come
ONLINEif the last THL file is empty.