View Single Post
Old 04-21-2021, 01:03 AM   #3
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
As @PeterT said, this means the database on the device is corrupted. The database backup does a full check on the database after taking the copy to make sure nothing is wrong. Usually, if the backup reports problems, there will be issues seen elsewhere. Such as calibre reporting problems when getting the book list. But, those actions will only have errors if the parts of the database they use have problems.

You should also see the above errors if you use the database check function in the Kobo Utilities plugin. That is checking the database in the same way as the backup does. Or you can use any SQLite database manage to check as well.

For this error, it is not causing any errors at this point. But, it usually will lead to worse things later. And it can be fixable. You can try compressing the database, or a VACUUM in SQLite terms. The Kobo Utilities plugin can do this. It basically dumps the database and then reloads it. That reorganises everything and removes any unused space such as this. That should fix things. The alternative is to restore your last good backup.
davidfor is offline   Reply With Quote