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

Chris Tepe cstepe at ctdataservices.com
Thu Nov 5 22:26:31 UTC 2009


Chris Tepe wrote:
> Michael T. Dean wrote:
>> 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
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> No help.  Tried setting it to 16M and 32M.  I did have an issue with 
> the qt libraries when I first upgraded.  Yum installed qt4 instead of 
> qt44.  I had to remove qt4 which unistalled myth then reinstalled with 
> the qt44 libraries.  This got me to this point.
>
> 2009-11-05 14:52:47.951 Upgrading.
> 2009-11-05 14:52:47.953 Newest MythTV Schema Version : 1244
> QSqlQuery::exec: database not open
> 2009-11-05 14:52:52.604 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 14:52:52.605 Database Schema upgrade FAILED, unlocking.
> 2009-11-05 14:52:52.618 Couldn't upgrade database to new schema
>
> [root at mythcentos mythtv]# cat /etc/my.cnf
> [mysqld]
> datadir=/var/lib/mysql
> socket=/var/lib/mysql/mysql.sock
> user=mysql
> key_buffer = 16M
> table_cache = 128
> sort_buffer_size = 2M
> myisam_sort_buffer_size = 8M
> query_cache_size = 16M
> # Default to using old password format for compatibility with mysql 3.x
> # clients (those using the mysqlclient10 compatibility package).
> old_passwords=1
> max_allowed_packet = 32M
>
> [mysqld_safe]
> log-error=/var/log/mysqld.log
> pid-file=/var/run/mysqld/mysqld.pid
> [root at mythcentos mythtv]#
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
If I drop the old database and start with a blank database everything 
appears to be working.  The issue occurs when upgrading the old 
database.  If I can't upgrade the old database how do import my previous 
settings? Or can the upgrade be done off line?


More information about the mythtv-users mailing list