Journaling Restrictions When Using a Staging Table - Teradata Data Mover

Teradata Data Mover User Guide

Product
Teradata Data Mover
Release Number
16.10
Published
June 2017
Language
English (United States)
Last Update
2018-03-29
dita:mapPath
kmo1482331935137.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem

In some cases, a job can copy tables to a staging table when using Teradata ARC. The job then performs INSERT/SELECT statements from the staging table to the target table. If the table does not exist on the target, Data Mover uses the output from SHOW TABLE to create the target table.

The following restrictions apply if a job uses Teradata ARC and a staging table:
  • If the table does not exist on the target and has an associated journal, the associated journal must exist on the target. This applies even if <journaling>false</journaling> is specified for the table.
  • If the table exists on the target and has an associated journal, Data Mover maintains the journal attribute for the target table. This applies even if <journaling>false</journaling> is specified for the table.
The target user must have table creation privileges to create a target table associated with a journal.

If you attempt to apply or copy journal data to a table being copied to a staging table, a create time error results. To avoid this error, set the <journaling> attribute of the table being copied to false.

Data Mover must use a staging table in the following scenarios:
  • If the job copies a table between Teradata Databases and the table has a join or hash index on the source.
  • If the job copies a table and its associated trigger that specifies BEFORE as the action_time parameter.
  • If the job copies a source table that uses foreign keys and the table does not exist on the target.
  • If the job does a partial table copy using Teradata ARC.