Copy Journals | Teradata Data Mover - About Copying Journals - Teradata Data Mover

Teradata® Data Mover User Guide

Product
Teradata Data Mover
Release Number
16.20
Published
November 2021
Language
English (United States)
Last Update
2021-11-04
dita:mapPath
wph1512683331242.ditamap
dita:ditavalPath
4101_UG_dm_1620.ditaval
dita:id
B035-4101
lifecycle
previous
Product Category
Analytical Ecosystem

Teradata ARC is required to copy permanent journal data from a source database to a target database. When an attempt is made to copy journal data with Teradata PT API or Teradata DSA, an error results.

When a database that includes a journal is queried, the journal information is displayed in the XML. In the following example, the attribute selection="included" of the <journal> element specifies that the journal should be copied. Other parameters are listed in the table following.

<journals> 
	<journal selection="included">
		<journal_database>west1000</journal_database>
		<name>MyJournal</name>
	</journal>

	<journal selection="included">
		<journal_database>MyDatabase1</journal_database>
		<name>MyDBJournal1</name>
	</journal>
</journals>
Parameters for Journal Table Element
Parameter Description
journal selection Values
  • Specify "included" to copy the journal
  • Specify "unselected" so that the journal is not copied
journal_database Database or user where the journal resides.
name Name of the journal.

When a journal is copied, the entire journal is not copied to the target system. Only journal information for tables being copied as part of the job is copied to the target system. When copying TableA (that uses a journal called JournalABC) and JournalABC as part of the job, only journal information from JournalABC that is associated with TableA is copied to the target. The entire journal table, JournalABC, is not copied to the target.

Rules for Copying Journals

  • Copying data tables that use journals without copying the journal data associated with those tables is valid if the journal table exists on the target. For example, if TableA uses a journal called JournalABC, TableA can be copied without copying JournalABC if JournalABC exists on the target.
  • A journal table must be copied with at least one table that uses that journal, or an error results at job creation time.
  • When overwriting a table on the target, the existing target table must use the same journal as the source table or an error results when copying journal data for the table. For example, if TableA on the source uses a journal called JournalQQQ and TableA on the target uses a journal called JournalYYY, copying TableA from the source to the target overwrites TableA on the target but uses JournalYYY from the existing target table. Trying to copy journal data from JournalQQQ for this table results in an error.
  • If the existing target table has no journal table, the new target table is created with no journaling. Trying to copy journal data for a table that does not use journaling results in an error.
  • Restoring permanent journal data is not supported when the hash bucket size for the target system does not match that of the source system.
  • Journal data cannot be copied when the version of the source system is a prior major release.
  • Journal data cannot be copied when copying data between 32-bit and 64-bit systems because journal row format is different between the two systems.