-
If the Teradata ActiveMQ, DSC, and DSA Network Client (ClientHandler) are not running, at the command line, type the following and press Enter after each component string to start the service:
/etc/init.d/tdactivemq start
/etc/init.d/dsc start
/etc/init.d/clienthandler start client_handler_name (optional)
If the client_handler_name parameter is not provided, the command will start all instances if you have multiple DSA Network Client (ClientHandler) instances configured. To specify an instance of DSA Network Client, type /etc/init.d/clienthandler start client_handler_name , where client_handler_name specifies the DSA Network Client instance and refers to the Server ID parameter (usually the hostname).
The SQL Engine / Teradata Database must be active in order to start the DSC service. -
Verify that the services are running:
/etc/init.d/tdactivemq status
/etc/init.d/dsc status
/etc/init.d/clienthandler status client_handler_name (optional)
If the client_handler_name parameter is not provided, the command will start all instances if you have multiple DSA Network Client (ClientHandler) instances configured. To specify an instance of DSA Network Client, type /etc/init.d/clienthandler status client_handler_name , where client_handler_name specifies the DSA Network Client instance and refers to the Server ID (usually the hostname).
To have a fully functional Teradata DSA environment, you must have the Teradata ActiveMQ service, DSC, DSA Network Client (ClientHandler), and Viewpoint running. Follow these steps if you need to restart DSA Services.
The Teradata ActiveMQ service must be running before the DSC and DSA Network Client (ClientHandler) process are started, although, after installation, the DSC and ClientHandler should already be running.