Stopping Map Reassignments Abruptly - Teradata Database - Teradata Vantage NewSQL Engine

Teradata Vantage™ - Database Administration

Product
Teradata Database
Teradata Vantage NewSQL Engine
Release Number
16.20
Published
March 2019
Language
English (United States)
Last Update
2019-05-03
dita:mapPath
tgx1512080410608.ditamap
dita:ditavalPath
TD_DBS_16_20_Update1.ditaval
dita:id
ujp1472240543947
Product Category
Software
Teradata Vantage
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 recommends 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 Teradata Vantage™ SQL Operators and User-Defined Functions, B035-1210.