Views, Macros, Stored Procedures, Triggers, UDFs, and UDTs - TARA/ABU

Teradata Archive/Recovery Utility Reference

Product
TARA/ABU
Release Number
16.10
Published
May 2017
Language
English (United States)
Last Update
2018-05-01
dita:mapPath
utr1488824663491.ditamap
dita:ditavalPath
Audience_PDF_include.ditaval
dita:id
B035-2412
lifecycle
previous
Product Category
Teradata Tools and Utilities

Copying a full database archive is the same as a restore operation. Teradata ARC drops all existing objects and dictionary information in the receiving system. The data in the archive is then copied to the receiving database.

However, triggers cannot be copied. If a trigger is defined in a database, <trigger> NOT COPIED is displayed when the COPY statement is processed. This is not an error or warning. Triggers must be manually recreated with SQL.

If the views, stored procedures, and macros have embedded references to databases and objects that are not in the receiving environment, those views, stored procedures, and macros will not work. To make any such views, stored procedures, and macros work, recreate or copy the references to which they refer into the receiving database.

If the views, stored procedures, and macros have embedded references to databases and objects that are in the receiving environment, they will work correctly.

Fully qualify all table, stored procedure, and view names in a macro and all table names in a view. Otherwise, an error can result. When COPY is used, partial names are fully qualified to the default database name. In some cases, this might be the name of the old database.