On 29 Jul 2013, at 10:21am, techi eth <techi...@gmail.com> wrote: > Reference from below link gave me hint about integrity check failure case > recovery by Export/Import of database. > > Please let me know is this is correct & way to handle integrity failure > check.
This is not the correct way to handle integrity failure check. > http://blog.niklasottosson.com/?p=852 > > http://community.spiceworks.com/how_to/show/1468-how-to-fix-corrupt-sqlite-database This process, if it works, will present you with a /usable/ database: one which won't cause SQLite to crash. But the database A) may have incorrect data in it if some corruption affected only the contents of fields B) may have inconsistent data in it, e.g. an entry in your 'sales' table for a customer who is not in the 'customer' table C) may be missing all data added after the point of corruption, or worse still just /some/ of the data added after the point of corruption. It all depends on exactly which bytes of the file got corrupted. > In failure case integrity check return say “If any problems are found, then > strings are returned (as multiple rows with a single column per row)” > > With this how can I found in which table, row got issue? Could be many rows in many tables were corrupted. If SQLite knew exactly what had been corrupted it could just go and fix it without even needing your help. This is not the correct way to handle integrity failure check. The correct way to handle integrity failure check it to figure out what caused it (probably a hardware or low-level programming issue), try to make sure it doesn't happen again, then to restore the database file(s) from the last good backup you took. The method of rescue described on those pages /can/ be useful if you have a programmer who understands the data structure who has been told to spend hours desperately recovering all available data. It might be useful to reassemble new data files which could be printed out, then inspected for useful information. But I would not just recover datafiles that way and continue to use them in an operating system: you are running the risk of accumulating missing and incorrect data which will cause you problems later. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
