MAPS Support | Copy Objects | Teradata Data Mover - Teradata Database MAPS Architecture Feature Support - Teradata Data Mover

• When using ARC with Teradata Database 16.10 or later, you must set the DBS control internal flag EnableARC4MHM to true. The default is false.
• ARC cannot specify map or colocate details while moving objects or databases at any level.
• ARC requires that the source database and its objects use an all-AMP contiguous map for a full database copy; ARC overwrites the object map on the target database and uses the all-AMP contiguous map.
• Data Mover only validates that ARC MAPS restrictions are met when the configuration parameter databaseQueryService.useBaseViewsOnly is set to true (default). If this parameter is set to false, Data Mover does not default to ARC even when ARC is the only usable copy method. You can set the force utility job parameter to ARC, forcing Data Mover to allow the job to be created and run. However, the following may occur if the ARC MAPS restrictions are not met:
  • ARC fails at run time
  • ARC only copies the object definition and not the object data
• Aster does not support Teradata Database 16.10, and therefore does not support the map and colocate parameters.
• The map and colocate parameters are not supported in databases prior Teradata Database 16.10.
• The target user must have permissions on target maps.
• The target default map is the help session map when the object owner and target login user are the same, or the map is null for the target owner. When the target object owner and the user are different, the system uses the map of the target owner as the target default map. The help session is a query which displays information on the current session, see the Teradata Database Tools and Utilities guide.
• Creating a colocate name is only allowed for sparse maps and can be any valid name, the default name is DatabaseName_TableName.
• DSA supports user-defined map values when copying tables, but does not support user-defined colocate values. When a map is not specified, DSA tries to find a map on the target system with a similar definition as the source table. If no map is found or user does not have permissions for sparse maps, DSA uses the default map.
• When DDL is enabled, make sure the following map and colocate parameters match:
  • If map and colocate parameters exist on the source and target systems, they should match.
  • If map and colocate parameters are provided in a job, then they should match the map and colocate parameters on the target system.

<property>
	<key>map</key>
	<value>false</value>
	<maps>
		<systemLevelMap>
			<system>prodSystem1</system> 
			<map>sparsemap4amp</map>
		</systemLevelMap>
	</maps>
</property>

<dmCreate>
	. . . . . .
	<log_to_even_table><log_to_event_table>
	<map>TD_SparseMap</map>
	<colocate>ColocationName2</colocate>
	. . . . . .
</dmCreate>

<database selection="unselected">
	. . . . . .
	<compare_dll></compare_dll>
	<map>TD_SparseMap</map>
	<colocate>ColocationName2</colocate>
	. . . . . .
</database>