[mythtv-commits] Ticket #6923: 0.21->trunk DB upgrade failed

MythTV mythtv at cvs.mythtv.org
Mon Nov 2 21:20:19 UTC 2009


#6923: 0.21->trunk DB upgrade failed
-----------------------------------+----------------------------------------
 Reporter:  warpme@…               |        Owner:  ijr    
     Type:  defect                 |       Status:  closed 
 Priority:  minor                  |    Milestone:  unknown
Component:  MythTV - Mythtv-setup  |      Version:  head   
 Severity:  medium                 |   Resolution:  invalid
  Mlocked:  0                      |  
-----------------------------------+----------------------------------------

Comment(by mdean):

 This error seems to be relatively common and is due to restoring a
 0.21-fixes DB on top of a 0.22 DB schema (such as the "blank" ones
 provided by distros/packages).  The issue will occur for users who do a
 "binary" restore (copying the 0.21 binary MySQL data files on top of the
 0.22 DB data files) as well as those who do a "SQL" restore (using a
 backup script).  In the latter case--using a SQL restore of 0.21-fixes
 data into a 0.22-schema database--MySQL will do automatic conversions of
 data formats where the schema has changed and will cause data corruption.

 Users restoring backups ''must'' DROP the old database before restoring
 the backup.  Please see
 http://www.mythtv.org/wiki/Database_Backup_and_Restore#Database_Restore
 for more information, and please use the restore script to do the restore
 (as it performs sanity checks and alerts the user when something is
 wrong).

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/6923#comment:4>
MythTV <http://www.mythtv.org/>
MythTV


More information about the mythtv-commits mailing list