On 9/14/17, Esplin, Justin <jlesp...@verisk.com> wrote: > > We are seeing a couple worrisome (and not very informative) messages > repeatedly in our logs: > > SQLite error (11): database corruption at line 55472 of > [cf538e2783] > > SQLite error (11): database corruption at line 55514 of [cf538e2783] > > I have been looking around the web for a few days to try and figure out how > to diagnose this, but have come up empty-handed. This is occurring on > various Windows machines, though they appear to functional normally before, > during and after these errors are written to the logs. It was by chance that > we stumbled across these errors in the logs. > > Is there a way to know what the lines are that the error messages are > complaining about? Is there a chance that the corruption is of a nominal > variety or that it is able to automatically recover, which is why it appears > to continue to function normally?
Both errors are badly formatted b-tree pages in the database file. These both indicate serious database corruption. You should be able to verify the corruption by running "PRAGMA quick_check". Is the database file located on a network filesystem? -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
