Index consistency check (-IndexCheck)

-IndexCheck {
tablename.indexname | 
ownername.tablename.indexname |   
ownername.tablename.indexname.partitionname
}

ownername

Specifies the owner of the table containing the index you want to check. You must specify an owner name unless the table's name is unique within the database, the table is owned by PUB, or if you are specifying a partition of the index. By default, ABL tables are owned by PUB.

tablename

Specifies the table containing the index to be checked.

indexname

Specifies the name of the index for consistency checking.

partitionname

Specifies the partition of the index for consistency checking.

Use Index consistency check to enable consistency checking for all index blocks in the specified index. When enabled, this option applies consistency checks to all index blocks and index write operations.

Index consistency check validates a block is still physically correct after an operation has been performed. For example, after an index key is inserted into an index block, the consistency check validates that the block still laid out correctly.

You can only specify one index or partition with -IndexCheck. To check multiple partition, apply consistency checking to the entire index. To check multiple indexes, you can apply consistency checking to the entire database with Database consistency check (-DbCheck), or if multiple indexes are in one area, you can apply consistency checking to an entire area with Area consistency check (-AreaCheck).

When specifying the index or index partition to check, the following parsing rules are applied:

• If two variables are supplied, they are interpreted as the table name and the index name (tablename.indexname).
• If three variables are supplied, they are interpreted as the ownername, the table name, and the index name (ownername.tablename.indexname).
• Four variables must be supplied to specify a partition of an index (ownername.tablename.indexname.partitionname).

Index consistency checking can be enabled or disabled while your database is online with PROMON. See PROMON utility for more information.

Index consistency check can be enabled for a single user client or for any offline utility. If the utility is read-only, such as DBANALYS, the -IndexCheck parameter is ignored. Online utilities determine whether or not to perform index consistency checking during execution based on the use of -IndexCheck at broker startup or by the enablement/disablement of the index consistency checking in PROMON.

You can use this parameter to support continuous operation of the database. For more information, see Change database parameters while the database is running.