Reply to thread

Message

<blockquote data-quote="scythe000" data-source="post: 984727" data-attributes="member: 78738">Hi guys. I've got a MovingPictures DB with about 500 movies in it. Many filenames don't match right in the importer, so I've spent lots of time curating this. Recently, it looks like I have a little bit of corruption. I see from some of the logs about 30 entries of &quot;closing SQLite database.&quot; Opening the DB with SQLite3.exe and running a &quot;pragma integrity_check;&quot; gives the following output:&nbsp;[CODE]SQLite version 3.7.16.2 2013-04-12 11:52:43Enter &quot;.help&quot; for instructionsEnter SQL statements terminated with a &quot;;&quot;sqlite&gt; *** in database main ***On tree page 3661 cell 1: 1 of 3 pages missing from overflow list starting at 3505Page 3664 is never usedsqlite&gt; [/CODE]&nbsp;Looks pretty minor. How can I repair the damage rather than start over?&nbsp;I've tried this:1. Copy movingpictures.db3 somewhere.2. echo .dump | sqlite3.exe movingpictures.db3 &gt; movingpictures.db3.repair3. rename movingpictures.db3 movingpictures.db3.bak4. sqlite3.exe -init movingpictures.db3.repair movingpictures.db3&nbsp;However, the resulting .db3 is 0 bytes for some reason, even though the .repair file is not.&nbsp;Any ideas?</blockquote>

[QUOTE="scythe000, post: 984727, member: 78738"] Hi guys. I've got a MovingPictures DB with about 500 movies in it. Many filenames don't match right in the importer, so I've spent lots of time curating this. Recently, it looks like I have a little bit of corruption. I see from some of the logs about 30 entries of "closing SQLite database." Opening the DB with SQLite3.exe and running a "pragma integrity_check;" gives the following output: [CODE]SQLite version 3.7.16.2 2013-04-12 11:52:43 Enter ".help" for instructions Enter SQL statements terminated with a ";" sqlite> *** in database main *** On tree page 3661 cell 1: 1 of 3 pages missing from overflow list starting at 3505 Page 3664 is never used sqlite> [/CODE] Looks pretty minor. How can I repair the damage rather than start over? I've tried this: 1. Copy movingpictures.db3 somewhere. 2. echo .dump | sqlite3.exe movingpictures.db3 > movingpictures.db3.repair 3. rename movingpictures.db3 movingpictures.db3.bak 4. sqlite3.exe -init movingpictures.db3.repair movingpictures.db3 However, the resulting .db3 is 0 bytes for some reason, even though the .repair file is not. Any ideas? [/QUOTE]

Verification