On 2 Mar 2012, at 1:20pm, Steffen Mangold <steffen.mang...@balticsd.de> wrote:
> i have a problem with the sqlite2.exe under windows. > Ok, I have here 20 corrupted DBs and want to repair they all. > I do this with CMD and the command ".dump | sqlite3 rebuild.db3 | sqlite3 > rebuild.temp" > > This works perfect for all DBs except one. > The DB where it is not working has a size of 15GB. > During processing I can see the "rebuild.temp" is going bigger and bigger. > But at the end the hole file is set empty!! It has a size of 0kb after > sqlite3.exe is finished?!?! First, get all the other databases done, so you're worried only about the one which doesn't work. Then do the .dump part for that database, putting the output into a file on disk, which should leave you with a huge file of SQL commands which should rebuild it. It's likely that the .dump stage will fail because your original database is corrupt. That's your problem. If it doesn't fail, split it up into parts, and rebuild your database using '.read' by reading the parts in one at a time. One of those parts should cause an error message or a crash. That's your problem. Either way, you should be able to narrow down the possible scope for the crash. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
