Kbase P79507: Database background writers do not auto start through AdminServer
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/30/2008 |
|
Status: Unverified
SYMPTOM(s):
Database background writers (APW, BIW and WDOG) do not auto start.
Database is started through AdminServer / AdminService.
A high value for the -B parameter is being used.
Error in startup of watchdog process for database <dbname>
Message: <time> WDOG <usr>:** This process terminated with exit code 1. (8619) (JUNMsg028)
Error in startup of asynchronous page writer process for database <dbname>
Message: <time> APW <usr>:** This process terminated with exit code 1. (8619) (JUNMsg029)
FACT(s) (Environment):
Progress 9.1x
OpenEdge 10.x
Windows
CAUSE:
With the database buffer pool, a certain amount of memory needs to be allocated. (See Progress Knowledge Base Solution 20183 to calculate the amount of memory.)
Sometimes this allocation will create a delay sufficient to produce a AdminServer timeout. Since the behavior will vary across machines, it can be a trial and error process to determine the timeout limit.
FIX:
Decrease the database buffer pool size to prevent a timeout or increase the AdminServer timeout value using the -AdminMsgTimeout parameter.