Root Cause of Unrecoverable Objects | Teradata Business Continuity Manager - Finding the Root Cause of Unrecoverable 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
  1. If an object has not been made intentionally unrecoverable, collect all DBQL for the object on all managed systems, then open an incident.
    The following is an example of an unrecoverable object alert:
    Alert No.          : 85
    Alert Type         : 40032
    Alert Description  : The object cannot be recovered and synchronized automatically  by Teradata Business Continuity Manager. The object will need to be manually resynchronized. Refer to the User Guide for more information.
    Alert Details      : System 1 (manageddb1) sent an inconsistent message, table sample.cascade is unrecoverable: 
    Transaction: 26
    SQL: 'insert into cascade select * from base;'
    Expected response:  [success] row count 1
    Actual response:  [success] row count 0