Deleting a lockfile

[Richard Kreiss]

> -----Original Message-----
> From: Kenneth Brody [mailto:kenb at fptech.com]
> Sent: Tuesday, April 05, 2011 5:09 PM
> To: rkreiss at gccconsulting.net
> Cc: 'filePro Mailing List'
> Subject: Re: Deleting a lockfile
> 
> On 4/5/2011 4:26 PM, Richard Kreiss wrote:
> > Can deleting a manually deleting a lockfile, using windows file
> > manager, while the file is in use also delete demand indexes and
> processing tables?
> 
> (Assuming that the first "deleting a" was a typo.)
> 
> No.
> 
> It can, of course, cause other problems, such as allowing an index
definition
> to be changed, or the file restructured, while someone is using the file.
> 
> [...]
> > I went to the file manager and noted that everything in that folder
> > stating with A through I but not including index.n was missing. Also
> > the 10 demand indexes were gone.
> 
> Then they didn't delete just the lockfile, did they?
> 
> My shot-in-the-dark out-of-the-blue guess...
> 
> The shift-clicked on "lockfile", thereby selecting everything from the
> currently-selected item (which defaults to the first filename) through the
> lockfile.  And, given that there probably weren't any J, K, or L files
(aside from
> "lockfile"), that could be seen as "everything in that folder starting
with A
> through I".
> 

Ken,

I think you are correct. 

I was able to reinstall most of what was deleted except some new selection
sets that I don't normally copy to my test bed.  Looks like I will have to
start copying these also.

If they had caught this early enough and the person who deleted the files
had not logged off of his terminal server session, we might have been able
to recover these files.

Richard