Memory consistency check (-MemCheck)
- Last Updated: June 13, 2025
- 1 minute read
- OpenEdge
- Version 12.8
- Documentation
Memory consistency check (-MemCheck)
| Operating system and syntax | UNIX / Windows |
|
||
|---|---|---|---|---|
| Use with | Maximum value | Minimum value | Single-user default | Multi-user default |
| CC, DBS | – | – | disabled | disabled |
Use Memory consistency check to enable memory overwrite checking for the buffer pool and prevent memory corruption. Memory consistency check detects illegal operations in memory movement, such as a buffer copy with a negative length of data, or a memory move to an incorrect location.
Index and record block operations are checked prior to before-image note writing and the subsequent database block write. The length of the intended operation is checked to prevent operations that exceed database the block size.
Index block splits and index insert operations are checked at strategic points to monitor consistency.
Memory consistency checking is available for both single-user and multi-user environments.
For multi-user environments, it can be enabled or disabled as a startup parameter, with the
_dbparams VST, or using PROMON. See Enable/disable block level consistency check for more information. The parameter is ignored for read-only utilities,
such as DBANALYS.
You can use this parameter to support continuous operation of the database. For more information, see Change database parameters while the database is running.