Write Requests for Managed Routing | Teradata Business Continuity Manager - Write Requests for Managed Routing - Teradata Business Continuity Manager

Teradata® Business Continuity Manager User Guide

Product
Teradata Business Continuity Manager
Release Number
1.0
Published
January 2022
Language
English (United States)
Last Update
2022-01-27
dita:mapPath
otc1639627713801.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-2550
lifecycle
previous
Product Category
Analytical Ecosystem
Business Continuity Manager runs the write request on the active system first. Based on the response from the active system, Business Continuity Manager performs one of the following:
  • If the write request succeeds, Business Continuity Manager sends the response to the client application. The write request is then run on the standby system.

    Business Continuity Manager compares the activity count (number of rows affected) and status code from the standby system with the active system.

    • If the write request fails on the standby system, Business Continuity Manager marks the affected tables as interrupted. Business Continuity Manager periodically retries the write request to recover the request.
    • If there is a mismatch in the activity count, Business Continuity Manager marks the affected tables as unrecoverable. Optionally, Business Continuity Manager can use the Table Sync feature to re-synchronize the table by copying data to the out-of-sync tables.
  • If the write request fails, Business Continuity Manager sends an error to the client application and does not replay the request on the standby system.