Sorry, I meant .dump Given what you're describing I think it's worth finding out if you've found some bug in 3.7.2. The docs say 3.7.2 fixed a long-standing corruption bug. I don't know if that's related to this or not but sounds suspiciously close. So... #1 .dump the database #2 .import in into 3.7.2 #3 Run for a few days and see if you still get your backup problem. If still corrupt try 3.7.3 If it works then it sounds like the database was corrupt already and 3.7.2 just hits it. Michael D. Black Senior Scientist Advanced Analytics Directorate Northrop Grumman Information Systems
________________________________ From: sqlite-users-boun...@sqlite.org on behalf of Pirmin Walthert Sent: Tue 11/16/2010 7:09 AM To: sqlite-users@sqlite.org Subject: Re: [sqlite] EXTERNAL:Re: Strange Corruption Well indeed it wasn't 3.7.X that created the database originally. But it was always 3.7.2 that made the INSERTS/UPDATES that lead to the state in which the database couldn't be backed up anymore. So what do you mean in fact: 3.7.X maybe can't handle database structures created with older versions?! Even after doing a vacuum which fixed the bug I had the same errors again on the machines with 3.7.2 after a few days (after other INSERTS/UPDATES). About the thing I should test: There is no command called ".export" it seems?! But I think that I don't even have to test the thing you propose, as it will work almost for sure => like already stated several times one little tiny tiny tiny change already fixes the error. As an .export/.import will change some bits for sure this will already change the situation! Am 16.11.2010 13:53, schrieb Black, Michael (IS): > I thought of another test you should try. > > Do an .export of your original database using 3.6.23.1 and .import it > (constructing a new database). Then try your backup. > > If that works then you're just seeing corruption in the original database > that 3.6.23.1 handles (since it created it). > > If it doesn't work import into 3.7.3 and test backup again. > > If it doesn't work then try cutting the SQL in half until it does work. > Maybe you'll finally get a small enough size you can post. > > > > Michael D. Black > Senior Scientist > Advanced Analytics Directorate > Northrop Grumman Information Systems > > > ________________________________ > > From: sqlite-users-boun...@sqlite.org on behalf of Pirmin Walthert > Sent: Tue 11/16/2010 6:27 AM > To: sqlite-users@sqlite.org > Subject: EXTERNAL:Re: [sqlite] Strange Corruption > > > > No, this is definitely not the reason in my case as I can reproduce this > issue on every 3.7.2/3.7.3 machine I've tested after copying the > database file (and only the database file) to these machines. > > > > > > _______________________________________________ > 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
_______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
