TROUBLESHOOTING AND FAQ

When something does not work as expected, start here. The pages of this section answer the usual questions and say what to do about the messages that Repstance prints.

First steps

1. Look at the state of the processes with repcli status. A process that has failed shows its error after the state (see Status of any Capture or Apply Processes).
2. Read the log of the process in /opt/repstance/log, and raise the debug level when the log does not say enough (see Logs and Information for Support).
3. Look at Incident Management in the Web UI, which lists the errors and the warnings of all the processes (see Monitoring Replication).
4. For a problem with the server itself, such as the start-up, the ports or the license key, read the service log with sudo journalctl -u repstance (see Access and Product Validation).
5. When you contact support, send the information that is listed in Logs and Information for Support.

In this section

• Frequently Asked Questions: editions and limits, ports and passwords, replication, restarts, files and disk space.
• Access and Product Validation: the Web UI, repcli and the REST API cannot connect, a password or a token is refused, the server does not start, a command is refused.
• Capture and Source Databases: a Capture Process cannot connect, cannot start, stops, or captures nothing.
• Apply and Target Databases: an Apply Process fails, waits, or starts at the wrong position; a column or a table is missing in the Target Database; triggers and foreign keys of the Target Database; the Target Database cannot be prepared.
• Data Type Conversion: dates held as text, bit and boolean, long strings and decimals, converted with a rule of the Apply Process.
• Logs and Information for Support: where the logs are, the debug level, and what to send to support.