Kbase P133456: Index packing factor not being recognised always 100%
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
21/07/2008 |
|
Status: Unverified
SYMPTOM(s):
Index packing factor not being recognised always 100%
idxbuild '-pfactor' LT 100 is not being recognised in the "proutil -C idxbuild"
the 13943 database lg file message always shows packing factor is 100
idxbuild always creates indexes at 100% compaction
FACT(s) (Environment):
OpenEdge 10.1C
OpenEdge Category: Database
CAUSE:
If the database is Large Key Entries (LKE) enabled and database blocksize is 4KB, -pfactor will be reset to 100. This is due to block size/maximum index entry limits. The requirement that there should be room for at least two entries in any index block is the reason for this enforcement. Since the size of two LKE entries plus overhead can approach 4k, the -pfactor has to be reset to 100 to ensure it.
There is an important rule in index manager: each index block must be able to at least contain two entries. If each index block first has to be verified for this condition, the performance of idxbuild will be slower. In essence, this is a compromise to keep inline with the idxbuild performance enhancements in OpenEdge releases.
FIX:
Large Key Entries (LKE) are enabled by default since OpenEdge 10.1B and there is no current method to disable this feature. Effectively, this feature cannot be used without first converting to an 8KB database (dump and load).
A product enhancement has been logged with development to offer an option to the logic at a per-index level.