Copy Join and Hash Indexes | Teradata Data Mover - 17.11 - Copying Join and Hash Indexes - Teradata Data Mover

Teradata® Data Mover User Guide

Product
Teradata Data Mover
Release Number
17.11
Release Date
October 2021
Content Type
User Guide
Publication ID
B035-4101-091K
Language
English (United States)
When copying entire databases using DSA, join and hash indexes on the source database are not automatically copied to the target when either relocating the database or when database.copy.joinIndex is not set to true. You must copy join and hash indexes explicitly during a database relocation or during a database copy when database.copy.joinIndex is set to false using the following instructions:
  1. Open the parameters.xml file that has the job definition information for the job.
  2. Create an indices section.
  3. Add the selection="included" attribute to an index element.
  4. Specify the name of the join or hash index using a name element.
  5. Specify the index type using an index_type element. The possible values are HASH_INDEX and JOIN_INDEX.
    DSA automatically copies join or hash indices when the source or target database version is prior 16.20. In this instance, creating an additional indices section is not necessary. In addition, when using DSA on databases with versions earlier than 16.20, extra indices are not supported.

In the following example, the hash index DBName.Orders_hi associated with the DBName.Orders table is copied to the target when copying the database DBName.

<database selection="included">
	<name>DBName</name>
</database>
		<indices>
			<index selection="included">
				<name>Orders_hi</name>
				<index_database>DBName</index_database>
				<index_type>HASH_INDEX</index_type>
			</index>
		</indices>