Root Cause of Unrecoverable Objects | Teradata Unity - Finding the Root Cause of Unrecoverable Objects - Continuous Availability - Teradata Unity

Teradata® Unity™ Monitoring and Management Guide

Product
Continuous Availability
Teradata Unity
Release Number
17.00
Published
September 2020
Language
English (United States)
Last Update
2020-09-15
dita:mapPath
yuc1569253595897.ditamap
dita:ditavalPath
ft:empty
dita:id
yuc1569253595897
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 Unity. 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