Kbase P21510: _mprosrv waits 3 minutes before timing out and causing 8619
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/20/2007 |
|
Status: Verified
FACT(s) (Environment):
Windows NT 32 Intel/Windows 2000
Progress 9.1X
OpenEdge 10.0X
SYMPTOM(s):
Database doesn't start from the dbman script.
Database always starts at the second attempt
Cannot start database using AdminServer
Long physical redo time causing database won't start when using AdminServer
This process terminated with exit code 1 (8619).
-AdminMsgTimeout set to 900 doesn't make any difference
Database doesn't start from the command line running _mprosrv.
CAUSE:
Bug# 20050412-011
CAUSE:
The Windows _mprosrv (c code) code will wait 3 minutes (180 seconds) for the start-up to occur before reporting the process terminated with exit code 1. Because of the timer, the child process is actually running when the error is reported to std out, which accounts for the timing in the .lg file. That being the case, when the physical re-do actually completes, the child process begins the next phase in the start-up and writes to the database's .lg file. However the parent process has already been terminated (and reported an error) so the adminserver will reject any registration.
FIX:
Upgrade to 9.1E02 later.
Upgrade to 10.0B03 or later.
An immediate workaround - truncate the BI file before re-starting the database or start the database in single user mode first.