Logically Deleted Rows | Teradata Vantage - Logically Deleted Rows - Analytics Database - Teradata Vantage

Teradata Vantageā„¢ - Analytics Database Node Software Migration Guide - 17.20

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-01-27
dita:mapPath
ydx1628095838609.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
B035-5942
Product Category
Teradata Vantage

Rows can be logically deleted for load-isolated (LDI) tables and during certain join index operations. These rows are marked for deletion, but not immediately physically deleted from the database. After the data is restored to the destination system, tables with these rows cannot be revalidated until the rows have been physically deleted.

The post_data_restore script returns a Failure 9899 error when it encounters logically deleted rows. Use the information in the script output to note the tables containing logically deleted rows, and issue an SQL ALTER TABLE RELEASE ROWS statement for each affected table. See Teradata Vantageā„¢ - SQL Data Definition Language Syntax and Examples, B035-1144.