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 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 Replicator and should be taken into account when deploying or updating to this release.
LOAD DATAcommands requires the correct permissions to be given to the
mysqluser. One of the following must be done.
tungstensystem user must have the same default group as the
mysqlsystem user must be a member of the default group for
--file-protection-leveloption must be set to
noneto allow full visibility to all temporary files.
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
For more information, see ???.
A slave replicator could fail to come
ONLINE if the last THL
file is empty.
The replicator incorrectly assigns
LOAD DATA statements to
#UNKNOWN shard. This
can happen when the entire length is above 200 characters.