Log file truncate size (-lgTruncateSize)
- Last Updated: February 11, 2026
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
Use Log file truncate size (-lgTruncateSize) to specify a size for truncating the log file.
| Operating system and syntax | UNIX / Windows |
-lgTruncateSize n |
||
|---|---|---|---|---|
| Use with | Maximum value | Minimum value | Default | |
| Database Server | n/a | 0 | 0 | |
- n
-
A number indicating the maximum size of the database log file in MB before truncating it. 0 indicates that the database log file should not be truncated based on size.
Truncating the log file will not split a message. If the -lgTruncateSize value is reached while a message is being
written, the log file is truncated after the message is completely
written to guarantee that no message is split.
If the database is offline or in single-user mode when the truncate size is reached, the database log file is not truncated. The log file will be truncated the next time the database is brought online in multi-user mode, provided the size is larger than the truncate size specified at startup.
The value for the -lgTruncateSize can be changed while your database is
online with PROMON or the _DbParams VST.
You can use this parameter to support continuous operation of the database. For more information, see Change database parameters while the database is running.