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 revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
manual:advanced:map_tools:corrupted_sqlite [2017/07/25 12:35] mstupkamanual:advanced:map_tools:corrupted_sqlite [2019/01/22 10:18] – external edit 127.0.0.1
Line 7: Line 7:
 ==== Quick solution for MS Win users ==== ==== Quick solution for MS Win users ====
 This procedure concerns corrupted //'tracks.db'// file that you can find in your Locus directory //Locus/data/database//: This procedure concerns corrupted //'tracks.db'// file that you can find in your Locus directory //Locus/data/database//:
-  - Download **[[http://nas.asamm.com:8080/share.cgi?ssid=04tjsoL|this .ZIP file]]** and unpack it+  - Download **[[http://storage.asamm.com/locus/data/various/SQLite_tools.zip|this .ZIP file]]** and unpack it
   - Copy tracks.db to the unpacked directory   - Copy tracks.db to the unpacked directory
-  - Rename tracks.db to tracks_old.db 
   - Run **fix_tracks.bat**   - Run **fix_tracks.bat**
   - copy repaired tracks.db to its original place (i.e. to Locus/data/database folder)    - copy repaired tracks.db to its original place (i.e. to Locus/data/database folder) 
Line 26: Line 25:
   * Run   * Run
  
-<code>>sqlite3 filename.db ".dump" | sqlite3 new.db+<code>>sqlite3.exe filename.db ".dump" | sqlite3 new.db
 </code> </code>
   * If you repeat above integrity check on a new.db file, you should get "OK" message.   * If you repeat above integrity check on a new.db file, you should get "OK" message.
manual/advanced/map_tools/corrupted_sqlite.txt · Last modified: 2022/08/23 08:29 by menion