Thanks lot Pavel,
>I only had two problem tables and luckily these seldom change, for
these I went back to the week old backup and cut them out of the dump
file and applied them to the newly created database. Now I
integrity_check more often
i will try out ".dump option", i done last time als
I recently had a similar problem, not wanting to fall back to a week
old dump of the database, what I did was to command line ".dump"ed the
defective database and attempt a reload.
I only had two problem tables and luckily these seldom change, for
these I went back to the week old backup and cut
> How can i recover this kind of DB, is it possible? and is there any way
> to avoid these
> unused pages, will enable auto_vacuum solve the problem ?
'VACUUM' is not designed to recover malformed database. Yes, there are
some kinds of problems that can be eliminated during vacuuming, but
not all
Hi All,
I found the DB corruption (malformed database), reporting some unused
pages,
please find the below trace,
*** in database main ***
Main freelist: 21 of 21 pages missing from overflow list starting at 0
Page 1604: sqlite3BtreeInitPage() returns error code 11
Page 1461 is never used
Page
4 matches
Mail list logo