17.05 - File System: Data Block Update Operations Columns - Teradata Database

Teradata Vantage™ - Resource Usage Macros and Tables

prodname
Advanced SQL Engine
Teradata Database
vrm_release
17.00
17.05
created_date
June 2020
category
Administration
User Guide
featnum
B035-1099-170K

These columns identify the file system operations required when a data block is being updated (BlkUpd). When a block is updated, it can be ‘in place’ and requires no new data blocks, or it could spill over the current data block and require one, two, three or more new data blocks in addition to the current data block. Only logical I/Os and the amount moved (KB) are identified, except for the amount moved for cylinder indexes because they can be calculated by multiplying the current fixed cylinder index size by the I/Os. Data block updates should only be performed on permanent tables (including append and transient journal tables), so no attempt is made to separate permanent and spool data segments.

Column Name Mode Description Data Type
FileCiUpd0IO count Number of cylinder index logical I/Os performed for a block update operation requiring no new data blocks. FLOAT
FileCiUpd1IO count Number of cylinder index logical I/Os performed for a block update operation requiring 1 new data blocks. FLOAT
FileCiUpd2IO count Number of cylinder index logical I/Os performed for a block update operation requiring two new data blocks. FLOAT
FileCiUpd3IO count Number of cylinder index logical I/Os performed for a block update operation requiring three new data blocks. FLOAT
FileCiUpdNIO count Number of cylinder index logical I/Os performed for a block update operation requiring over three new data blocks. FLOAT
FileDbUpd0IO count Number of data block logical I/Os performed for a block update operation requiring no new data blocks. FLOAT
FileDbUpd1IO count Number of data block logical I/Os performed for a block update operation requiring one new data blocks. FLOAT
FileDbUpd2IO count Number of data block logical I/Os performed for a block update operation requiring two new data blocks. FLOAT
FileDbUpd3IO count Number of data block logical I/Os performed for a block update operation requiring three new data blocks. FLOAT
FileDbUpd0KB count KB moved by FileDbUpd0IO. FLOAT
FileDbUpd1KB count KB moved by FileDbUpd1IO. FLOAT
FileDbUpd2KB count KB moved by FileDbUpd2IO. FLOAT
FileDbUpd3KB count KB moved by FileDbUpd3IO. FLOAT
FileDbUpdNKB count KB moved by FileDbUpdNIO. FLOAT
FileDbUpdNIO count Number of data block logical I/Os performed for a block update operation requiring over three new data blocks. FLOAT