Example: Revalidating the Partitioning for a Table - Teradata Vantage

Teradata® VantageCloud Lake

Deployment
VantageCloud
Edition
Lake
Product
Teradata Vantage
Published
January 2023
ft:locale
en-US
ft:lastEdition
2024-12-11
dita:mapPath
phg1621910019905.ditamap
dita:ditavalPath
pny1626732985837.ditaval
dita:id
phg1621910019905

Suppose that one of the following events causes you to suspect that incorrect partitioning of the orders table has occurred.

  • You suspect that partitioning is not correct after a restore.
  • You copy the table to a system with different hardware or operating system.
  • A system malfunction has occurred.
  • The data dictionary has not been updated for tables created in an earlier release.

You can validate the partitioning of orders table rows using either of the following ALTER TABLE requests, with the first request deleting any problematic rows and the second moving those rows into a new table.

     ALTER TABLE orders 
     REVALIDATE WITH DELETE;
    
     ALTER TABLE orders 
     REVALIDATE WITH INSERT INTO old_orders;

Now assume that orders is column-partitioned and is named orders_cp. The following ALTER TABLE requests validate the partitioning of orders_cp table rows as in the previous part of this example.

     ALTER TABLE orders_cp 
     REVALIDATE WITH DELETE;
    
     ALTER TABLE orders_cp 
     REVALIDATE WITH INSERT INTO old_orders;