Kbase P107165: Understand the increase of index blocks after idxbuild
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/16/2008 |
|
Status: Unverified
GOAL:
Understand the increase of index blocks after idxbuild
GOAL:
Why the number of index blocks is incremented after idxbuild
FIX:
When running "idxbuild", the index blocks are made full (with no empty space) and therefore adding a record will generate a new index block to be created.
After a first new block created, the following record(s) added to the same table will generate either a new entry within the same block or a new index block, depending on the fields value.
If you use "idxbuild" to compact your indexes, running an "idxcompact" instead might reduce the number of index block splits and it will prevent new index block to be created on additions of record as the index blocks will not be 100% full, but 80% per default. The command "idxcompact" has been enhanced in OE10 with an additional option "n" for the degree of index compaction which can be specified as an integer >= 50 and <= 100.
proutil db-name -C idxcompact [owner-name.]table-name.index-name [n]
It is to be noted that idxcompact does not change the blocks which are full over the given degree of index compaction (full over 80% per default).