[mythtv-users] database upgrade fail: schema 1160 to 1244

Michael T. Dean mtdean at thirdcontact.com
Wed Dec 9 05:38:58 UTC 2009

On 12/09/2009 12:26 AM, Jeff Bryner wrote:
> Thanks for the quick response:
>> No, the problem is that you're using an old version of 0.22-fixes (or 
>> 0.22 release tarball).  You need to update to current 0.22-fixes (at 
>> least r22550).
> Looks like I've got a good version? The latest in gentoo/portage is:
> mythtv-0.22_p22860 which is what I have just installed.

I'd feel more comfortable with the below if I could see the output of: 
mythbackend --version

> Lemme know if I should grab something specific from the trunk or just 
> go for a non-portage install.
> The mysql status dump is the current mysql which was also updated in 
> the emerge -avu world. I wasn't smart enough to copy the old config, 
> so I'll have to assume I'm in the camp with the bad config.

Very likely true.

>> You should a) upgrade to current 0.22-fixes, and b) go back to the 
>> 0.20 backup and try 
>> http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding .
> OK, I've been studying it and will give it a go. 

If you do, in fact, have a sufficiently-new version of MythTV, then it's 
the invalid UTF-8 connection causing the issues, so when you fix the 
database (both the database server configuration and the database data) 
with http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding , it 
will work.


More information about the mythtv-users mailing list