Self-Healing Unrecoverable Tables | Teradata Business Continuity Manager - Self-Healing Unrecoverable Tables - Teradata Business Continuity Manager

Business Continuity Manager self-healing feature can automatically validate, re-synchronize, and re-activate unrecoverable tables. Tables may become unrecoverable when a session encounters data inconsistency with multiple tables involved in the request. Only one of the involved tables may be out of sync. The rest of the tables can be automatically re-synchronized after they are validated.

The table synchronization service uses the QueryGrid T2T connectors to synchronize data across managed Teradata systems.

The table synchronization service only copies the table content and does not create the missing tables. If the service fails with the error code 3807, Object does not exist, the DBA should create the missing tables and associated structures. After the DBA creates the missing tables, Table Sync replicates data to these tables.

If enabled, Business Continuity Manager runs the self-healing feature automatically, with default intervals of 10 minutes, to re-activate unrecoverable tables found to be in-sync. The Business Continuity Manager table synchronization service automatically re-synchronizes other out-of-sync tables.

config update AutoSelfHealingInterval 600 reason 'Enable Self-healing';
config update AutoTableValidateAttempts 1 reason ‘Enable Self-healing’;

config update AutoSelfHealingOptions 1 reason 'Enable Self-healing table sync';

config update DefaultObjectResyncOption 2 reason ‘Enable Self-healing table sync’;

config update DefaultObjectResyncTimeout 600 reason 'Setting global resync timeout';