Write Requests for Managed Routing | Teradata Unity - 17.00 - Write Requests for Managed Routing - Continuous Availability - Teradata Unity

Teradata® Unity™ User Guide

Product
Continuous Availability
Teradata Unity
Release Number
17.00
Published
September 2020
Language
English (United States)
Last Update
2020-09-15
dita:mapPath
fmz1594836948704.ditamap
dita:ditavalPath
qqk1595871525984.ditaval

For write requests, Unity checks the first response for a successful operation or error code, such as communication failures. If the first response is successful, Unity notifies the client application. If the first response is an error, all active Teradata systems must return a response before the client application is notified.

The active sequencer determines which response is the most common successful response and sends that response back to the client application. If no successful response is available, the most common error response is sent to Unity. If responses come at the same time, the first response that Unity receives returns to the client application.

If the error code specifies the action Exit, Unity returns the error and exits the session on all Teradata systems. If the response indicates a successful operation, Unity compares the results returned from all Teradata systems to determine consistency across the systems. All responses returned by the Teradata systems must match to verify data consistency.

Unity uses the activity count (number of rows) to indicate data consistency for all INSERT, DELETE, UPDATE, and MERGE statements. The activity count from all Teradata systems must match the activity count of the response sent back to the client. The activity count is not checked for any other types of writes. For these type of statements, Unity only checks for statement success or failure. If the activity count or status of the write operation does not match, Unity changes the table state to Interrupted or Unrecoverable depending on the type of statement.