Compatibility Considerations | Teradata Business Continuity Manager - ​​​​Compatibility Considerations - Teradata Business Continuity Manager

Teradata® Business Continuity Manager Compatibility Matrix

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Teradata Business Continuity Manager
Release Number
1.xx, 2.xx
Published
March 2024
Language
English (United States)
Last Update
2024-03-21
dita:mapPath
dtf1639590758356.ditamap
dita:ditavalPath
ft:empty
dita:id
dtf1639590758356
Product Category
Analytical Ecosystem

The following compatibility observations apply to Business Continuity Manager with Vantage 2.4.

Support/Limitation Compatibility Information
Platform support
  • Business Continuity Manager is available on VMware, Teradata Managed Systems, AWS, Azure, and Google Cloud.
  • Business Continuity Manager supports Teradata Vantage™ on the following platforms:
    • Vantage on-premises (IntelliFlex)
    • Vantage on VMware private cloud
    • Vantage on AWS
    • Vantage on Azure
    • Vantage on Google Cloud
HA-DR System support
  • Business Continuity Manager supports only one active and one standby system.
Table support
  • Due to recovery limitations, limit the use of volatile tables (VTs) and global temp tables (GTTs) in Business Continuity Manager-managed systems. Business Continuity Manager does not support non-deterministic write requests to VTs/GTTs. Deterministic write requests to VTs/GTTs are not recoverable if a failure happens after populating the VTs/GTT and before completing all writes using the VT/GTT.
  • Business Continuity Manager supports write requests to tables that read from GTT, VT, or external tables as the data source and uses CDM by default to replicate the target write table to the standby system. To switch to QueryGrid for replication, set the CDMreplicationforvtgtt parameter to 0. In Business Continuity Manager 1.02.02 and older versions, QueryGrid is the default replication method to replicate the target write table to the standby system.
Routing rules
  • Business Continuity Manager does not change routing rules based on alternative current users defined in Query Bands.
Replication limitations
  • ​​Business Continuity Manager does not replicate the following: ​
    • Changes applied using sessions connected directly to Vantage outside of Business Continuity Manager
      Business Continuity Manager 2.0 and subsequent releases do not have this limitation, as ROS/direct connections are supported.
    • Object names, including usernames, when the name includes: periods, single quotes, and spaces
    • Sessions using Teradata Secure Zones
    • Sessions issuing QueryGrid, SQL-H, or Foreign Server requests
Functionality limitations
  • Business Continuity Manager does not support the following:
    • Expansion servers
    • Debugging of User Defined Functions (UDF)
    • Extended Multiload (MloadX)
    • Load isolation
    • Statement independence
      Business Continuity Manager 2.0 and subsequent releases support statement independence through direct session.
    • TDNEGO authentication
    • Unicode pass-through characters
    • Fastload for the Teradata SQL Driver for Python
      Business Continuity Manager 2.0 and subsequent releases do not have this limitation.
    • Load jobs with non-deterministic DML
    • JDBC FastExport
    • Partition-level locking
    • Size of external data, including Stored Procedures, is limited to 16MB.
      This limitation is specific to ROS.
Objects support
  • Business Continuity Manager supports up to 1 Million objects in managed dictionaries.
  • Business Continuity Manager does not synchronize DBQL objects as the objects are system-specific.
Viewpoint support
  • Business Continuity Manager does not support Viewpoint as Viewpoint is not required to monitor the Business Continuity Manager environment.
System support
  • Business Continuity Manager requires the following:
    • All system-specific statements to be run using system-specific session routing rules
    • All managed Vantage systems and Business Continuity Manager servers to have the date-and-time and time zone synchronized using NTP or similar service
    • All managed Vantage systems to have CDM enabled to replicate statements using non-deterministic functions
    • Proxy-Authorization to be enabled in all managed Vantage systems
    • CDM to be enabled in order to issue CREATE/REPLACE PROCEDURE requests which are greater than 1MB in size
Identity column support
  • Business Continuity Manager uses CDM to replicate statements that use Identity columns and requires Identity columns to be defined such that the columns have different ranges on different systems.
Character set support
  • Business Continuity Manager supports the following character sets: ARABIC1256_6A0, ASCII, EBCDIC, LATIN1250_1A0, LATIN1252_3A0, LATIN1254_7A0, LATIN1258_7A0, LATIN1258_8A0, LATIN9_0A, LATIN1_0A, THAI874_4A0, UTF8, and UTF16.