16.10 - Stopping Map Reassignments Abruptly - Teradata Database

Teradata Database Administration

Product
Teradata Database
Release Number
16.10
Published
April 2018
Language
English (United States)
Last Update
2018-04-26
dita:mapPath
qjg1509413559832.ditamap
dita:ditavalPath
changebar_rev_16_10_exclude_audience_ie.ditaval
dita:id
ujp1472240543947
To stop a map reassignment job immediately, call the procedure StopMovesTablesSP and specify Y for the StopQueuedActions parameter. For example:
CALL TDMaps.StopMoveTablesSP('Y',
		 :NumActionsStopped, :NumQueuedActionsStopped);
The ActionHistoryTbl records any already queued actions that are stopped .
If a table group is interrupted during the map reassignment process, related tables may be assigned to different maps and may reside on different AMPs for a long time, slowing down request processing. For this reason, Teradata recomends stopping map reassignments gracefully, allowing groups of related tables to stay together.

Do not stop the map reassignment job by issuing ABORT SESSION LOGOFF. That causes the manager session to hang. Calling StopMoveTablesSP releases the manager session. After running StopMoverSP, you need to manually abort the worker sessions.

For more information on StopMoveTablesSP, including the syntax, see SQL Functions, Operators, Expressions, and Predicates.