Running CheckTable Before a Migration or Upgrade - 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
Running CheckTable is an optional step, however, if you haven't run CheckTable in the past couple of months, it is recommended that you do so now.
  1. Coordinate with the system administrator to determine the priority setting to use for CheckTable, as follows:
    • l = Low
    • m = Medium (default)
    • h = High
    • r = Rush
    You should run CheckTable at level 2 on DBC and level 1 on user tables. (In rare cases, a table may fail during restore because it was corrupted on the source system. Sometimes these tables can be detected on the source by running CheckTable at level 2 on user tables.) This ensures that CheckTable will complete in a reasonable amount of time. Additional information on this issue is located in Tech Alert NTA 2234 available from https://access.teradata.com.
  2. In the Teradata Database Window, open the Supervisor window.
  3. In the Supervisor window, start CheckTable:

    start checktable

    The CheckTable window opens. Do not change the log file.
  4. In the CheckTable window, start a log file of CheckTable output:
    1. Select File > Logging. The Select Log File for window dialog box appears.
    2. Enter the path and file name for the logging file at Filter and Selection. The logging file should be /home/support/ccnumber/preupg_checktable_out.txt.
    3. Click OK.
  5. At the CheckTable command prompt, start a thorough check of DBC system tables: check dbc at level two with no error limit skiplocks priority=m error only;

    CheckTable commands require a semi-colon at the end.

    Use the IN PARALLEL option if there are no users logged on.
  6. Inspect the CheckTable log file for any problems. If CheckTable finds problems with any tables, correct each problem. If necessary, contact the Teradata Global Support Center for assistance. Then repeat the test to check each table skipped due to lock contention. Continue fixing problems until there are no further issues.
  7. Check all tables: check all tables exclude dbc at level one with no error limit skiplocks priority=m error only;
  8. Review the results and address any errors or issues.
    If necessary, open a support incident.
  9. Repeat the test to check each table and correct problems until CheckTable completes with no errors. Example:
    52 table(s) checked.
    31 fallback table(s) checked.
    21 non-fallback table(s) checked.
    1 table(s) bypassed because they are Permanent Journals.
    1 table(s) bypassed due to logical rows of a Join or Hash index.
    0 table(s) failed the check
    0 Dictionary error(s) were found
    Check completed at  time
  10. Quit CheckTable: quit;
  11. Exit logging by selecting File > Logging in the CheckTable window to uncheck Logging.
  12. Close the Database Window if desired.