Recovery Log Threshold (-bithold)
- Last Updated: April 23, 2024
- 1 minute read
- OpenEdge
- Version 12.2
- 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
(-bithold is disabled). If during database broker startup
-bithold is specified, it must be set to a minimum value of 3 MB. If a
-bithold value less than 3 MB is specified, the value
will be set to 3 MB. The maximum allowed value for -bithold is 0xFFFFFFFF
(232-1) MB.
Once a -bithold value has been set to a
value other than 0, it cannot be set again to 0 (disabled).
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 the BI extent is emptied.
Recovery Log Threshold (-bithold) can be
modified while your database is online using PROMON or through 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.