Tungsten Replicator 2.2 Manual

Command-line Tools
To put the replicator online use the standard form of the command:
shell> trepctl online
Going online may fail if the reason for going offline was due to a fault in processing the THL, or in applying changes to the dataserver. The
replicator will refuse to go online if there is a fault, but certain failures can be explicitly bypassed.
6.9.3.11.1. Going Online from Specific Transaction Points
If there is one, or more, event in the THL that could not be applied to the slave because of a mismatch in the data (for example, a duplicate
key), the event or events can be skipped using the -skip-seqno option. For example, the status shows that a statement failed:
shell> trepctl status
...
pendingError : Event application failed: seqno=5250 fragno=0 »
message=java.sql.SQLException: Statement failed on slave but succeeded on master
...
To skip the single sequence number, 5250, shown:
shell> trepctl online -skip-seqno 5250
The sequence number specification can be specified according to the following rules:
• A single sequence number:
shell> trepctl online -skip-seqno 5250
• A sequence range:
shell> trepctl online -skip-seqno 5250-5260
• A comma-separated list of individual sequence numbers and/or ranges:
shell> trepctl online -skip-seqno 5250,5251,5253-5260
6.9.3.11.2. Going Online from a Base Sequence Number
Alternatively, the base sequence number, the transaction ID where replication should start, can be specified explicitly:
shell> trepctl online -base-seqno 5260
Warning
Use of -base-seqno should be restricted to replicators in the master role only. Use on slaves may lead to duplication
or corruption of data.
6.9.3.11.3. Going Online from a Specific Event
If the source event (for example, the MySQL binlog position) is known, this can be used as the reference point when going online and
restarting replication:
shell> trepctl online -from-event 'mysql-bin.000011:0000000000002552;0'
Because events are not sequential numbers, the replicator will go online at the next nearest event id that corresponds to a transaction.
6.9.3.11.4. Going Online Until Specific Transaction Points
There are times when it is useful to be able to online until a specific point in time or in the replication stream. For example, when
performing a bulk load parallel replication may be enabled, but only a single applier stream is required once the load has finished. The
replicator can be configured to go online for a limited period, defined by transaction IDs, events, heartbeats, or a specific time.
The replicator must be in the offline state before the deferred online specifications are made. Multiple deferred online states can be
specified in the same command when going online.
The setting of a future offline state can be seen by looking at the offlineRequests field when checking the status:
shell> trepctl status
...
minimumStoredSeqNo : 0
offlineRequests : Offline at sequence number: 5262;Offline at time: 2014-01-01 00:00:00 EST
pendingError
: NONE
...
224