This object is in archive!
Offline map tile database corrupted
Solved
Hi,
since some days my most important offline map tile database becomes corrupted, when I try to calculate the number of updatable map tiles of a particular zoom level. The sqlitedb file then has a very small size (some kB, normally its size is ~4 GB). Fortunately beside it there is a backup version of the original one. So I simply can close Locus Map, delete the corrupted one, rename the backup file to the original name and start Locus Map again. So I thought, there must be a hidden error in the database, copied the sqlitedb file to my PC and localisied it with SQLite Administrator. The image of one single entry in the tiles table is corrupted. Sadly, SQLite Administrator is not very verbose, when reporting the error:
20.08.2022 13:50:30: SQL Error: SQL logic error or missing database < select image from tiles<br>where z = 2 and x = 17176 and y = 10814;>The other values x, y, z and s of this entry can be selected properly. And the image of any other entry can be selected too (is reported as "‰PNG" by SQLite Administrator). So my question is, can I fix or delete this corrupted entry in any way? Trying to delete it using the same where clause ends up with the same error:
20.08.2022 13:51:21: SQL Error: SQL logic error or missing database < delete from tiles where z = 2 and x = 17176 and y = 10814;>What can I do to repair my map tile database?
BR
tkansgar
The same problem 
Full success! Instead of
like you wrote in your document linked above, which didn't help in my case, I symply didThen I renamed new.db to the original name, copied it back into the maps folder on my smartphone, started Locus Map again, and voila, calculating the number of updatable map tiles and downloading them works again properly.
One additional note: After I had copied the last version of my database from my smartphone to my PC and directly executed my modified command, the lost_and_found table didn't exist. It obviously only existed, after I had modified the original database with SQLite Administrator and then did the recover command to this modified database. But maybe there is no warranty, that lost_and_found won't be added to the new.db. So you should keep in mind, that it could exist, and tink of, what to do with it.
Perhaps you could recommend to try it with ".recover" in your document, if ".dump" does not help.
BR
tkansgar
Full success! Instead of
like you wrote in your document linked above, which didn't help in my case, I symply didThen I renamed new.db to the original name, copied it back into the maps folder on my smartphone, started Locus Map again, and voila, calculating the number of updatable map tiles and downloading them works again properly.
One additional note: After I had copied the last version of my database from my smartphone to my PC and directly executed my modified command, the lost_and_found table didn't exist. It obviously only existed, after I had modified the original database with SQLite Administrator and then did the recover command to this modified database. But maybe there is no warranty, that lost_and_found won't be added to the new.db. So you should keep in mind, that it could exist, and tink of, what to do with it.
Perhaps you could recommend to try it with ".recover" in your document, if ".dump" does not help.
BR
tkansgar
Hello tkansgar,
sorry to read this, but it simply rarely happens. Because of similar problems, I wrote this document a long time ago, so you may give it a try. Seems you are quite skilled, so it should be no problem for you to try it. Hope this helps.
Menion
Hello tkansgar,
sorry to read this, but it simply rarely happens. Because of similar problems, I wrote this document a long time ago, so you may give it a try. Seems you are quite skilled, so it should be no problem for you to try it. Hope this helps.
Menion
Full success! Instead of
like you wrote in your document linked above, which didn't help in my case, I symply didThen I renamed new.db to the original name, copied it back into the maps folder on my smartphone, started Locus Map again, and voila, calculating the number of updatable map tiles and downloading them works again properly.
One additional note: After I had copied the last version of my database from my smartphone to my PC and directly executed my modified command, the lost_and_found table didn't exist. It obviously only existed, after I had modified the original database with SQLite Administrator and then did the recover command to this modified database. But maybe there is no warranty, that lost_and_found won't be added to the new.db. So you should keep in mind, that it could exist, and tink of, what to do with it.
Perhaps you could recommend to try it with ".recover" in your document, if ".dump" does not help.
BR
tkansgar
Full success! Instead of
like you wrote in your document linked above, which didn't help in my case, I symply didThen I renamed new.db to the original name, copied it back into the maps folder on my smartphone, started Locus Map again, and voila, calculating the number of updatable map tiles and downloading them works again properly.
One additional note: After I had copied the last version of my database from my smartphone to my PC and directly executed my modified command, the lost_and_found table didn't exist. It obviously only existed, after I had modified the original database with SQLite Administrator and then did the recover command to this modified database. But maybe there is no warranty, that lost_and_found won't be added to the new.db. So you should keep in mind, that it could exist, and tink of, what to do with it.
Perhaps you could recommend to try it with ".recover" in your document, if ".dump" does not help.
BR
tkansgar
Hmm perfect, thanks for info!
Manual updated.
Jiří M. aka Menion
Hmm perfect, thanks for info!
Manual updated.
Jiří M. aka Menion
Replies have been locked on this page!