Mike,<br><br>Following your advice, I built a virtual test box with mythtv-0.23.1 on it. I was able to successfully import my 0.20 DB, and upgrade from DBSchemaVer 1161 to 1254 without any errors (other than a few MythFont errors). Unfortunately, I ran into problems when I tried to upgrade the DB to 0.25.2. While mythtv-setup was upgrading the DB, it encountered the following problem and errored out:<br>
<br>2013-03-14 11:12:53.534448 E Unrecognized video database schema version. Unable to upgrade database.<br>2013-03-14 11:12:53.534459 E mythvideo.DBSchemaVer: '', VideoDBSchemaVer: '1010', DVDDBSchemaVer: '1002'<br>
2013-03-14 11:12:53.534464 E Database Schema upgrade FAILED, unlocking.<br><br>The mythtv schema version is currently at 1266<br><br>Since I never used mythvideo, would it be possible to just delete the conflicting tables, and have mythtv-setup recreate them while updating the DB? What do I need to do to resolve the problem?<br>
<br>-Rob<br><br><br><div class="gmail_quote">On Mon, Mar 11, 2013 at 3:25 PM, Michael T. Dean <span dir="ltr"><<a href="mailto:mtdean@thirdcontact.com" target="_blank">mtdean@thirdcontact.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On 03/11/2013 03:11 PM, Michael T. Dean wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
So, just do a full backup, then a full restore to a different MySQL server (if required), then run mythtv-setup from an upgraded version of MythTV (first, 0.23, then do another database backup, then run mythtv-setup from 0.25.2--or, better, the currently supported version, 0.26-fixes).<br>
</blockquote>
<br></div>
Oh, and I should have mentioned that this approach--using the <a href="http://mythconverg_backup.pl" target="_blank">mythconverg_backup.pl</a> SQL-based backup--is also the right approach to use when upgrading MySQL versions (so it's the approach you should use to go from MySQL 3.23 to MySQL 5.x). Doing a "binary copy" of the MySQL data files when upgrading MySQL versions is not recommended unless you happen to be a MySQL admin--and, even then, if you're talking about the MythTV database, doing so is only recommended if you prefer doing things the hard way for no benefit (i.e. the MythTV database is small enough that a backup/restore is quicker than doing a proper binary-data-file upgrade, and has the benefit of creating a version-independent backup of the schema you can use in case you break something along the way).<div class="HOEnZb">
<div class="h5"><br>
<br>
Mike<br>
______________________________<u></u>_________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/<u></u>listinfo/mythtv-users</a><br>
</div></div></blockquote></div><br>