Thanks for the log data.
If they are master and slave, the recommended way to sync them is using the --sync-to-master option
In this case it would be (supposing 10.126.0.120 is the slave, otherwise use 10.126.0.118) :
pt-table-sync --print --charset=utf8 --no-check-triggers --no-foreign-key-checks --databases tksing --tables tender_unit --sync-to-master h=10.126.0.120,u='pttool',p='9CrxYWm3a'
Checkout https://www.percona.com/doc/percona-toolkit/2.2/pt-table-sync.html#usage
Also note that the --print option will make the tool just print the queries needed to run on master to sync the servers, not actually execute them <- you probably were aware of this, but I mention it just in case :-)
https://www.percona.com/doc/percona-toolkit/2.2/pt-table-sync.html#cmdoption-pt-table-sync--print
Thanks for the log data.
If they are master and slave, the recommended way to sync them is using the --sync-to-master option
In this case it would be (supposing 10.126.0.120 is the slave, otherwise use 10.126.0.118) :
pt-table-sync --print --charset=utf8 --no-check-triggers --no-foreign- key-checks --databases tksing --tables tender_unit --sync-to-master h=10.126. 0.120,u= 'pttool' ,p='9CrxYWm3a'
Checkout /www.percona. com/doc/ percona- toolkit/ 2.2/pt- table-sync. html#usage
https:/
Also note that the --print option will make the tool just print the queries needed to run on master to sync the servers, not actually execute them <- you probably were aware of this, but I mention it just in case :-)
https:/ /www.percona. com/doc/ percona- toolkit/ 2.2/pt- table-sync. html#cmdoption- pt-table- sync--print