Kbase P55020: Progress Explorer: Why value 3 for "bi threshold" has no effect?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/11/2008 |
|
Status: Verified
GOAL:
Progress Explorer: What is the unit for "bi threshold"?
GOAL:
Progress Explorer: Why value 3 for "bi threshold" has no effect?
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
Windows
CAUSE:
Enhancement Request: OE00177365
FIX:
In Progress Explorer, the default the bi threshold is 3, but this does NOT set the -bithold against the database in the conmgr.properties, ie the bi file grow any size within largefile/OS limits.
It is only when this value is changed, in the following Progress Explorer configuration view that 'bi threshold' is set to that value, ie limiting the size of the bi files to -bithold value (in MegaBytes):
PExpl: Databases > dbname > Configurations > defaultConfiguration:
Background Writers - Before-image writer
It is then not easily possible to unset the -bithold through Progress Explorer, ie set to (zero) 0 is taken literally.
To un-set bi stall limits against a database:
a. shut down the adminserver
b. edit the conmgr.properties file and remove the /line/ bithold=<n>
c. restart the adminserver .. note that the 'default' 3 is back
Alternatively, set the bithold value to some more reasonably sized value.