[mythtv-users] major db problem upgrading from 0.21-fixes to 0.22

Michael T. Dean mtdean at thirdcontact.com
Sun Mar 7 06:26:06 UTC 2010


On 03/07/2010 01:16 AM, Michael T. Dean wrote:
> On 03/06/2010 06:41 PM, Nick Morrott wrote:
>> On 6 March 2010 23:23, Audio Phile wrote:
>>> new version: 1216
>>> 2010-03-06 18:09:12.841 DB charset conversions update failed! Your 
>>> database seems to be partially corrupted. Please move the backup to 
>>> a safe place. Your database must be fixed before you can upgrade 
>>> beyond 0.21-fixes. Please see 
>>> http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding for 
>>> information.
>>> 2010-03-06 18:09:12.866 Database Schema upgrade FAILED, unlocking.
>>> 2010-03-06 18:09:12.891 Couldn't upgrade database to new schema
>>> 2010-03-06 18:09:13.049 mythbackend version: 
>>> branches/release-0-22-fixes [23566M] www.mythtv.org
>>>
>>> I have no idea what these errors are nor how to resolve them.  Any 
>>> advise is greatly appreciated.
>> If you haven't already, I suggest you start by reading the relevant
>> wiki entry (the URL is purposefully provided in the error message
>> above).
> Normally, this would be the right advice, but in this case, the error 
> is due to a corrupt database /schema/, not corrupt data.

BTW, I just realized this sounds like I'm saying Nick's advice is bad.  
What I was trying to say is that the error message itself isn't the 
right advice--i.e. you don't have partially corrupt database character 
encoding, but you have a completely corrupt schema.

Nick's advice is correct--follow the instructions provided by the error 
message, even though your issue is different, the same "partial 
corruption" solution applies.

Mike


More information about the mythtv-users mailing list