The trepctl service commands operate per-service, that is, when there are multiple services in a configuration, the service name on which the command operates must be explicitly stated. For example, when a backup is executed, the backup executes on an explicit, specified service.
The individuality of different services is critical when dealing with the replicator commands. Services can be placed into online or offline states independently of each other, since each service will be replicating information between different hosts and environments.
Table 8.40. trepctl Service Commands
|capabilities||List the configured replicator capabilities|
|check||Generate consistency check|
|clear||Clear one or all dynamic variables|
|clients||List clients connected to this replicator|
|flush||Synchronize transaction history log to database|
|heartbeat||Insert a heartbeat event with optional name|
|load||Load the replication service|
|offline||Set replicator to OFFLINE state|
|offline-deferred||Set replicator OFFLINE at a future point in the replication stream|
|online||Set Replicator to ONLINE with start and stop points|
|perf||Print detailed performance information|
|properties||Display a list of all internal properties|
|purge||Purge non-Tungsten logins on database|
|qs||Print a simplified quick reqplicator status|
|reset||Deletes the replicator service|
|setrole||Set replicator role|
|shard||List, add, update, and delete shards|
|status||Print replicator status information|
|unload||Unload the replication service|
|wait||Wait for the replicator to reach a specific state, time or applied sequence number|
The following sections detail each command individually, with specific options, operations and information.