manual:advanced:map_tools:corrupted_sqlite
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| manual:advanced:map_tools:corrupted_sqlite [2015/05/15 06:58] – mstupka | manual:advanced:map_tools:corrupted_sqlite [2016/05/03 12:29] – mstupka | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| ---- | ---- | ||
| - | <WRAP todo round center 60%>This page is obsolete and will be reworked soon</ | ||
| - | Sqlite databases on Android devices are by definition very stable. However we have own experience that databases can be corrupted. This may be due to wrong closing database or kill Locus app. The result is that Locus is not able open the map file or map deletes itself. Luckily sometimes it is possible to repair corrupted database. | ||
| + | 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 to open the database file or the file deletes itself - **this concerns both map files and points/ | ||
| ===== How to ===== | ===== How to ===== | ||
| - | Following steps require working with the command line. | + | Following steps require working with the DOS command line (cmd). |
| - | * Copy corrupted map file (sqlite database) from your device to PC | + | * Copy corrupted map file (or other sqlite database) from your device to PC |
| - | * Download sqlite-shell http:// | + | * Download sqlite-tools from [[http:// |
| - | * Unpack it and place corrupted database file into the same directory as sqlite3.exe | + | * Unpack it and place corrupted database file into the same directory as sqlite3.exe |
| - | * Start cmd and navigate to the directory with map file | + | * Start "cmd" |
| * Run | * Run | ||
| - | echo .dump | sqlite3.exe name_of_map.sqlitedb | + | < |
| + | </ | ||
| + | * Run | ||
| + | |||
| + | < | ||
| + | </code> | ||
| + | * If you repeat above integrity check on a new.db file, you should get " | ||
| + | * Try to import the fixed database (i.e. copy fixed tracks.db or waypoints.db to Locus/ | ||
| - | * and then | + | For example: |
| + | {{ : | ||
| - | sqlite3.exe -init name_of_map_dump.sql name_of_map_fixed.sqlitedb | + | <WRAP important round> However, this is not always possible. The easiest and most reliable way is to restore the database file from the backup. </ |
| - | * Try import fixed map | ||
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
