Do not use database DBC as the target database name in a COPY statement. Use DBC as the source database in COPY FROM, but specify a target database name that is different than DBC. This allows DBC to be copied from a source system to a different database on a target system. When used as the source database in COPY FROM, database DBC is not linked to database SYSUDTLIB. Therefore, only database DBC is copied.
Do not use database SYSUDTLIB as the target database name in a COPY statement. Use SYSUDTLIB as the source database in COPY FROM, but specify a target database name that is different than SYSUDTLIB. This SYSUDTLIB to be copied from a source system to a different database on a target system. When used as the source database in COPY FROM, database SYSUDTLIB is not linked to database DBC. Therefore, only database SYSUDTLIB is copied.
Teradata ARC supports duplicate rows in a copy operation. However, if a restart occurs during the copy of a table with duplicate rows, the duplicate rows involved in the restart may be removed.
When restoring a cluster archive to a reconfigured system, run the cluster archives serially. If this restore scenario is detected by ARCMAIN, the NO BUILD option is automatically enabled, if not specified, and an explicit BUILD command must be run after all restore jobs are completed.
COPY moves an archive copy of a database or table to a new environment. Copy options allow renaming archive databases or creating tables in existing databases. The table does not have to exist in the database it is being copied into. However, because the Teradata Database internal table identifier is different for the new table, access privileges for the table are not copied with the data.
When a database or table copies from an older version source system with a different configuration, it affects the time and space required to copy data to the destination system. The data must be redistributed among the new set of AMPs. The system uses a different algorithm to copy and restore when the number of AMPs is different between the source and destination systems. This new algorithm is usually faster when the configurations are different. The old algorithm may be faster in some restricted situations.
Do not copy a table name generated in a character set different from the default character set or the character set specified in the Teradata ARC invocation. For example, a table name from a multibyte character set archive cannot be copied into a single-byte character set database.
To work around this restriction do the following:
- ANALYZE the archive tape with the HEX runtime option specified.
- Result: The table names are displayed in hexadecimal format (X’ C2C9C72A750A3AC5E4C5E4C36DD9D6E6).
- Run the COPY table statements using the hexadecimal table names.
To copy more than one table or database with one COPY statement, separate the names with commas. Teradata ARC reads the archive data for each COPY statement it processes, therefore one COPY statement yields better performance than multiple COPY statements.