View Single Post
Old 10-01-2021, 08:36 PM   #2296
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
What @theducks said is largely true. But, if you have a recent good database backup, then you can restore that. Simply copy the database backup in place of the existing corrupt database. When you disconnect the device, shut it down completely. That will prevent the device from trying to use it. It will be read when you start up. After the device has started, connect to the PC and check the database again. The disconnect and it will cleanup the database removing or adding any changes you have made since. You will lose any reading status and annotations that changed since the backup. If you are using the plugin to store the reading status, then you can connect again and restore that for the books you have read since the backup was taken.

You can try to compress the database. Most of the errors are in the indexes. A compress can fix these. But, the first few errors are elsewhere. These might prevent the compress from happening at all.
davidfor is offline