Database always corrupts after import (1 Viewer)

Jwoodger

New Member
September 16, 2009
1
0
Home Country
When I import TV shows, I get the following from the MP-TVSeries.log (errors after completed):

00000003 - 16/09/2009 6:32:21 PM - ******************* Completed ********
00000001 - 16/09/2009 6:32:21 PM - Parsing Completed in 00:05:14.1100000
00000002 - 16/09/2009 6:33:26 PM - Cleaning up cached, generated Logos
00000002 - 16/09/2009 6:33:26 PM - Commit failed on this command: <select value from options where property = 'configSizeHeight'> (SQLiteClient: cmd:sqlite3_prepare16:pvm=null err:MISUSE detailed:eek:ut of memory query:select value from options where property = 'configSizeHeight').
00000002 - 16/09/2009 6:33:26 PM - Commit failed on this command: <insert into options (option_id, property, value) values(NULL, 'configSizeHeight', '1010')> (SQLiteClient: cmd:sqlite3_prepare16:pvm=null err:MISUSE detailed:eek:ut of memory query:insert into options (option_id, property, value) values(NULL, 'configSizeHeight', '1010')).
00000002 - 16/09/2009 6:33:26 PM - Commit failed on this command: <select value from options where property = 'configSizeWidth'> (SQLiteClient: cmd:sqlite3_prepare16:pvm=null err:MISUSE detailed:eek:ut of memory query:select value from options where property = 'configSizeWidth').
00000002 - 16/09/2009 6:33:26 PM - Commit failed on this command: <insert into options (option_id, property, value) values(NULL, 'configSizeWidth', '1296')> (SQLiteClient: cmd:sqlite3_prepare16:pvm=null err:MISUSE detailed:eek:ut of memory query:insert into options (option_id, property, value) values(NULL, 'configSizeWidth', '1296')).

In the MediaPortal.log I get the following:

2009-09-16 18:23:22.045398 [Info.][1]: using sqlite 3.6.6.1
2009-09-16 18:23:22.058398 [Info.][1]: SQLiteClient: TVSeriesDatabase4.db3 cmd:sqlite3_prepare16:pvm=null err:ERROR detailed:no such table: options query:select value from options where property = 'logLevel'
2009-09-16 18:23:22.095398 [Info.][1]: SQLiteClient: TVSeriesDatabase4.db3 cmd:sqlite3_prepare16:pvm=null err:ERROR detailed:no such table: options query:select value from options where property = 'logLevel'
2009-09-16 18:23:22.096398 [Info.][1]: SQLiteClient: TVSeriesDatabase4.db3 cmd:sqlite3_prepare16:pvm=null err:ERROR detailed:no such table: options query:insert into options (option_id, property, value) values(NULL, 'logLevel', '0')
2009-09-16 18:33:26.948398 [Info.][2]: SQLiteClient: Closing database: TVSeriesDatabase4.db3
2009-09-16 18:33:26.950398 [Info.][2]: SQLiteClient: cmd:sqlite3_prepare16:pvm=null err:MISUSE detailed:eek:ut of memory query:select value from options where property = 'configSizeHeight'
2009-09-16 18:33:26.951398 [Info.][2]: SQLiteClient: cmd:sqlite3_prepare16:pvm=null err:MISUSE detailed:eek:ut of memory query:insert into options (option_id, property, value) values(NULL, 'configSizeHeight', '1010')
2009-09-16 18:33:26.952398 [Info.][2]: SQLiteClient: cmd:sqlite3_prepare16:pvm=null err:MISUSE detailed:eek:ut of memory query:select value from options where property = 'configSizeWidth'
2009-09-16 18:33:26.953398 [Info.][2]: SQLiteClient: cmd:sqlite3_prepare16:pvm=null err:MISUSE detailed:eek:ut of memory query:insert into options (option_id, property, value) values(NULL, 'configSizeWidth', '1296')

Basically from a user perspective, I import my shows and it all seems fine. Then I exit the configuration tool, and thats when things turn pear-shaped - I start getting 'commit' errors. I note out of memory messages, but I have 2gb in my system and I don't believe it should be an issue...
 

Inker

Retired Team Member
  • Premium Supporter
  • December 6, 2004
    2,055
    318
    is your database on a server by any chance?

    if so, stop doing that as its not supported.
    if not, physically delete the db3 file and try again.
     

    millamber

    Portal Member
    July 1, 2007
    22
    0
    Home Country
    Parsing Rules

    I had this issue.

    I found that I had a lot shows that were not being parsed correctly and I thought it would just ignore these.

    However, I found when I made sure that there were no parsing errors, then it no longer corrupted the database after import.

    Millamber
     

    Users who are viewing this thread

    Top Bottom