This shows you the differences between two versions of the page.
Previous revision | |||
manual:advanced:map_tools:corrupted_sqlite [2016/05/03 12:29] – 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 to open the database file or the file deletes itself - **this concerns both map files and points/ | ||
- | ===== How to ===== | ||
- | |||
- | Following steps require working with the DOS command line (cmd). | ||
- | |||
- | * Copy corrupted map file (or other sqlite database) from your device to PC | ||
- | * Download sqlite-tools from [[http:// | ||
- | * Unpack it and place corrupted database file into the same directory as sqlite3.exe | ||
- | * Start " | ||
- | * Run | ||
- | |||
- | < | ||
- | </ | ||
- | * Run | ||
- | |||
- | < | ||
- | </ | ||
- | * 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/ | ||
- | |||
- | For example: | ||
- | {{ : | ||
- | |||
- | <WRAP important round> However, this is not always possible. The easiest and most reliable way is to restore the database file from the backup. </ | ||