Managed Routing Session Considerations | Teradata Business Continuity Manager - Managed Routing Session Considerations - Teradata Business Continuity Manager

Teradata® Business Continuity Manager User Guide - 2.00
Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Teradata Business Continuity Manager
Release Number
2.00
Published
August 2024
ft:locale
en-US
ft:lastEdition
2025-01-31
dita:mapPath
sko1694443904278.ditamap
dita:ditavalPath
ft:empty
dita:id
otc1639627713801
lifecycle
latest
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.