2012-05-01, 12:04 AM
I dont know.
Maybe try googling 'repair sqlite database file'
Maybe try googling 'repair sqlite database file'
2012-05-01, 12:04 AM
I dont know.
Maybe try googling 'repair sqlite database file'
2012-05-01, 08:51 AM
I was able to "kind of" recreate my npvr.db3 file using these directions...
http://structured-solutions.net/FixSqliteDatabase I used an older version of SQLite (http://www.sqlite.org/sqlite-3_6_16.zip) that was the current version when the directions were written as I had issues with the current SQLite version. I say "kind of" because everything appears to be fine, but the npvr.db3 file is smaller now. It's currently 41.7 MBs after an EPG update so it's almost half the size of the original. All channel names, recurring recordings, older recordings, decoders, etc. are listed as they were and appear to work fine so I am not sweating it at the moment. I still have a copy of the old npvr.db3 file that is corrupted.
2012-05-01, 11:04 AM
Try Firefox with the SQLite Manager add on. It is one of the best and easy to use SQLite managers and also has functions to check the integrity of the database.
2012-05-01, 05:41 PM
jcjefferies Wrote:Try Firefox with the SQLite Manager add on. It is one of the best and easy to use SQLite managers and also has functions to check the integrity of the database. +1 for that one.
2012-05-01, 10:45 PM
This is what I get with that add on. I am not sure how to fix it though...
Code: *** in database main ***
I gave this a try as well in Admin Command Prompt with SQLite3...
Code: C:\Users\Public\NPVR>sqlite3.exe OLD_npvr.db3 I guess there is no command to simply repair it HOWEVER, this still appears to be working fine... http://forums.nextpvr.com/showthread.php...post435749 Code: C:\Users\Public\NPVR>sqlite3.exe npvr.db3
2012-05-03, 11:59 AM
I think what I would do is to export the whole database to a text file, rename the database to save it, startup and exit NPVR to create a new, blank database and then import the saved text backup. This is assuming your data is valid and just some of the internals are a bit iffy.
|
|