Database Diagnostics Says Okay, But IMatch Says No!

[Darius1968]

I'm attaching a screen capture of IMatch after running database diagnostics, which has two conflicting verdicts!  I tried to attach the log file, but couldn't as it is over 2MB.  Any other way I can get that log file to you to analyze it? 

[attachment deleted by admin]

[Mario]

When do you get the "Severe Database..." message? After running the diagnosis or before?
I would need the database for further analysis. This is a unique case so far.
You can upload it to my FTP server. If you don't have the link yet, please contact me via Contact below.

What did you do before the Panic message came up? Usually physical damage of this extent to a database file is caused by severe crashes (rarely), physical damage to disk storage, network problems while writing to the database file, power failures and suchlike.

[Darius1968]

The "Severe Database..." message comes after the diagnosis has completed.  I would gladly upload you a copy of my database in question, but the catch-22 is that too much information it represents is private or classified, and I realize this doesn't help you out any.  What I can say it that it represents some 65,000 files, and this diagnosis is taking upwards of 20 min. or so.  There havve been power outages while the computer has been running recently because of thunderstorms and the like, but this doesn't happen when IMatch has been running, but could it still affect the database performance, nonetheless. 

I ran a chkdisk on my HD, and theere were only 2 files on a 500 GB HD that had to have bad clusters replaced, otherwise all was fine.

[Mario]

I ran a chkdisk on my HD, and theere were only 2 files on a 500 GB HD that had to have bad clusters replaced, otherwise all was fine.

That's no good. Power failures can cause harm to IMatch databases or other files. A typical scenario to corrupt an IMatch database is when IMatch has completed a transaction by writing data to the hard disk. While the data is still in the file system cache or the disk cache, a power failure occurs - and the data never reaches the disk. For IMatch, the data was written. But the data on the disk (after rebooting) does not match what the database system in IMatch expects -> database is damaged. The only way to recover from this is to restore the last backup.

Can you send me the IMatch Application log file in debug mode (Help > Support > Debug Logging) from a session where IMatch displays this message?

This would tell me maybe which part of the database has been damaged. IMatch logs all hard database failures internally and informs the user as soon as it happens. The diagnosis also runs an optimize which copies the entire database. This process should recognize all physical database damage and inform the user. This does happen, but not in the way I designed it. Your log file may be helpful to analyze this. Too bad I cannot get the damaged database...

[Darius1968]

I've decided to just ditch that database, and recreate a new one.  IMatch never informed me of any failures, however, for whatever reason, when I created the first database, I think IMatch may have for whatever reason froze and not completed the whole process, and I think the whole process did complete on the second database.  I'll just take it from here, but if I run into more issues like my post on this thread, I have your suggestions.