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
- 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.
Unable to rebuild table tablename due to table not in rebuilt AMPFor 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.