Shut Down Replication

Caution: Propagating the transaction log to disk will fail if processes are making database changes. As such the replication service must be stopped before attempting to propagate the log. Refer to Propagate the In-Memory Changes and Condense the Log.

1. Using PuTTY or your preferred terminal window, connect to the accelerator server and login as the root user.

2. Change directory to /opt/attunity/replicate/bin.

   # cd /opt/attunity/replicate/bin

3. Switch user to the attunity replication user.

   # su attunity

4. Get a list of all the running replication tasks.

   # ps -ef | grep repctl

   

   Caution: The running replication tasks are the processes that start repctl reptasksrv <TASK_NAME>. In the example above there are three running tasks:

   • PRODDTA

   • CUSTOM TABLES

   • JDE812

5. For each task returned by the above, run the following command to get the status of the task and if it is running to stop the replication task. (You can also stop the tasks in the Qlik Console, but you should check the status as instructed below)

   # ./repctl connect\; gettaskstatus <TASK_NAME>\; disconnect 

   # ./repctl connect\; stoptask <TASK_NAME>\; disconnect

   Caution: The stoptask command used above will signal the task to stop, if the task is currently showing latency, then the task will not stop immediately but will stop after processing the changes that are causing the latency. This will allow you to restart the task with the resume feature, this means you do not need to reload the data. If you run the stoptask command and manually kill the associated replication process, then you will not be able to use the resume command to restart the task, you will have to restart the task using the reload functionality in order to ensure data consistency. All the tasks must be stopped before moving on to Step 6 and 7.

6. Exit from attunity user to return to the root user:

   # exit

7. Change directory to /etc/init.d:

   # cd /etc/init.d

8. Shut down replication service. This will prevent users from connecting remotely using Qlik Console and starting new tasks.

   # ./areplicate stop

9. Confirm that the services has stopped by checking that there are no repctl processes running:

   # ps -ef | grep repctl