Check Managed System Health | Teradata Business Continuity Manager - Checking Managed System Health - 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
If the Business Continuity Manager system is undergoing planned maintenance, wait until the maintenance window is complete before checking managed system health.
  1. At bcmadmin, run the following command:
    STATUS;
    The expected status for each system is running.
  2. If the status is not running, do one of the following:
    Status Action
    Out-of-Service or Read-Only
    1. Confirm that the system is not undergoing maintenance.
    2. If you need the system to process queries, contact an Administrator, then run the following command from bcmadmin if advised:
      SYSTEM RECOVER;
    Unrecoverable
    1. Do one of the following:
      • If the system was previously active or standby, contact an Administrator to confirm it was not deactivated.
      • If the system is new or unrecoverable because of a user action, resynchronize and activate the system.
      • If the system was previously active or standby, and was not deactivated by an Administrator, open an incident.
    Interrupted (not previously interrupted)
    1. Check alerts for a root cause of the system interrupt.
    2. If the root cause is not apparent and does not resolve on its own, open an incident.
    Disconnected
    1. If there is no planned outage in progress, check connectivity between Business Continuity Manager and the disconnected system. See Responding to Critical Events.
      A system may become disconnected for any of the following reasons:
      • Database for the managed system is not running.
      • Business Continuity Manager User is unable to log on.
      • Business Continuity Manager is unable to reach the managed system over the network.
      • Managed system is not responding to the status request from Business Continuity Manager because the system is busy or the database is unavailable.