Read and Write Requests for Passive Routing | Teradata Unity - 17.00 - Read and Write Requests for Passive 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

According to the routing rule definition, passive sessions are opened on only one system. All read and write requests are directed to that system. If a request contains write requests to one or more objects, the objects are compared with the objects in the data dictionary. If a write object exist in the data dictionary and the session associated routing rule does not allow write requests to managed objects, the query is rejected with error code 4530, "Query rejected because associated routing rule prohibits writing to managed objects."

For write requests, because there is only one system, Unity does not perform data consistency checks or keep write requests to managed objects in sync. When a read or allowed write request is done against a Unity-managed object (object exists in data dictionary), access to the object is allowed regardless of the state of the objects. This allows passive sessions (sessions associated with a passive routing rule) to access objects that are unrecoverable or in an otherwise inaccessible state in the data dictionary.