Recovery Log Threshold (-bithold)
- Last Updated: February 11, 2026
- 1 minute read
- OpenEdge
- Version 13.0
- Documentation
Use Recovery Log Threshold (-bithold) to
set the maximum size to which recovery log files can grow.
| Operating system and syntax | UNIX / Windows |
-bithold
n
|
||
|---|---|---|---|---|
| Use with | Maximum value | Minimum value | Single-user default | Multi-user default |
| Database Server | System dependent (Limited by available disk space.) |
System dependent (Limited by available disk space.) |
— | 0 |
- n
-
An integer specifying the threshold, in MB.
The recommended threshold is between 3% and 100% of the largest possible recovery log file
size, rounded to the nearest cluster boundary. During database broker startup, if
-bithold is not specified, it is set to the default value of 0
(disabled). If during database broker startup -bithold is specified, it
must be set to a value greater than or equal to 3. If a -bithold value less
than 3 is specified, the value will be set to 3.
Once the threshold is reached, the database performs an emergency shutdown, unless you have
also specified the -bistall parameter. Using the -bistall
parameter with -bithold prevents the emergency shutdown; instead, the
database ceases activity until one of the following conditions occurs:
- The
-bitholdvalue is increased online. - The database is restarted with a larger
-bitholdvalue to allow transaction backout. - The database is shutdown, the BI file is truncated, and the database is restarted.
Once a -bithold value is set to a value other than 0, it cannot be reset
to 0 (disabled) online. Once enabled, disabling -bithold requires a
database restart.
Recovery Log Threshold (-bithold) can be modified while your database is online through PROMON, PROQUIET, or the _DbParams VST.