sqlite - How to debug the cause for SQLiteError(11): database corruption -


i have been tasked finding cause 2 repeated lines find in 5% our logs in our beta environment (this app not in prod yet). follow:

sqlite error (11): database corruption @ line 55472 of [cf538e2783]

sqlite error (11): database corruption @ line 55514 of [cf538e2783]

that's it. no other info available, , it's 2 lines. being logged system.data.sqlitelog.logeventhandler , log system trace.

interestingly, appears database continues function , usage of our application continues without apparent problems.

so question is: is there issue, and, if so, how go identifying it?

in research on issue have believe there legitimate problem here. according www.sqlite.org corruption in sqlite should rather rare. false corruption report can caused due database shrinkage (8.1), don't think that's case here. must assume @ point report correct , database corrupt.

however, how database continue function hours of use if is, in fact, corrupted?

many sites give solutions on how fix issue (by reverting backup, or otherwise recreating database), need find what's causing issue.

i have tried installing db browser sqlite , browsing database, seems , there doesn't seem way "browse" lines reportedly corrupt. (there must way so, though, right? why give line numbers if it's impossible know line numbers are?)

are there operations or areas culprits in circumstance can investigate? how identify lines being referenced in error messages?


Comments

Popular posts from this blog

neo4j - finding mutual friends in a cypher statement starting with three or more persons -

php - How to remove letter in front of the word laravel -

minify - Minimizing css files -