[mythtv-users] 0.22 database schema upgrade fails driver not loaded

Michael T. Dean mtdean at thirdcontact.com
Thu Nov 5 19:35:50 UTC 2009


On 11/05/2009 02:12 PM, Chris Tepe wrote:
> I had myth 0.21 running on my CentOS 5.3 box.  Upgraded to 0.22.  When 
> I run mythtv-setup it attempts to update the schema but fails.
> 2009-11-05 13:36:06.170 mythbackend version: 
...
> 2009-11-05 13:36:06.955 New DB connection, total: 1
> 2009-11-05 13:36:07.289 Connected to database 'mythconverg' at host: 
> localhost
> 2009-11-05 13:36:07.557 Closing DB connection named 'DBManager0'
> 2009-11-05 13:36:07.930 Connected to database 'mythconverg' at host: 
> localhost
> 2009-11-05 13:36:08.501 Current MythTV Schema Version (DBSchemaVer): 1215

Shows DB exists and connection works (as we retrieved data from it).

> 2009-11-05 13:37:05.121 Newest MythTV Schema Version : 1244
> QSqlQuery::exec: database not open
> 2009-11-05 13:37:09.922 DB Error (Unable to perform test for database 
> corruption before character set conversion.):
> Query was:
>
> Driver error was [1/-1]:
> Driver not loaded
> Database error was:
> Driver not loaded
>
> 2009-11-05 13:37:09.923 Database Schema upgrade FAILED, unlocking.
> 2009-11-05 13:37:09.924 Couldn't upgrade database to new schema

Now database is gone/we can't talk to it.

Can you try: 
http://www.gossamer-threads.com/lists/mythtv/users/405988#405988 and 
report back, please?

Though I can't see how any of our data could be sufficiently sized to 
cause issues with the MySQL default of 1MiB, perhaps your distro 
configured mysqld to use a much smaller size (to "save RAM" or 
something).  If some distro is configuring a value on the order of 
1024bytes (the smallest allowed size), we could have issues after 
0.21-fixes (as our text is now potentially 3 times as large as it was 
for 0.21-fixes and below).

Thanks,
Mike


More information about the mythtv-users mailing list