[mythtv-users] error when fixing database forced by mythtv upgrade

[Jim Stichnoth]

On Fri, Oct 16, 2009 at 12:41 PM, Gary Dawes <gary.dawes at gmail.com> wrote:
> Hmm, been spending far too much time on this today.
>
> I have created a fresh install of Knopppmyth R5.5 with Mythtv 0.21 installed
> on a VM. Checked the mysql config which was OK. Created a clean database,
> and ran mythtv-setup to populate the tables, and restored the existing data
> OK.
>
> I then backed up the data, and restored ok into the box with 0.22 installed
> after dropping the existing database. The restore worked, but failed on
> schema upgrade using mythtv-setup, with the "DB charset conversion failed"
> error.
>
> I then tried all the above again, running the sed command to change the
> encoding. Again, the restore worked, but the schema upgrade again failed
> with the same error.
>
> I then dropped the database again on the 0.21 box, and recreated. ran
> mythtv-setup to create a empty schema, and then performed a partial-restore
> into it. Checked for errors, and then backed that DB up. Once again a
> restore onto the 0.22 box with a fresh empty database was sucessful, but
> once again the schema upgrade in mythtv-setup failed with the same error.
>
> Any ideas? I really really do not want to start a database from scratch as
> there is 6 years worth of data in there.

When I first started testing 0.22, I had troubles getting the schema
upgrade to work.  It was also failing in the DB charset conversion
step.  It turned out I was running out of disk space on the test
system.  The charset conversion step creates a temporary table based
on the People table, and that temporary table temporarily takes up
mysql disk space.  If you have 6 years worth of data, the People table
should be quite large.  You might check if that's the case.  Do your
log files give any indication?

I figured this out by running with "-v all" and then pasting the sql
commands from the log into mysql one by one until I saw which one was
causing the error.

Jim