Kbase P145651: Bigrow causes excessive bi growth after upgrading to 10.1C or higher
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
23/02/2010 |
|
Status: Verified
SYMPTOM(s):
Bigrow causes excessive bi growth after upgrading to 10.1C or higher
Before Image file grows large when using bigrow
FACT(s) (Environment):
Using large bi cluster size and/or large bigrow value.
Prior to upgrading, bigrow caused the bi to grow by 4 clusters
proutil <dbname> -C bigrow <value>
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
CHANGE:
Upgraded to 10.1C or above
CAUSE:
Prior to 10.1C, bug# OE00099320 caused bigrow to ignore it's value if the bi cluster size and/or the bigrow size was large. By ignoring the bigrow value, the bigrow command only pre-formatted the bi file by the default 4 bi clusters.
In 10.1C onward, the bigrow value uses a 64-bit integer and therefore removes this limitation.
For example:
10.0B - A database with 256mb bi cluster size running bigrow 60 would cause bigrow to be ignored and would create a 1Gb bi file.
10.1C - A database with 256mb bi cluster size running bigrow 60 would cause bigrow to grow the bi file to 15.3Gb.
CAUSE:
Bug# OE00099320
FIX:
Reduce the bigrow value to a more appropriate number based on your requirements.