Oracle connection strings can now be configured using the Oracle TNS name, rather than purely the Oracle service or SID names. To use this option, specify the TNS name using the --datasource-oracle-service option to tpm. This will configure the connection using the service name or TNS name if this can be determined. If the TNS name cannot be resolved automatically, use the --oracle-redo-tnsadmin-home to specify the directory where the Oracle tnsnames.ora file is located.

To use the JDBC listener rather than the TNS service, use the --datasource-oracle-sid option.

Issues: CT-380

Oracle support has been improved, adding support for Oracle TNS naming and support for extracting Oracle RAC using the Oracle Redo Reader functionality.

Support has been added for extracting data from Oracle RAC hosts. To enable extraction from Oracle RAC requires use of the new Oracle service name (TNS) specification, and a different option to tpm to enable different Redo Reader configuration.

To enable extraction from an Oracle RAC instance, use the --oracle-redo-rac-enabled=true option to tpm. In addition, you should specify the connection information to Oracle using the --datasource-oracle-service option to specify the TNS name, and optionally specify the location of the tnsnames.ora file using the --oracle-redo-tnsadmin-home option to tpm.

If your RAC environment uses a different edition ASM than used by the core Oracle deployment, the --oracle-redo-asm-home option can be used to specify the home directory for the ASM version in use.

Currently, this includes an action script for use with Oracle RAC hosts to be used when switching RAC hosts during operation in the event of a failure. The action script can be found in support/oracle-rac-scripts/action_script.scr.

Issues: CT-660, CT-666

The output from thl list now includes the name of the file for the correspnding THL event. For example:

SEQ# = 0 / FRAG# = 0 (last frag)
- FILE = thl.data.0000000001
- TIME = 2018-08-29 12:40:57.0
- EPOCH# = 0
- EVENTID = mysql-bin.000050:0000000000000508;-1
- SOURCEID = demo-c11
- METADATA = [mysql_server_id=5;dbms_type=mysql;tz_aware=true;is_metadata=true;service=alpha;shard=tungsten_alpha;heartbeat=MASTER_ONLINE]
- TYPE = com.continuent.tungsten.replicator.event.ReplDBMSEvent
- OPTIONS = [foreign_key_checks = 1, unique_checks = 1, time_zone = '+00:00', ##charset = US-ASCII]

Issues: CT-550

The replicator has been updated to support the new character sets supported by MySQL 5.7 and MySQL 8.0, including the UTF-8-mb4 series.

Issues: CT-700, CT-970

During installation, tpm attempts to find the system commands such as service and systemctl used to start and stop databases. If these were not in the PATH, tpm would fail to find a start/stop for the configured database. In addition to looking for these tools in the PATH tpm also explicitly looks in the /sbin, /bin, /usr/bin and /usr/sbin directories.

Issues: CT-722

Using tpm diag, the command would ignore options on the command-line, including --net-ssh-option.

Issues: CT-610

When running tpm diag, the operation would fail if the /etc/mysql directory does not exist.

Issues: CT-724

Due to the operating taking a long time or timing out, the capture of the output from lsof has been removed from running tpm diag.

Issues: CT-731

When performing an Oracle installation for applying data, tpm would report an issue with permissions not required for app;ying data into Oracle.

Issues: CT-664

The prepare-offboard-fetcher.pl script has been updated to address an issue with one of the checks made during execution.

Issues: CT-665

The LOAD DATA INFILE would fail to be executed and replicated properly.

Issues: CT-10, CT-652

The trepsvc.log displayed information without highlighting the individual services reporting the entries making it difficult to identify individual log entries.

Issues: CT-659

When replicating data that included timestamps, the replicator would update the timestamp value to the time within the commit from the incoming THL. When using statement based replication times would be correctly replicated, but if using a mixture of statement and row based replication, the timestamp value would not be set back to the default time when switching between statement and row based events. This would not cause problems in the applied host, except when log_slave_updates was enabled. In this case, all row-based events after a statement based event would have the same timestamp value applied.

Issues: CT-686