Kbase 19271: Problem with modifying records per block in areas
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/19/1999 |
|
Title: Records per block problems in 9.0B
KnowledgeBase number:
Creation Date: 09/22/99
Modified Date:
This document applies to: Modifying records per block in areas
network environment
Version: All
Problem:
Resolution
The problem
is that an inordinate number of blocks have to be accessed in order to find
space. The bug is that blocks are being left on the RM chain with too
little free space and if they were not put there then it would be determined
immediately that the database has to be extended in order to get the
requisite free space.
Storage areas that contain records per block of 128 or 256 will end up with
every record block being in the RM chain and unuseable with respect to
getting space. This also means we incur 3 block read opertations reading
blocks at the beginning of the rm chain which we then rotate to the end of
chain. This bug seriously degrades performance for record create
operations.
Besides the performance problems associated with this bug, the following
errors may occur when doing a proutil tabanalysis or dbanalysis..
This could result in many instances of this error..
[Warning] RM block found that should be in the RM free chain. (2802)
dbkey=32256, free space=552, # of free directories=130, hold=0
(3865)
This is reported fixed in the Progress 9.1A release.
See bug 19990730-038