Check Object Health | Teradata Business Continuity Manager - Checking Object 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.
If you are using passive routing, you cannot see objects in the active or other states. This is expected.
  1. At bcmadmin, run the following command:
    STATUS;
  2. If the status for any system is not active, do the following:
    Response or Result Action
    STATUS can only be run on the active sequencer The sequencer is not the active sequencer.
    1. Log on to the other sequencer in the cluster.
    2. At bcmadmin, run one of the following commands:
      • View overall status of all components:
        STATUS;
      • See if the cluster is currently in peer state:
        HA STATUS;
    Interrupted sessions
    1. At bcmadmin, run the following command:
      SESSION LIST INTERRUPTED;
    2. Make a note of the error preventing recovery of the system and try to fix it.
    3. If you cannot fix the error, open an incident.
    Interrupted objects
    1. At bcmadmin, run the following command:
      OBJECT LIST INTERRUPTED;
    2. Check the results against previous results.
    3. Fix the error causing the interruption.

      See Interrupted Objects.

    4. Raise an incident in the following cases:
      • Objects are interrupted during multiple recovery attempts and cannot be fixed.
      • The same object is interrupted on all Business Continuity Manager servers.
    Unrecoverable objects
    1. At bcmadmin, run the following command:
      OBJECT LIST UNRECOVERABLE;
    2. If there are new unrecoverable objects that the DBA did not deactivate and you cannot identify the cause, do the following:
      1. Resynchronize the objects.
      2. Open an incident for later investigation.