Kbase P155109: Database shutdown abnormally when running in a multi-user mode.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/20/2009 |
|
Status: Unverified
SYMPTOM(s):
Database shutdown abnormally when running in a multi-user mode.
Begin ABNORMAL shutdown code (2249)
Database log file is also showing error 4195
<file-name> is missing, shutting down... (4195)
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Product Family
CAUSE:
The error message (<dbname>.lk is missing, shutting down... (4195)) occurs when an Operating System stat function is executed to check the existence of a dbname.lk file. If the stat function returns with a -1 return code and an errno (Operating System Error number) for ENOENT (No such file or directory), the database will perform an abnormal shutdown. This is expected behavior.
The trigger for the abnormal shutdown is the result of the errno ENOENT being returned for the stat function. Even if the database.lk file did exist, if the stat function fails per the criteria above, the abnormal shutdown will still occur. During the shutdown process, the broker will then remove the .lk file that could not be statted.
FIX:
Investigate and address the reason as to why the dbname.lk file could not be validated with the stat function.
1. Was the file inadvertently deleted by a user or process?
2. Was the file possibly locked by another 3rd party application that would lock it in an exclusive mode such that a stat function could not be performed against it. (Something like a sharing violation).