Copy Restrictions | Teradata DSA - Copy Restrictions - BAR - Data Stream Architecture

Teradata® DSA User Guide

Product
BAR
Data Stream Architecture
Release Number
17.10
Published
April 2022
Language
English (United States)
Last Update
2022-04-08
dita:mapPath
het1611950545663.ditamap
dita:ditavalPath
vwp1576617377804.ditaval
dita:id
B035-3150
lifecycle
previous
Product Category
Software
Teradata Tools and Utilities
To use the copy operation, the following conditions must be met:
  • Restore access privileges on the target database or table are required.
  • A target database must exist to copy a database or an individual object.
  • When copying a table that does not exist on the destination system, you must have both CREATE TABLE and RESTORE database access privileges for the target database.

No Support for Copying DBC Database

Teradata DSA does not support copying the DBC database, which must be restored after a successful Teradata system initialization. Refer to Full System Restore Using the BAR Portlets or Full System Restore Using the Command Line.

No Support for Copying SYSUDTLIB Database

Teradata DSA does not support copying the SYSUDTLIB database, which is restored when the DBC database is restored.

Restriction on Copying TD_SERVER_DB Database

[Advanced SQL Engine 16.20 and later / Teradata Database 15.10 and later] TD_SERVER_DB database cannot be copied to a different name.