If Dbvisit Replicate stops responding, or the replication appears to be stalled or has slowed down, the following is a first level trouble shooting guide to determine what the issue can be. This guide is a good initial step before contacting Contacting Support
|Issue||Cause and action|
Was the Mine process started on the Mine server?
If no, then start.
If Mine was started, but it stopped without reason, please see MINE or APPLY process stops without any reason.
To restart the Mine process, see Restarting MINE Process
Was the Apply process started on the Apply server?
If no, then start.
If Apply was started, but it stopped without reason, please see MINE or APPLY process stops without any reason
Check the Mine log is being updated. On the Mine server, the Mine log is located in the "log" directory and the file name is similar to dbvrep_MINE_*.log. This log will be updated every few seconds. Check for error messages in the log if the file is not being updated.
|If no, then check if the dbvrep process or service is still running.|
|4||Check the Apply log is being updated. On the Apply server, the Apply log is located in the "log" directory and the file name is similar to dbvrep_APPLY_*.log. This log will be updated every few seconds. Check for error messages in the log if the file is not being updated.||If no, then check if the dbvrep process or service is still running.|
Check that the DBRSCOMMON_HEARTBEAT is still being updated. This table is in the dbvrep schema on both the source and target systems.
The table is updated by determination of the MINE_HEARTBEAT_TIME parameter. The parameter default is set to 10 seconds by can be set according to the needs of the customer. Every 10 seconds the DBRSCOMMON_HEARTBEAT table would be updated with new information such as the timestamp and SCN.
See Heartbeat table for more information and an example SQL statement that can be used to run against the heartbeat table.
|If no, then check the Mine or Apply log for errors.|
|6||Check that the dbvrep process or service is still running|
If not, then check if there is enough memory for the process to run.
Some OS may terminate processes without warning if they consume heavy resources. Check the OS logs for notification of this.
|7||Check if there are any current conflicts. This may pause the replication.||See Viewing the conflicts|
|8||Has the replication slowed down?|
Causes of slowdown: