Version End of Life. 5 September 2021
Release 6.0.3 is a bugfix release.
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
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,
to specify the directory where the Oracle
tnsnames.ora file is located.
To use the JDBC listener rather than the TNS service, use the
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
option to tpm. In addition, you should
specify the connection information to Oracle using the
option to specify the TNS name, and optionally specify the
location of the
tnsnames.ora file using the
option to tpm.
If your RAC environment uses a different edition ASM than used
by the core Oracle deployment, the
can be used to specify the home directory for the ASM version in
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
Issues: CT-660, CT-666
For more information, see Section 5.2.4, “Deploying on Oracle RAC”.
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]
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
tpm would fail to find a start/stop for the
configured database. In addition to looking for these tools in
PATH tpm also
explicitly looks in the
Issues: CT-10, CT-652
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
was enabled. In this case, all row-based events after a
statement based event would have the same timestamp value