The trepctl online command puts the replicator into
the online state. During the state change from offline to online various
options can be used to control how the replicator goes back on line. For
example, the replicator can be placed online, skipping one or more
faulty transactions or disabling specific configurations.

The trepctl online command attempts to switch
replicator into the online state. The replicator may need to be put
online because it has been placed offline for maintenance, or due to a
failure.

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.

8.24.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:

When used, replication will start from the next event within the THL.
The event ID provided must be valid. The event cannot be found in the
THL, the operation will fail.

8.24.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:

8.24.3.11.4.2. Going Online Until Specified Event

Replication will go offline when the event ID up to the specified
event has been processed.

8.24.3.11.4.3. Going Online Until Heartbeat

To go online until a heartbeat event:

shell> trepctl online -until-heartbeat

Heartbeats are inserted into the replication stream periodically,
replication will stop once the heartbeat has been seen before the
next transaction. A specific heartbeat can also be specified:

shell> trepctl online -until-heartbeat load-finished

8.24.3.11.4.4. Going Online Until Specified Time

To go online until a specific date and time:

shell> trepctl online -until-time 2014-01-01_00:00:00

Replication will go offline once the transaction being processed at
the time specified has completed.

8.24.3.11.5. Going Online by Force

In situations where the replicator needs to go online, the online
state can be forced. This changes the replicator state to online, but
provides no guarantees that the online state will remain in place if
another, different, error stops replication.

shell> trepctl online -force

8.24.3.11.6. Going Online without Validating Checksum

In the event of a checksum problem in the THL, checksums can be
disabled using the
-no-checksum option:

shell> trepctl online -no-checksum

This will bring the replicator online without reading or writing
checksum information.

Important

Use of the -no-checksum
option disables both the reading and writing of checksums on log
records. If starting the replicator without checksums to get past a
checksum failure, the replicator should be taken offline again once
the offending event has been replicated. This will avoid generating
too many local records in the THL without checksums.