Yes, this is a case of corruption. The problem occurred during a power cycle test. I have the synchronous mode set to NORMAL. By examining the header of the DB ,is it possible to find out if sqlite was in the middle of a transaction when the power off occurred ?
-Sreekumar On Mon, Jan 23, 2012 at 2:21 PM, Roger Binns <rog...@rogerbinns.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 23/01/12 00:13, Sreekumar TP wrote: > > What can I infer from these logs ? > > Your database is corrupted. Here is a list of possible causes: > > http://www.sqlite.org/howtocorrupt.html > > Roger > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iEYEARECAAYFAk8dH4kACgkQmOOfHg372QThhwCgyPS+Sl28MEMHln4I6iRcm5VL > 2ZkAn0tIpqfbGbkIZwUs3myTbwzv+jdw > =Czsj > -----END PGP SIGNATURE----- > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
