Verify Connection to the ActiveMQ Server | Teradata DSA | DSE | DSU - 17.05 - Verifying Teradata Connection to the ActiveMQ Server - BAR - Data Stream Architecture - Data Stream Extensions

Teradata® DSA - DSE for IBM Spectrum Protect Installation, Configuration, and Upgrade Guide

Product
BAR
Data Stream Architecture
Data Stream Extensions
Release Number
17.05
Release Date
September 2020
Content Type
Configuration
Installation
Publication ID
B035-3155-090K
Language
English (United States)
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. [SQL Engine / Teradata Database 16.0 and later] If you have multiple DSCs, get the list of ActiveMQ servers:
    1. Log on to the database system using bteq.
    2. Issue this command to get a list of the DSCs and their associated ActiveMQ server:
      select cast(activemqserver as char(30)), cast(dscname as char(30)) from sysbar.dsaconnectionstbl;
  2. On every node, run ping TDAMQservername to check the connection to the TDAMQ server. Every node must be able to ping the TDAMQ server.
  3. If DSMAIN did not start, go to the node with the lowest online RSG vproc number, and 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.
    As of SQL Engine 16.20 and Teradata Database 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.