Data Mover includes a single script that enables you to check status of, start, restart, or stop each Data Mover Component. The script name is dm-control.sh, and is installed by the Data Mover daemon package on the Data Mover Multi-Purpose Server in the directory: /opt/teradata/datamover/daemon/20.00.xx.xx.
- Do not use the dm-control.sh script when Data Mover is configured with high availability. To avoid interference with automatic failover, run dmcluster status from /opt/teradata/client/nn.nn/failover to check component status. If failover is configured, running dmcluster setmaster restarts services.
- Only root users can run the dm-control.sh script or any of the individual Data Mover component scripts, including tdactivemq. Use the dm-control.sh to start/stop Data Mover services if Teradata is not recommending any other method.
The script includes the following commands:
Script Command | Description |
---|---|
dm-control.sh status | Displays status of Data Mover daemon, Data Mover agent, Data Mover sync, tmsmonitor, Analytics Database, Data Stream Controller, and Teradata ActiveMQ. |
dm-control.sh start | Starts all Data Mover components on the local Data Mover Multi-Purpose Server. This includes Data Mover daemon, Data Mover agent, Teradata ActiveMQ, Data Stream Controller, and tmsmonitor. This does not include the Data Mover sync service or the failover monitoring service. |
dm-control.sh stop | Stops all Data Mover components on the local Data Mover Multi-Purpose Server. This includes Data Mover daemon, Data Mover agent, Teradata ActiveMQ, Data Stream Controller, and tmsmonitor. This does not include the Data Mover sync service or the failover monitoring service. |
dm-control.sh restart | Stops and starts all Data Mover components on the local Data Mover Multi-Purpose Server. This includes Data Mover daemon, Data Mover agent, Teradata ActiveMQ, Data Stream Controller, and tmsmonitor. This does not include the Data Mover sync service or the failover monitoring service. |