16.10 - UPDATE DATA INTEGRITY FOR - Teradata Database

Purpose

The UPDATE DATA INTEGRITY FOR command allows you to update the disk I/O integrity checksum level fields of a table type you modified using the DBS Control utility. For more information, see DBS Control (dbscontrol).

Syntax

ALL

All table types (system, system journal, system logging, user, permanent journal, and temporary tables) simultaneously.

SYSTEM

All system table types (for example, data dictionaries and session information) and table numbers0, 1 through 0, 999.

SYSTEM JOURNAL

Transient journals, change tables, and recovery journals.

SYSTEM LOGGING

System and resource usage (RSS) tables.

USER

All user tables (table numbers 0, 1001 through 16383, 65535), which includes the following:

• Stored procedures
• User-defined functions
• Join indexes
• Hash indexes

This also includes fallback for these and secondary indexes for tables and join indexes.

PERMANENT JOURNAL

All permanent journal tables (table uniq[0] IDs 16384 through 32767).

TEMPORARY

All temporary and spool tables (table uniq[0] IDs 32768 through 65535), which includes the following:

• Global temporary tables
• Volatile tables

Usage Notes

This command provides similar functionality as issuing an ALTER TABLE command on an individual table where the data integrity level is changed with the IMMEDIATE option. Performing this operation causes all tables in the table type being updated to be read and have the checksum updated and DBD rewritten. By rewriting the DBD, the checksums are updated to the correct data integrity level automatically. By updating the data integrity level immediately, you can convert back to a lower data integrity level if you previously had to run at a higher level because of corruption problems, but the problem was fixed.

To enable disk I/O integrity checking on an individual table, use the ALTER TABLE command. For detailed information, see “SQL Data Definition Language.

UPDATE DATA INTEGRITY FOR SYSTEM JOURNAL