Submitted by WayneK on 2022/04/19 12:50

I tried to run a database repair on my new 160 mb file after getting a message about corruption.

An hourglass came up and remained unchanged for 45 minutes.  I finally killed the process to exit InfoQube.  Tried it twice more and it locked up again (though I waited only a few minutes this time).

Past repairs have taken only a few seconds so I presume these are lockups.  How should I proceed? 

Note: the file seems to be working ok.  The corruption messages I've gotten were caused by clicking on one of the items copied from another file.  When I ran database repair, the hourglass flickered on for a few seconds, so I presumed the repair was done (the corruption message went away).  There have been only a handful of these cases.  99.9% of the items copied over seem fine.

Related suggestions:

1) Provide a progress bar so you can see that the repair is actually in process and not locked up.  Right now, I'm not sure if the repairs are locking up or just taking a very long time to run. 

2) Have a "Repair completed successfully" at the end.

Wayne

Comments

Hi Wayne,

Good suggestion (progress bar). If you have an issue with repair, you can also initiate it with the file closed first, and then with it opened. When closed, it is a plain database engine repair being done. When opened, it also regenerates all fields and grids, perhaps there was a problem there

Pierre_Admin

p.s. I guess you meant 160MB (not GB) !

How do I ?