Critical Event Checks | Teradata Unity - Responding to Critical Events - Continuous Availability - Teradata Unity

Teradata® Unity™ Monitoring and Management Guide
Product
Continuous Availability
Teradata Unity
Release Number
17.00
Published
September 2020
Language
English (United States)
Last Update
2020-09-15
dita:mapPath
yuc1569253595897.ditamap
dita:ditavalPath
ft:empty
dita:id
yuc1569253595897
Product Category
Analytical Ecosystem
  1. Perform the following checks:
    Check Steps
    Client-to-Unity connectivity
    1. Do one of the following:
      • If an application is not functioning, use a basic BTEQ connection to check the network. If possible, run BTEQ from a client system to Unity.
      • If a BTEQ connection is not available, use a telnet connection to the Unity system with port 1025 to check for a listening port. If port 1025 is not available for a connection, contact your IT department.
      • If a connection is not possible from the client system to Unity or is not working, use BTEQ to log on to the Unity system from the Unity system.
        At the Linux prompt, run the following command with a managed database username and password to log in locally through Unity: 
        bteq .logon 127.0.0.1:1025/<user>;
        Specifying port 1025 is required when using BTEQ from the Unity system.

        If the login succeeds from the Unity system but fails from the client system, contact your IT department.
    Unity servers
    1. Log on to each Unity server.
    2. At the Linux prompt, run the following command to confirm all processes are running: 
      unity status
    3. Do one of the following:
      • If the server cannot be reached, contact your IT department.
      • If the server can be reached, confirm Unity processes are running. If they are not running, see Checking Unity System Health.
    Unity operational status At least one managed system must be active for Unity to process requests.
    1. At unityadmin, from the system you think is the primary, run the following command: 
      STATUS;
    2. Do one of the following:
      • If the system is not the primary system, run the command on the other Unity system to see if a failover has occurred.
      • If neither system is primary, check network connectivity between Unity systems.
      • If systems are disconnected, check managed system status and connectivity. See Checking Managed System Health.
      • If managed systems are interrupted, check alerts and sequencer logs. For more information about system interrupts, see Common Reasons for Interrupted Systems.
      • If systems are unrecoverable, queries that use that managed system will fail. Investigate why a system is unrecoverable and open an incident if needed.
    Unity-to-database connectivity
    1. To confirm connectivity is working between the Unity servers and the managed Teradata system, run the following command: 
      /opt/teradata/unity/scripts/connTest.sh -s <tdpid>

      You can repeat this command on each Unity server to confirm that server can connect.
    TVI alerts
    1. At the Linux prompt on the Unity primary server, run the following command to check for critical alert messages:
      grep “Unity:” /var/log/messages
    Critical alerts
    At unityadmin, run the following command to check for critical alerts:
    ALERT LIST;