Critical Event Checks | Teradata Business Continuity Manager - Responding to Critical Events - Teradata Business Continuity Manager

Teradata® Business Continuity Manager Monitoring and Management Guide
Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Teradata Business Continuity Manager
Release Number
1.xx, 2.xx
Published
January 2024
Language
English (United States)
Last Update
2024-02-06
dita:mapPath
wmz1639626084071.ditamap
dita:ditavalPath
ft:empty
dita:id
wmz1639626084071
Product Category
Analytical Ecosystem
  1. Perform the following checks:
    Check Steps
    Client-to-Business Continuity Manager 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 Business Continuity Manager.
      • If a BTEQ connection is not available, use a telnet connection to the Business Continuity Manager 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 Business Continuity Manager or is not working, use BTEQ to log on to the Business Continuity Manager system from the Business Continuity Manager system.
        At the Linux prompt, run the following command with a managed database username and password to log on locally through Business Continuity Manager: 
        bteq .logon 127.0.0.1:1025/<user>;

        If the logon succeeds from the Business Continuity Manager system but fails from the client system, contact your IT department.
    Business Continuity Manager servers
    1. Log on to each Business Continuity Manager server.
    2. At the Linux prompt, run the following command to confirm all processes are running: 
      bcm status
    3. Do one of the following:
      • If the server cannot be reached, contact your IT department.
      • If the server can be reached, confirm that Business Continuity Manager processes are running. If the processes are not running, see Checking System Health.
    Business Continuity Manager operational status At least one managed system must be active for Business Continuity Manager to process requests.
    1. At bcmadmin, from the system you think is the active, run the following command: 
      STATUS;
    2. Do one of the following:
      • If the system is not the active system, run the command on the other Business Continuity Manager system to see if a failover has occurred.
      • If neither system is active, check network connectivity between Business Continuity Manager 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 fails. Investigate why a system is unrecoverable and open an incident if needed.
      • If the active system is available, check the DBS for issues, as an application failure through Business Continuity Manager is valid if the active system returns those errors.
    Business Continuity Manager-to-database connectivity
    1. To confirm connectivity between the Business Continuity Manager servers and the managed Teradata system, run the following command: 
      /opt/teradata/bcm/scripts/connTest.sh -s <tdpid>

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