View Single Post
Old 09-01-2023, 08:43 AM   #144
enuddleyarbl
Guru
enuddleyarbl ought to be getting tired of karma fortunes by now.enuddleyarbl ought to be getting tired of karma fortunes by now.enuddleyarbl ought to be getting tired of karma fortunes by now.enuddleyarbl ought to be getting tired of karma fortunes by now.enuddleyarbl ought to be getting tired of karma fortunes by now.enuddleyarbl ought to be getting tired of karma fortunes by now.enuddleyarbl ought to be getting tired of karma fortunes by now.enuddleyarbl ought to be getting tired of karma fortunes by now.enuddleyarbl ought to be getting tired of karma fortunes by now.enuddleyarbl ought to be getting tired of karma fortunes by now.enuddleyarbl ought to be getting tired of karma fortunes by now.
 
enuddleyarbl's Avatar
 
Posts: 786
Karma: 1538394
Join Date: Sep 2013
Device: Kobo Sage
Quote:
Originally Posted by enuddleyarbl View Post
It looks like I repaired the database issue with SQLite Expert Personal. The help pages say there's supposed to be a Repair option under Database. But, I didn't see one. I used the Vacuum option and it appears to have fixed it.

With this firmware, I'm pretty sure this is the 2nd such time I've had database issues. The first time, I just deleted my books and re-sideloaded them from Calibre. Repairing the database with that SQLite utility is much easier than re-sideloading.
Well, I didn't pay attention and connected my Kobo Sage to Calibre without first rebooting the Forma. I was on the Home page, though. Immediate dirty bit/database error. Unfortunately, when I try using SQLite Expert Personal to fix things, it no longer works. There's still no Repair option under Database (which the Help file says should be there). And, the Vacuum option just pops up the error:

"database disk image is malformed SQL Statement: VACUUM."

The Check database function gives:

"database disk image is malformed SQL Statement: pragma integrity_check."

Any suggestions on how to get SQLite Expert Personal to repair the database?

It looks like the newest firmware (which may or may not be withdrawn) doesn't fix this (according to that thread). This has gotten very old, very fast.

Last edited by enuddleyarbl; 09-01-2023 at 05:38 PM.
enuddleyarbl is online now   Reply With Quote