Table consistency check (-TableCheck)
- Last Updated: February 11, 2026
- 2 minute read
- OpenEdge
- Version 13.0
- Documentation
Use Table consistency check to enable consistency checking for all record blocks of the specified table or table partition (excluding BLOBS).
| Operating system and syntax | UNIX / Windows |
|
||
|---|---|---|---|---|
| Use with | Maximum value | Minimum value | Single-user default | Multi-user default |
| Client Connection, Database Server | — | — | — | — |
- ownername
- Specifies the owner of the table you want to check. You must specify an owner name unless the table's name is unique within the database, or the table is owned by PUB. By default, ABL tables are owned by PUB.
- tablename
- Specifies the name of the table for consistency checking.
- partitionname
- In a database with partitioned tables, specifies a named partition. Specify the
composite initial partition by using
initialas partitionname.
Table consistency check validates a block is still physically correct after an operation has been performed.
You can only specify one table or partition with -TableCheck. To check multiple partitions, you must check the entire table. To
check multiple tables, you must apply consistency checking to the entire database with Database consistency check (-DbCheck), or if multiple tables are in one area, you
can apply consistency checking to an entire area with Area consistency check (-AreaCheck).
When specifying the table or partition to check, the following parsing rules are applied:
- If one variable is supplied, it is interpreted as a table name.
- If two variables are supplied, they are interpreted as the owner and table name (ownername.tablename).
- Three variables must be supplied to specify a table partition (ownername.tablename.partitionname).
Table consistency checking can be enabled or disabled while your database is online with PROMON. See Manage the OpenEdge Database for more information.
Table 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 -TableCheck parameter is
ignored. Online utilities determine whether or not to perform table consistency checking
during execution based on the use of -TableCheck at broker startup or by
the enablement/disablement of the table consistency checking in PROMON.