Kbase P60150: Potential consequences of removing the .lk file while the database is running.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
30/04/2010 |
|
Status: Verified
GOAL:
Potential consequences of removing the .lk file while the database is running.
GOAL:
What can happen if the .lk file is removed while a database is running?
FACT(s) (Environment):
All Supported Operating Systems
Progress/OpenEdge Product Family
FIX:
If the database server is running and the .lk file is removed it would be possible for another process to try to connect to the database.
This other process would have no awareness that the database was served since it is the .lk file which indicates the database is in use by another process, and it is the .lk file which stores what PID is controlling the database on what machine.
The potential exists to irrevocably corrupt the database if 2 separate processes believed they were in full control of the database.
The only recourse would be to go to backup.
In some versions of Progress / OpenEdge, the database server engine periodically scans to see if the .lk file has been removed and if it observes the .lk file no longer exists in the expected location the database server engine will shut the database down to attempt to preserve database integrity.
Depending on how quickly the database server engine detects the missing .lk file there is still a possibility that another process will attempt to touch the database and could corrupt the database.