Managed Routing Session Considerations | Teradata Business Continuity Manager - Managed Routing Session Considerations - 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
For managed routing sessions, do the following:
  • Enable proxy authentication.
  • Use NTP to synchronize all time zones. All systems act as one logical system.
  • Do not change DBQL and related configuration settings with Business Continuity Manager in managed sessions. Run those changes directly on each managed Teradata system.
For managed routing sessions, the following options are not supported:
  • XQuery
  • Teradata (QueryGrid) Foreign Server, including Foreign Server definitions and Foreign Server access within SQL code
  • SQL-H
  • Writes that read from system-specific information
    Writes are supported in passive routing, but are not synchronized.
  • Usernames and database objects containing periods, single quotation marks, spaces, or special characters as managed objects
In managed sessions, DDL requests using ETL routing may not achieve expected performance. When processing multiple, simultaneous requests, use passive routing.