Supported Database Objects | Teradata Data Mover - 17.10 - Supported Database Objects - Teradata Data Mover

Teradata® Data Mover User Guide

Product
Teradata Data Mover
Release Number
17.10
Release Date
June 2021
Content Type
User Guide
Publication ID
B035-4101-061K
Language
English (United States)
In general, you cannot copy any database objects that use features that exist in newer versions of Teradata Database to older versions of Teradata Database.
Database Object Name Older to Newer Versions Between Same Versions Newer to Older Versions Restrictions
Databases Can copy entire databases with Teradata DSA. See Copying an Entire Database.
Tables Yes Yes Yes

Cannot copy multi-set tables from newer to older systems when target only has 1 AMP or 1 AMP clusters (Teradata PT Update operator restriction).

Cannot use TPTAPI_LOAD to copy multi-set tables if the allowTptLoadForMultiset table attribute is not set to true.

Full-table copies with tables that have show table output larger than 1MB are not supported. Show table is the text needed to reproduce the table definition. There is no limit to how much data the table can contain.

Cannot use Teradata DSA to copy tables from newer to older versions of Teradata Database.

Cannot use Teradata DSA if the override_lock_access parameter is set to true.

Cannot use Teradata DSA if the source and target TDPIDs are the same.

Cannot use DSA to copy partial tables unless source staging is used.

Global Temporary Tables Yes Yes Yes  
Hash and Join Indexes Yes Yes Yes See Copying Join and Hash Indexes.
Macros Yes Yes Yes The underlying table must already exist on the target system or be copied with the job.
PPI Tables Yes Yes Yes  
Queue Tables Yes Yes No Teradata PT Export operator does not support queue tables.
Schema Yes Yes No

Schema is supported in Teradata Database 16.00 or later.

Teradata DSA and Teradata JDBC support copying tables with an associated schema object.

When copying a table that references a schema object, the schema object must either already exist on the target system or must be copied in the same job.

Data Mover does not relocate or rename schema objects.

Schemas are created only in the SYSUDTLIB database.

If you copy a schema with the same name that exists on the target system and overwrite_existing_objects is set to true, the schema is overwritten if no columns on the target system reference the schema.

Stored Procedures Yes Yes Yes The underlying table must already exist on the target system or be copied with the job.
Table Statistics Yes Yes Yes See About Copying Statistics.
Referencing Tables (parent/child) Yes Yes Yes See About Copying Tables with Referential Integrity.
Tables with LOB Columns Yes Yes Yes

Teradata JDBC is used for newer to older versions of the Teradata Database. You cannot use Teradata JDBC to move tables with more than 15 LOB columns.

Teradata PT API does not support copying data in tables with LOB-based columns.

Tables with Identity Columns Yes Yes Yes Will not copy from newer to older versions if identity column defined with GENERATED ALWAYS statement.
Tables with User-Defined Type (UDT) Columns Yes Yes Yes

UDT must already be defined on target system.

If a job copies a table with UDT columns, the source user and target user must have UDTUSAGE access to SYSUDTLIB to create the job. If a job copies a table with UDT columns and the job uses the Teradata DSA utility, there are no access restrictions for the target user.

Tables with XML, ST_Geometry, JSON Columns Yes Yes Yes

Teradata DSA, and Teradata JDBC support copying tables with XML, ST_Geometry, or JSON column types.

Teradata JDBC is used for copying from newer to older versions of the Teradata Database.

Teradata PT API does not support copying data with these column types.

Due to syntax and format changes in Teradata Database 16.00, compare DLL fails for these column types when copying between systems where one system is earlier than Teradata Database 16.00 and the other is Teradata Database 16.00 or later.

Columnar Tables Yes Yes Yes

Columnar tables with Primary AMP index or Primary Index are supported in Teradata Databases 15.10 or later.

Cannot force the use of TPTAPI_LOAD or TPTAPI_UPDATE.

Triggers Yes Yes Yes See About Copying Triggers.
Views Yes Yes Yes

You must use TPTAPI_UPDATE, TPTAPI_STREAM, T2T, or JDBC to copy view data.

DSA cannot be used when source staging table is not in use.

The TPTAPI_LOAD operator cannot be used.

Foreign Server Objects Yes Yes Yes You can copy foreign server objects only between Teradata Database 15.00 or later.
Function Alias Objects Yes Yes Yes You can copy function alias objects only between Teradata Database 16.20 Feature Update 1 or later.
Users Yes Yes No User must already exist on the target Teradata system. Data Mover moves user objects as database objects. Only the objects within the user are moved. Passwords, permissions, and roles associated with the user are not moved. See About Copying Entire Databases.