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/11/06 10:04] – [How to] mstupka | manual:advanced:map_tools:corrupted_sqlite [2017/07/25 12:35] – mstupka | ||
---|---|---|---|
Line 3: | Line 3: | ||
---- | ---- | ||
- | 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/ | + | 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 ===== | ||
+ | ==== Quick solution for MS Win users ==== | ||
+ | This procedure concerns corrupted //' | ||
+ | - Download **[[http:// | ||
+ | - Copy tracks.db to the unpacked directory | ||
+ | - Rename tracks.db to tracks_old.db | ||
+ | - Run **fix_tracks.bat** | ||
+ | - copy repaired tracks.db to its original place (i.e. to Locus/ | ||
+ | ==== General solution ==== | ||
- | Following steps require working with the command line. | + | Following steps require working with the DOS command line (cmd). |
* Copy corrupted map file (or other sqlite database) from your device to PC | * Copy corrupted map file (or other sqlite database) from your device to PC | ||
- | * Download sqlite-shell from 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 the corrupted file | + | * Start "cmd" |
* Run | * Run | ||
- | $ sqlite3 | + | < |
+ | </ | ||
+ | * Run | ||
+ | |||
+ | < | ||
+ | </ | ||
+ | * If you repeat above integrity check on a new.db file, you should get " | ||
+ | * Rename new.db file to the original name of your file and copy it to its original place (i.e. copy fixed tracks.db or waypoints.db to Locus/ | ||
+ | |||
+ | For example: | ||
+ | {{ : | ||
- | * Try to import | + | <WRAP important round> However, this procedure is not always successful. The easiest and most reliable way is to restore |
- | <WRAP important round> | ||
- | However, this is not always possible. The easiest and most reliable way is to restore the database file from the backup. | ||
- | </ |