Common Reasons for Interrupted Systems | Teradata Business Continuity Manager - Common Reasons for Interrupted Systems - 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
Common reasons for interrupted systems include the following:
Reason Resolution
Mismatch on certain DDL statements, for example CREATE DATABASE. Repairing the mismatch.
Timeout during automatic recovery of a long-running transaction. If Business Continuity Manager does not receive a response within the specified recovery timeout, the system interrupts to allow the long-running transaction to complete, then restarts recovery. If this is an ongoing issue, contact Teradata Services.
Dispatcher network timeout while reaching the Sequencer. Check the network stability and contact Teradata Services about adjusting the network timeouts.