Recover from a Broken Sync Service | Teradata Data Mover - Use Case: Recover from a Broken Synchronization Service - Teradata Data Mover

Teradata® Data Mover User Guide

Product
Teradata Data Mover
Release Number
17.05
Published
October 2020
Language
English (United States)
Last Update
2020-11-18
dita:mapPath
xxl1591023586203.ditamap
dita:ditavalPath
mpm1591127278842.ditaval
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem

When data sent to the standby server cannot be inserted, deleted, or modified successfully, the synchronization service is not working correctly due to either a bad foreign key issue or a duplicate primary key. Perform the following if the synchronization service is not working as expected:

  1. Drop this standby server from the synchronization service by following the steps in Use Case: Drop One Standby Server from the Synchronization Service.
  2. Add the server back by following the steps in Use Case: Add an Extra Standby Server to an Existing Active Server.