16.10 - Verifying Teradata Connection to the ActiveMQ Server - Data Stream Architecture - Data Stream Extensions

Data Stream Extensions Installation, Configuration, and Upgrade Guide for Customers

prodname
Data Stream Architecture
Data Stream Extensions
vrm_release
16.10
created_date
August 2017
category
Configuration
Installation
featnum
B035-3151-087K
All Teradata nodes require a network connection to the Teradata ActiveMQ (TDAMQ) server. The startup listener DSMAIN process runs on the node with the lowest online vproc number and does not start if the TDAMQ server cannot be reached.

If a Teradata system is not on the same network domain as the TDAMQ server, you must update the hosts file with the TDAMQ server IP address.

  1. On every node, run ping TDAMQservername to check the connection to the TDAMQ server. Every node must be able to ping the TDAMQ server.
  2. If DSMAIN did not start, on the node with the lowest online RSG vproc number, look at the startup listener log in /var/opt/teradata/tdtemp/bar for a message to troubleshoot the problem. The startup listener log uses the format BARLog_rsgno_40.txt where rsgno is the lowest RSG vproc number, such as BARLog_26621_40.txt.
    Note: As of Teradata Database 14.10.7.17, 15.0.6.1, 15.10.04.04 and 16.0, the startup listener log has changed from BARLog_rsgno_15.txt to BARLog_rsgno_40.txt.