Kbase P20021: Unable to read the (probably truncated) .lk file message when starting database from script.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/23/2006 |
|
Status: Verified
FACT(s) (Environment):
UNIX
SYMPTOM(s):
Database fails to start when started from script with error:
Unable to read the (probably truncated) .lk file. (1383)
** This process terminated with exit code 2. (8619)
Another script runs proutil busy against the databases every x seconds
Database will start from command prompt
Two parallel processes: one looping doing proutil busy's every 5 seconds and
another doing _mprosrv.
CAUSE:
Timing issue. This problem occurs very infrequently and it could not be duplicated in house. Proutil Busy will first check if an lk file exists. If no lk file is present proutil busy creates a lk file, ensures it has write permission by writing some data to the file then removes the file. The create, write , and delete happen very quickly.
FIX:
Avoid running proutil busy while the database is being started.
Change the frequency in which proutil busy runs in the script.