Salesforce

IDXBUILD: Index packing factor not being recognised always 100%

« Go Back

Information

 
TitleIDXBUILD: Index packing factor not being recognised always 100%
URL NameP133456
Article Number000136903
EnvironmentProduct: OpenEdge
Version: 10.1C, 10.2B, 11.x
OS: All supported platforms
Other: IDXBUILD
Question/Problem Description
Index packing factor not being recognised by IDXBUILD always 100%
IDXBUILD '-pfactor' LT 100 is not being recognised in the "proutil -C idxbuild"
13943 database lg file message always shows packing factor is 100:
(13943) TB value is 24, TM value is 32, SG value is 48, packing factor is 100
idxanalys/Idxblockreport output after IDXBUILD shows that index utilization % above the number provided for -pfactor
IDXBUILD always creates indexes at 100% compaction regardless of the -pfactor specified
Steps to Reproduce
Clarifying Information
Error Message
Defect NumberEnhancement PSC00202371 / OE00170579
Enhancement Number
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.

Resolution
A product enhancement has been logged with development to offer an option to the logic at a per-index level. This enhancement has not been implemented in the product.  As an alternative use the workaround below.
Workaround
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). 
Notes
Keyword Phrase
Last Modified Date9/24/2015 2:51 PM

Powered by