[mythtv-users] Myth Database Upgrade failed preventing 0.22 from starting on gentoo.

[John Drescher]

> On 12/05/2009 01:07 PM, John Drescher wrote:
>>
>> I am having problems upgrading my database on gentoo for 0.22 because
>> it appears mythbackend is causing my database to go back from latin1
>> to utf8
>>
>
> That's what the upgrade to 0.22 will do.  (It's a good thing.)
>
>
>> jmd0 mythtv # mysql -umythtv -p mythconverg -e 'status;'
>> Enter password:
>> --------------
>> mysql  Ver 14.12 Distrib 5.0.84, for pc-linux-gnu (x86_64) using readline
>> 5.2
>>
>
> ...
>>
>> Server characterset:    latin1
>> Db     characterset:    latin1
>> Client characterset:    latin1
>> Conn.  characterset:    latin1
>
> Good.  Your DB server is properly configured, now.
>
>> jmd0 mythtv # ~john/scripts/mythconverg_restore.pl --filename
>> mythconverg-to_uncorrupt.sql
>>
>
> Did you try upgrading from the original backup?

No. Yesterday, I had

Server characterset:    utf8
Db     characterset:    latin1
Client characterset:    utf8
Conn.  characterset:    utf8

with 0.21-fixes. I followed the guide

http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding

to get my database to

Server characterset:    latin1
Db     characterset:    latin1
Client characterset:    latin1
Conn.  characterset:    latin1

under 0.21 fixes still. I used 0.21 in this condition for the evening
and then tried the 0.22 upgrade today.

When I did the 0.22 upgrade today I got the warning about having a
corrupt database and to consult the guide to fix that. I was about to
mail that it was already fixed yesterday. But when I checked it I had

Server characterset:    latin1
Db     characterset:    utf8
Client characterset:    latin1
Conn.  characterset:    latin1

instead of the expected

Server characterset:    latin1
Db     characterset:    latin1
Client characterset:    latin1
Conn.  characterset:    latin1

So I tried the guide again from the current database (not the pre
updated 0.21 db) and this output is what I posted in thread.

>
>> jmd0 mythtv # mythbackend
>>
>
> ...
>>
>> 2009-12-05 13:05:27.059 Newest MythTV Schema Version : 1244
>> 2009-12-05 13:05:27.345 Database corruption detected. Unable to
>> proceed with database upgrade. (Table: people, Warnings: 289)
>> 2009-12-05 13:05:27.345 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 on fixing your database.
>>
>
> Because the changed one is putting broken data in your database.
>
> If you've tried both the original pre-upgrade 0.21-fixes backup and the
> "uncorrupted" backup you show your using above, then you have partial
> corruption, and you'll need to do:
>  http://www.gossamer-threads.com/lists/mythtv/users/406111#406111 .
>

Thanks I will look into that.

John