Kbase 13684: When Bi Writes are not 100% - what is writing out the rest
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
When Bi Writes are not 100% - what is writing out the rest
In Promon the Activity screen (option 9.) shows, among other
things the percentage of writes by the BIW. If the Writes by
BIW is not 100% and there are no waits for the BIW, this is to
explain what process is doing the rest of the percentage of writes to
the bi file.
It is easy to explain where the extra BI writes are being done,
although we do not track the writes by individual process so we
cannot say who performed them.
If any process is going to write a DB block (an APW or a server)
and the BI notes associated with that block have not been flushed
to disk, then before the DB block is written, the BI block(s)
containing those notes are written. This is required to insure
that the write ahead logging rule is followed.
Non-BIW BI writes can easily be caused by overly aggressive APWs.
They can also be caused by AIWs if they go to write AI blocks before
the corresponding blocks have been written. The potential for APWs
to do this sort of thing has been greatly reduced in 7.3A with
self-tuning APWs.
Progress Software Technical Support Note # 13684