17.10 - Error Handling - Advanced SQL Engine - Teradata Database

Teradata Vantage™ - Database Utilities

Advanced SQL Engine
Teradata Database
Release Number
July 2021
Last Update
Content Type
Publication ID
English (United States)
Last Update

Table Rebuild issues messages interactively.

The following message might be returned by Table Rebuild after processing is complete:

Bad table header on AMP ccc-p for table tablename
This message can be caused by one of the following conditions:
  • The table header does not exist. This might be because the table was dropped after Table Rebuild was started.
  • A header was found, but the table was rebuilt unsuccessfully on the identified AMP.

To recover the table, restore it from the latest archive. If restoring from an archive is not an option, contact the Teradata Support Center.

When a table is marked as being in an invalid state and not redistributable during a system reconfiguration, there is no guarantee that the rows in the table are where they should be. Table Rebuild cannot rebuild the table, and displays “Unable to rebuild due to pending Reconfig Abort of table tablename.” In these cases, before rebuilding the table you should first recover these tables by restoring them from the latest archive, or drop these tables.

Tables that use sparse maps (or contiguous maps that include only a subset of all AMPs in the system) are not necessarily distributed to all AMPs of the system. If a table specified for rebuilding does not exist on an AMP specified in the REBUILD command, Table Rebuild issues the following message:
Unable to rebuild table tablename due to table not in rebuilt AMP
For more information on contiguous and sparse maps, see Teradata Vantage™ - Database Design, B035-1094.

For more information on error messages involving AMP operations, see Teradata Vantage™ - Database Messages, B035-1096.