User Tools

Site Tools


manual:advanced:map_tools:corrupted_sqlite

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
manual:advanced:map_tools:corrupted_sqlite [2015/09/02 15:13]
mstupka
manual:advanced:map_tools:corrupted_sqlite [2019/01/22 08:18] (current)
Line 1: Line 1:
-====== How to repair a corrupted SQLite database ======+====== Corrupted SQLite Database Repair ======
  
 ---- ----
  
-SQLite databases on Android devices are very stable by definition. However, we have an experience 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 map file or map deletes itself. Luckily sometimes it is possible to repair such a 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/track databases, all are SQLites**. Luckily sometimes it is possible to repair such a corrupted database.
 ===== How to ===== ===== How to =====
 +==== Quick solution for MS Win users ====
 +This procedure concerns corrupted //'tracks.db'// file that you can find in your Locus directory //Locus/data/database//:
 +  - Download **[[http://storage.asamm.com/locus/data/various/SQLite_tools.zip|this .ZIP file]]** and unpack it
 +  - Copy tracks.db to the unpacked directory
 +  - Run **fix_tracks.bat**
 +  - copy repaired tracks.db to its original place (i.e. to Locus/data/database folder) 
 +==== 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 
 +  * Download sqlite-tools from [[http://www.sqlite.org/download.html|http://www.sqlite.org/download.html]] 
 +  * 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
  
-  * Copy corrupted map file (sqlite database) from your device to PC +<code>>sqlite3.exe filename.db "PRAGMA integrity_check" 
-  * Download sqlite-shell from http://www.sqlite.org/download.html +</code>to verify databaseResult will be probably error message Error: database disk is malformed.
-  * Unpack it and place corrupted database file into the same directory as sqlite3.exe  +
-  * Start cmd and navigate to the directory with map file+
   * Run   * Run
  
-  echo .dump | sqlite3.exe name_of_map.sqlitedb name_of_map_dump.sql+<code>>sqlite3.exe filename.db ".dump| sqlite3 new.db 
 +</code> 
 +  * If you repeat above integrity check on a new.db file, you should get "OK" message. 
 +  * 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/data/database folder)
  
-  * and then+For example: 
 +{{ :manual:advanced:map_tools:sqlite_repair.png?nolink |}}
  
-  sqlite3.exe -init name_of_map_dump.sql name_of_map_fixed.sqlitedb+<WRAP important round> However, this procedure is not always successfulThe easiest and most reliable way is to restore the database file from the backup</WRAP>
  
-  * Try to import the fixed map 
manual/advanced/map_tools/corrupted_sqlite.1441199603.txt.gz · Last modified: 2015/09/02 15:13 (external edit)