Root Cause of Interrupted Objects | Teradata Business Continuity Manager - Finding Root Cause of Interrupted Objects - 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
When an object becomes interrupted, the session also becomes interrupted. From the alert sent to the DBA, identify the SQL statement that failed on the standby system and any difference in response.
  1. At bcmadmin, run the following command:
    SESSION LIST INTERRUPTED;
    Business Continuity Manager displays the session list. For example:
    bcmadmin> session list interrupted;
    ---------------------------------------------
    BCM Session Number      : 1000
    BCM Transaction ID      : 13
    System                    : exampledb2
    Root Cause                : Yes
    Interrupt Time            : 03/27 13:45:45
    Time of Original Query    : 03/27 13:15:42
    Error Code                : 3807
    Error Text                : Object 'example' does not exist.
    SQL Text                  : insert into example values (25);
    Statement Type            : Insert

    The error in this example indicates that the object example does not exist on the system exampledb2. When you create the object example on the system, the interrupt recovers automatically.