Run any Capture or Apply Processes

The run command starts a Capture Process or an Apply Process, all the processes of one kind, or all the processes. Without parameters it starts every process that is not running. The parameters process and id, the states in which a process accepts the command and the HTTP codes are explained on PROCESS CONTROL COMMANDS.

Command line (repcli)

repcli prints a line for every process the command is meant for: the status in brackets and the message.

Run all the processes. The Capture Process 1 and the Apply Process 1 were stopped:

Run the same command again while the processes are running. Nothing is sent, and each process says why:

Run one process:

A process that does not exist:

A process that has failed can be run again after the cause has been removed. Repstance also runs a failed process again by itself, see Stop/Run Replication Processes.

REST API

• Endpoint: https://repstance_url/control/process
• Method: POST
• Header: Content-Type: application/json and X-Token: token

The body of the request. The element parameters is optional: without it the command is sent to all the processes. The pairs are in the same order as in repcli, process first and then id:

The body of the answer is an array with an element for every process the command is meant for. The element names the process in its message:

What happens when a process runs

• Checks. Before a process starts, Repstance checks that the Source and the Target Databases are configured for the replication. If they are not, the process fails and its message lists the inconsistencies. To check a process in advance see Validate Process.
• First run of a Capture Process. For a SQL Server Source Database it creates the CDC tables it needs and starts from the first LSN that is available in them. For an Oracle Source Database it starts from the current SCN of the database. A transaction that is active at that SCN and is committed after it is captured completely, so the tables stay consistent and no change is lost.
• First run of an Apply Process. It starts from the first transaction in the trail files of its Capture Process. It fails if the Capture Process is not configured or has never been run. To start from another transaction use reset (see Reset Process).
• Changed configuration. A change of the replication objects (see Capture Objects Specification) or of the transformation rules (see Objects Mapping and Possible Transformations) is put into effect when the process is run: the DDL and DML changes are captured with the new criteria. For a SQL Server Source Database CDC is turned off for the objects that are not replicated any more, and they are no longer written to the trail files; for new objects it is turned on.

Web UI

Click “Run All Processes” on the dashboard to run all the processes, or “Run” on the card of a process to run that process. Both ask for a confirmation. The buttons, the confirmations and the state of the cards are shown in Stop/Run Replication Processes.