Synchronization Commands | Teradata Data Mover - 17.10 - Synchronization Commands - Teradata Data Mover

Teradata® Data Mover User Guide

Product
Teradata Data Mover
Release Number
17.10
Release Date
June 2021
Content Type
User Guide
Publication ID
B035-4101-061K
Language
English (United States)
Use the Data Mover synchronization service to help you set up the Postgres logical replication. The provided four commands are user-interactive and must be run from the active server, unless otherwise noted.
Command Description
config Runs on the active server only and sets up the publication on the active repository and the subscription on the standby repository. Connects the subscription on the standby repository to the publication on the active repository. There are two options when running the config command:
  • Set up a new replication service between the active repository and one or more standby repositories.
    • This is a fresh setup where either there is no existing publication on the active repository or the active repository needs the publication recreated.
    • This command creates the publication on the active repository and the subscription on the standby repository. It also connects the standby repository to the active repository.
  • Add additional standby repositories to the existing replication service.
    • Run this command when a publication already exists on the active repository.
    • This command creates a subscription on a standby repository and connects that repository to the active repository.
dropconfig Runs on the active server only and drops an existing replication service. There are two options when running the dropconfig command:
  • Drop replication on the active repository server.
    • This option drops the replication service completely on the active and standby servers.
    • Prompts for the standby host name and Postgres user credentials are required.
  • Drop replication on the standby repository servers.
    • This option drops the subscription on the standby repository servers only. Publication on the active repository server remains untouched.
startmonitor Runs on the active server only and starts monitoring data replicated between publication and subscription. The following conditions trigger an alert:
  • Publication does not exist on the active repository
  • Any established standby repository is not active
  • Data replication is slower than the specified threshold
stopmonitor Stops the synchronization monitoring service.