Subject pretty much says it all. The program will start up and will load my other databases but this particular one hangs about half way through the verification process. It opened fine yesterday.
Of all my databases, this one is really the most important. Any help would be appreciated.
Thanks for the quick response and the suggestion. However, as far as I can tell, the options described in the help file require that the database be opened, which is not possible here. In the absence of anything better, I’m left with the possibility of restoring from a Time Machine backup - something that I’d rather not do as I will lose at least a days worth of work.
Tom - did you reboot? How about permissions on that disk - have you checked them in DiskUtilty, Onyx, or otherwise?
This isn’t what you want to hear, but if you need to restore from TM and are left with the possibility of lost data, here’s a method to locate the “lost” files. This takes work and involves the (free) FileMerge utility available on the OS X Xcode download from Apple:
Make copies of the restored and the lost database. In Finder “show package contents” and drag the folder Files.noindex out of each database to a new folder (renaming one of them). Use FileMerge to compare the two folders and locate the “lost” documents. This doesn’t help you with groups, tags, etc., but it is a life saver if you’ve been creating valuable documents inside a DT database and the database refuses to open under any circumstances.
The copy of the output to the terminal is below. I went a head and began executing Korm’s solution so there’s no hurry with this.
I should mention that this is probably my fault, not DT’s. I keep the database on Dropbox and I’m guessing that it wasn’t fully synced when I loaded the program up. Nevertheless, I don’t think the program, itself, should hang under any circumstances so it might be worth it for someone to take a look.
So for the purpose of “debugging” here’s the output to a terminal when I start the program and then try to load a copy of the corrupted package:
Version 2.0.3 will handle this, meaning that it won’t freeze in this case but nonetheless the database seems to be slightly damaged (probably due to Dropbox). Therefore v2.0.3 should be able to rebuild this database, just let me know (via PM or email) if you’re interested in the current beta.