Kbase 13817: dpend: sdpend dbkey, rlwritten, rldepend, rlputmod, bibufs
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
dpend: sdpend dbkey, rlwritten, rldepend, rlputmod, bibufs
Under certain circumstances, the following errors may occur:
dpend: <n> sdpend <n> dbkey: <y>
rlwritten: <n> , rldepend <n>
rlputmod: dpend <n> already written
This would then result in an abnormal shutdown of the database.
The errors do not indicate database corruption.
To avoid the errors, increase the -bibufs parameter to 30 or higher.
There is no "rule of thumb" regarding how high to set the -bibufs
parameter, however 30 is good for most databases. If after setting
-bibufs to 30 the errors re-occur, set -bibufs higher to 50 or higher.
Each bi buffer takes up 1K of memory. There are no adverse
consequences to setting -bibufs too high, although anything over
1,000 is likely excessive and would be using up memory unnecessarily.
These errors can occur in V6.3 and V7. This issue is fixed in 7.3C
and above.
OCT-30-1995
DESCRIPTION OF PROBLEM:
The problem can only occur when there are no free bi buffers. It is a
race condition in that two user's processes try to put the current bi
output buffer on the bi modified buffer list at the same time. This
race condition can only occur if there are no free bi buffers. That
is why adding more bi buffers is usually a good work around. When
more bi buffers are added, it becomes less likely that they will all
be on the filled bi buffer list. In addition to having a lot of bi
buffers, it is important to run a BIW writer and have well tuned
asynchronous page writer(s). Most importantly, the page writer(s)
should not be overly aggresive, ie flush modified buffers as soon as
they are modified.
Progress Software Technical Support Note # 13817