Finishing Pending Operations - Teradata Database

Teradata Database Node Software Migration Guide

Product
Teradata Database
Release Number
16.10
Published
November 30, 2017
Language
English (United States)
Last Update
2018-04-25
dita:mapPath
bkn1504122461303.ditamap
dita:ditavalPath
5942_Migrating_1610.ditaval
dita:id
B035-5942
lifecycle
previous
Product Category
Software

Due to changes in worktable definitions and other considerations, a load operation cannot begin on one release and complete after the migration on a different release. Therefore, there can be no pending data transfer jobs during the migration.

Many tables that are in a pending state are the result of aborted load operations and will never complete loading. These tables must be deleted, with the agreement of the database administrator. Any active load operations should be allowed to finish.

Coordinate with the site Database Administrator to arrange finishing all pending operations and to prevent any new operations until after the migration.

  1. Run CheckTable using the following command:

    check all tables at level pendingop skiplocks priority=h;

  2. Drop any pending tables using the BTEQ command: DROP TABLE databasename.tablename;