Home / Repstance User Guide / PROCESS CONFIGURATION COMMANDS / Validate Process

Validate Process

The validate command checks that a Capture Process or an Apply Process has what it needs to run. It does not run the process and it does not change anything. The result is Valid or Invalid, and the message tells what is wrong.

What is checked

The parameters. A Capture Process needs its name and the connection to the Source Database: for SQL Server the server, the user and the password, for Oracle the parameters of its connection type (tnsname for tns, or server, user, password and servicename for ezconnect). An Apply Process needs the name of its Capture Process and the connection to the Target Database. When several parameters are missing the message names one of them, fix it and run the command again.
The connection and the database. Repstance connects to the database with the parameters and checks that the database has been prepared for the process (see Validate Database). For a SQL Server Source Database it checks that CDC is enabled, that the schema repi with its tables, trigger and procedures exists and that SQL Server Agent is running (when the database is not a managed service).
The position. When the process has been run, the message shows where it is: the last captured LSN, its time, the trail file and the number of the tables of a Capture Process, and the point where an Apply Process starts. A Capture Process also warns when no table is configured, when a table has no column to replicate and, for Oracle, when a column has an unsupported type.

Command line (repcli)

repcli validate process=capture|apply id=processID

Parameter	Description
process	capture or apply.
id	The identifier of the process.

A Capture Process that has been run:

repcli validate process=capture id=1
[Valid]: Capture process 1 is valid
 Last Captured LSN       : 0x0000008D000083E70007
 Last Captured Timestamp : 2026-10-20 17:07:00.970000
 Trail File Name         : trail/trdemo_cap00000002
 Tables to Replicate     : 4

An Apply Process that has been run:

repcli validate process=apply id=1
[Valid]: Apply process 1 is valid
[Start Point]: First Available Transaction After DB Change 2026/10/20 17:07:00.970 UTC (0x0000008D000083E70007)

A process that lacks parameters, and one whose database cannot be reached (here the name of the server does not exist):

repcli validate process=capture id=4
[Invalid]: password parameter can not be empty

repcli validate process=capture id=2
[Invalid]: lookup db-src.example.com on 10.0.0.5:53: no such host

REST API

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

The body of the request:

{
  "command": "validate",
  "parameters": [
    ["process", "capture"],
    ["id", "2"]
  ]
}

The body of the answer for a process that is valid, and for one that is not. When the status is Invalid the message tells why:

{
  "Status": "Valid",
  "Message": "Capture process 1 is valid\n Last Captured LSN       : 0x0000008D0000844F0007\n Last Captured Timestamp : 2026-10-20 17:11:00.243000\n Trail File Name         : trail/trdemo_cap00000002\n Tables to Replicate     : 4"
}

{
  "Status": "Invalid",
  "Message": "lookup db-src.example.com on 10.0.0.5:53: no such host"
}

HTTP code	Meaning
200	The check has been made. The status is Valid or Invalid.
401	The token is invalid.
422	The request is invalid, for example the process does not exist: the status is Failed and the message is Invalid Process ID has been supplied.

Web UI

Click “Edit” on the card of the process and then “Validate” at the bottom of the form. The result is shown in the form, with the same information as in the message above. The form is described in Edit Replication Processes.

Alter Process

Show Process