About Logging SQL Updates on the Slave Server - Teradata Data Mover

Teradata Data Mover User Guide

Product
Teradata Data Mover
Release Number
16.00
Published
December 2016
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
rdo1467305237457.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem

When you start the slave synchronization service, dmSyncSlave.json is created in the specified path as defined by the value of sql.log.directory in sync.properties. The service writes the SQL updates to the file /var/opt/teradata/datamover/logs/dmSyncSlave.json. The slave synchronization service writes SQL statements that the master sends to dmSyncSlave.json, after which the slave service executes the SQL statements using another service on the slave repository. After all SQL statements are executed, dmSyncSlave.json is deleted. If any SQL statements fail to execute, a TVI alert is triggered.