About 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.
• 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 login 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.

<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>