openedge - Why do we get time-stamp issue in progress database? -

We've upgraded from version 9.1 to version 11.3. It was working fine for two days and later the database was down. It has been mentioned in the log file. FIE has been removed. We are getting the following error when we do

old qhn -c truncate BI

OpenAge release 11.3 According to Mercury July 17: 16: 45:17 ADT 2013

** Monday 13 12:15:15 2014 database was last used. (886) ** Prospect of the first image file Tuesday 14 October 12:48:47 2014. (887) ** These dates do not match, so one of them is the wrong copy of you. (888)

We have restored DB from backup. For future reference, we want to know the root cause analysis of the issue below.

You have one or more files that make DL (which includes two files) To manipulate the .lk file is removed and maybe used the OS tools.

This is common in "cowboy" stores, where administrators do some work like remove the .lk file or use "kill-9" on users.

The root cause is simple - the progress of manipulating another database is that it means that the error message is correct and you have not found this error for any other reason.

You can easily do it yourself "Touch" any of the DB extras or two files or copy them somewhere and copy them (usually affect the "MV" command timestamp Does not, so that's okay).