<div class="gmail_quote">2009/10/16 Jim Stichnoth <span dir="ltr"><<a href="mailto:stichnot@gmail.com">stichnot@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Fri, Oct 16, 2009 at 12:41 PM, Gary Dawes <<a href="mailto:gary.dawes@gmail.com">gary.dawes@gmail.com</a>> wrote:<br>
> Hmm, been spending far too much time on this today.<br>
><br>
> I have created a fresh install of Knopppmyth R5.5 with Mythtv 0.21 installed<br>
> on a VM. Checked the mysql config which was OK. Created a clean database,<br>
> and ran mythtv-setup to populate the tables, and restored the existing data<br>
> OK.<br>
><br>
> I then backed up the data, and restored ok into the box with 0.22 installed<br>
> after dropping the existing database. The restore worked, but failed on<br>
> schema upgrade using mythtv-setup, with the "DB charset conversion failed"<br>
> error.<br>
><br>
> I then tried all the above again, running the sed command to change the<br>
> encoding. Again, the restore worked, but the schema upgrade again failed<br>
> with the same error.<br>
><br>
> I then dropped the database again on the 0.21 box, and recreated. ran<br>
> mythtv-setup to create a empty schema, and then performed a partial-restore<br>
> into it. Checked for errors, and then backed that DB up. Once again a<br>
> restore onto the 0.22 box with a fresh empty database was sucessful, but<br>
> once again the schema upgrade in mythtv-setup failed with the same error.<br>
><br>
> Any ideas? I really really do not want to start a database from scratch as<br>
> there is 6 years worth of data in there.<br>
<br>
</div>When I first started testing 0.22, I had troubles getting the schema<br>
upgrade to work. It was also failing in the DB charset conversion<br>
step. It turned out I was running out of disk space on the test<br>
system. The charset conversion step creates a temporary table based<br>
on the People table, and that temporary table temporarily takes up<br>
mysql disk space. If you have 6 years worth of data, the People table<br>
should be quite large. You might check if that's the case. Do your<br>
log files give any indication?<br>
<br>
I figured this out by running with "-v all" and then pasting the sql<br>
commands from the log into mysql one by one until I saw which one was<br>
causing the error.<br>
<font color="#888888"><br>
Jim<br>
</font><div><div></div><div class="h5"><br></div></div></blockquote><div>Thanks. Oddly enough. I have just been running mythtv-setup -v all, and found that it was the people table which seemed to be causing the problems. I've removed the data lines for that table from the .sql backup file, and everything has now upgraded OK. Which is a massive relief! My database was around 200MB, but I have a 25GB / partition, with normally about 21GB free.<br>
<br>mythfrontend is now crashing with a en_gb error, but I haven't started tracking that down yet.<br><br>Gary<br></div></div><br>