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/09/03 13:11] – mstupka | manual:advanced:map_tools:corrupted_sqlite [2015/11/06 10:04] – [How to] mstupka | ||
---|---|---|---|
Line 3: | Line 3: | ||
---- | ---- | ||
- | SQLite databases on Android devices are very stable by definition. However, we have an experience | + | SQLite databases on Android devices are very stable by definition. However, we have experienced |
===== How to ===== | ===== How to ===== | ||
Line 9: | Line 9: | ||
Following steps require working with the command line. | Following steps require working with the command line. | ||
- | * 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 from http:// | * Download sqlite-shell 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 and navigate to the directory with the corrupted |
* Run | * Run | ||
- | | + | |
- | * and then | + | * Try to import the fixed database |
- | 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 | |
- | * Try to import | + | </ |