If the Business Continuity Manager system is undergoing planned maintenance, wait until the maintenance window is complete before checking system health.
- Log on to the active or standby Business Continuity Manager server as on of the following:
- Root user
- Another user with sudo privileges
- Teradata user.
- At the Linux prompt, run the following command:
bcm status
- Confirm that the following processes are in a running status:
- Watchdog
- Sequencer
- Endpoint
- All Dispatcher processes
- If a process is not running, run the following command at the Linux prompt to start the process:
bcm start <processName>
- Do one of the following:
Status Action Process started Investigate why the process was not running previously and if the reason is unexpected or cannot be determined, contact Teradata Services. Process did not start - Do one of the following:
- Check if the standby sequencer can reach the managed databases and active sequencer.
- Check if the active sequencer can reach the managed databases and standby sequencer.
- Do one of the following:
- If a sequencer can reach the managed system and other sequencer, run the following command at the Linux prompt:
bcm start <processName>
- If a sequencer cannot reach the managed databases and the other sequencer, open an incident.
- If a sequencer can reach the managed system and other sequencer, run the following command at the Linux prompt:
- At the Linux prompt, run the following command to check how much disk space is left for the partition containing the /data/directory:
df -H
- If the partition is more than 80% full, contact Teradata Services for instructions on removing files in the /data/directory.
- At the Linux prompt, run the following command to check for TVC messages raised since the last check that may be of concern:
grep “BCM:” /var/log/messages
- Do one of the following: