manual:advanced:map_tools:corrupted_sqlite
Differences
This shows you the differences between two versions of the page.
| Previous revision | |||
| manual:advanced:map_tools:corrupted_sqlite [2015/11/06 09:57] – [How to] mstupka | — | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Corrupted SQLite Database Repair ====== | ||
| - | ---- | ||
| - | |||
| - | SQLite databases on Android devices are very stable by definition. However, we have experienced that databases can be corrupted. This may be due to wrong closing the database or killing Locus app. The result is that Locus Map is not able open the database file or the file deletes itself - **this concerns both map files and points/ | ||
| - | |||
| - | ===== How to ===== | ||
| - | |||
| - | Following steps require working with the command line. | ||
| - | |||
| - | * Copy corrupted map file (or other sqlite database) from your device to PC | ||
| - | * Download sqlite-shell from http:// | ||
| - | * Unpack it and place corrupted database file into the same directory as sqlite3.exe | ||
| - | * Start cmd and navigate to the directory with the corrupted file | ||
| - | * Run | ||
| - | |||
| - | echo .dump | sqlite3.exe name_of_map.sqlitedb > name_of_map_dump.sql | ||
| - | |||
| - | * and then | ||
| - | |||
| - | sqlite3.exe -init name_of_map_dump.sql name_of_map_fixed.sqlitedb | ||
| - | |||
| - | * Try to import the fixed database | ||
manual/advanced/map_tools/corrupted_sqlite.txt · Last modified: 2019/01/22 09:18 by mstupka
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
