[mythtv-users] Upgrading database from .18 to .19 then to .20

Michael T. Dean mtdean at thirdcontact.com
Wed Sep 13 12:26:08 EDT 2006

On 09/13/06 11:19, Stephen Atkins wrote:

>So I thought I would start with just backing up the the db as it is
>right now.  Problem is that it hits the table oldprogram and dies with
>an error of "can't open file".  All three (MYD, MYI and frm) are there.
> I guess my question now is what the heck do I do.

In 0.19 there's a script called optimize_mythdb.pl.  It will fix things 
up.  If you're not using 0.19, you can manually run mysqlcheck with the 
repair argument.

Note, also, that as of 0.19 (and still holds true with 0.20 or post-0.20 
SVN trunk), you should put the optimize_mythdb.pl script in a daily cron 
job to prevent database corruption.

Depending on how long the tables have been corrupt, you may have 
corrupt/missing data in the database.  If so, it will have varying 
effects on Myth (i.e. missing or some forms of corrupt information in 
oldprogram means Myth doesn't know that you've recorded some programs, 
so you may record repeats).  The optimize_mythdb.pl script in a daily 
cron job will minimize the time you operate with a corrupt data--thereby 
making sure you lose as little data as possible.


More information about the mythtv-users mailing list