Kbase P135677: APW does not write to the database anymore
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/18/2009 |
|
Status: Unverified
SYMPTOM(s):
APW does not write to the database anymore
FACT(s) (Environment):
According to the log file the APW connected to the database successfully
According to promon the APWs are completely inactive and do not write to the DB at all anymore:
09/29/08 Activity: Page Writers
08:26:01 09/28/08 22:02 to 09/29/08 08:07 (10 hrs 5 min)
Total Per Min Per Sec Per Tx
Total DB writes 706921 1169 19.48 2.50
APW DB writes 0 0 0.00 0.00
scan writes 0 0 0.00 0.00
apw queue writes 0 0 0.00 0.00
ckp queue writes 0 0 0.00 0.00
scan cycles 0 0 0.00 0.00
buffers scanned 0 0 0.00 0.00
bufs checkpointed 0 0 0.00 0.00
Checkpoints 89 0 0.00 0.00
Marked at checkpoint 661143 1093 18.22 2.34
Flushed at checkpoint 649723 1074 17.91 2.30
OpenEdge 10.1B
Sun Solaris SPARC
CAUSE:
DB directory contained a pipe file with the same name as the DB without extension. This file was used for backup and restore purposes.
Sometime it did not work and left garbage in the pipe. It was observed that the APW process also use such a pipe with the same name.
FIX:
Delete the pipe file from the DB directory and the APWs will work again.