Database consistency check (-DbCheck)
- Last Updated: March 13, 2026
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
| Operating system and syntax | UNIX / Windows |
|
||
|---|---|---|---|---|
| Use with | Maximum value | Minimum value | Single-user default | Multi-user default |
| CC, DBS | — | — | — | — |
Use Database consistency check to enable consistency checking for all record and index blocks in the entire database. When enabled, this option applies consistency checks to all index blocks and record blocks for record and index write operations.
Database consistency check validates that 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 limit the scope of consistency checking by specifying one area with Area consistency check (-AreaCheck), one table with Table consistency check (-TableCheck), or one index with Index consistency check (-IndexCheck).
Database consistency checking can be enabled or disabled while your database is online with PROMON. See PROMON utility for more information.
Database 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 -DbCheck parameter is ignored. Online utilities
determine whether or not to perform database consistency checking during execution
based on the use of -DbCheck at broker startup or
by the enablement/disablement of the database 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.