Cascade Interrupts | Teradata Business Continuity Manager - Cascade Interrupts - 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 an object is interrupted on a system and another SQL statement or session needs to use that object, any other objects used by that session or SQL statement also become interrupted. This is a cascade interrupt.

You do not need to take any direct action to resolve cascade interrupts. Cascade interrupts resolve automatically when the object or session that caused the interrupt is fixed. Resolution may require multiple rounds of automatic recovery.

Example Cascade Interrupted Objects

A cascade alert indicates an object needs another object or session to recover before it can become active. For example:

Alert No.          : 27
Alert Type         : 40033
Alert Description  : A recovery operation on an object has been interrupted. Recovery can continue when the current condition is resolved. Refer to the User Guide for more information.
Alert Details      : Transaction 14 (session 1000) cannot be applied on system 1 (manageddb1) because session 1000 is interrupted.  Table sample.cascade is interrupted.

See Finding Root Cause of Interrupted Objects.