Restart Cleanup during Mover Process | Teradata Vantage - 17.00 - 17.05 - Restart Cleanup during the Mover Process - Advanced SQL Engine - Teradata Database

Teradata Vantage™ - Database Administration

Product
Advanced SQL Engine
Teradata Database
Release Number
17.00
17.05
Published
June 2020
Language
English (United States)
Last Update
2021-01-22
dita:mapPath
rgu1556127906220.ditamap
dita:ditavalPath
lze1555437562152.ditaval
If an abort or system restart interrupts the Mover process, any transactions in progress are rolled back when the database is back online. Call CleanUpMoveTablesSP to clean up internal tables left over after the abort or restart. For example:
CALL TDMaps.CleanUpMoveTablesSP();

If the system restarts, a DBA needs to manually check the status of the tables that were being assigned to new maps when the restart occurred. The tables may now use new maps, but the status in ActionHistoryTbl may not have been updated yet.

The CleanUpMoveTablesSP procedure may mark tables as aborted that were actually completed. To remedy this, issue a SHOW TABLE request on any tables that are shown as being in progress in the ActionHistoryTbl. The map SHOW TABLE/JOIN/HASH INDEX returns indicates whether or not the map reassignment completed before the status was marked Complete.

For more information on CleanUpMoveTablesSP, including the syntax, see Teradata Vantage™ - SQL Operators and User-Defined Functions, B035-1210.