Differences

This shows you the differences between two versions of the page.

--- troubleshooting:replication [2018/07/18 12:24] – Scott Cunliffe
+++ troubleshooting:replication [2025/01/21 22:07] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== Troubleshooter: Replication ======
---> Replication previously set up and running
+The purpose of this troubleshooter is to diagnose why Replication is not being performed.
-Is the master server running
---> Yes
+The symptom of Replication not working is [[object:volume|Volume]] movements executed in the Main database are not being Replicated in the Replication database.
-Is the replicant server running
---> Yes
+To begin diagnosing the problem select from the following options:
-Are the ports used by the master and replicant open and listening
---> Yes
+  * [[troubleshooting:replication:setup_yes|Replication previously set up and running]]
-<--
+  * [[troubleshooting:replication:setup_no|Replication not previously set up]]
---> No
-<--
---> Not sure
---> Checking master to replicant port access
-<--
---> Checking replicant to master port access
-Stop the server
-Open config file and comment out replicant section and save file
-restart server in foreground mode, using the command
-<sxh>
-TMSS10Server -f -h "%TMSS10DB%" -p 5010
-</sxh>
-<--
-<--
-<--
---> No
-Restart the replicant server using the Framework Server Helper, administrative command line or windows services
-<--
-<--
---> No
-<--
---> Not sure
-From an administrative command line window on the master server run the command TMSS10Ping
---> Connection Successful
-From an administrative command line window on the replicant server run the command TMSS10Ping
---> Connection Successful
-<--
---> Connection Unsuccessful
-<--
-<--
---> Connection Unsuccessful
-Restart the master server using the Framework Server Helper, administrative command line or windows services
-<--
-<--
-<--
---> Replication not previously set up
-<--