I've been running 0.21-fixes on gentoo for quite a while, and thought I
had already done the database encoding fix on that... in any case, I've
double checked my configuration - when I restore the 0.21 database, i
get the following mysql status:<br>
<br>--------------<br>mysql Ver 14.12 Distrib 5.0.84, for pc-linux-gnu (x86_64) using readline 6.0<br><br>Connection id: 15<br>Current database: mythconverg<br>Current user: root@localhost<br>SSL: Not in use<br>
Current pager: stdout<br>Using outfile: ''<br>Using delimiter: ;<br>Server version: 5.0.84 Gentoo Linux mysql-5.0.84-r1<br>Protocol version: 10<br>Connection: Localhost via UNIX socket<br>
Server characterset: latin1<br>Db characterset: latin1<br>Client characterset: latin1<br>Conn. characterset: latin1<br>UNIX socket: /var/run/mysqld/mysqld.sock<br>Uptime: 28 min 56 sec<br>
<br>Threads: 1 Questions: 3131 Slow queries: 0 Opens: 720 Flush tables: 1 Open tables: 5 Queries per second avg: 1.804<br>--------------<br><br><br>Then I start 0.22 mythbackend, and it says in the log:<br><br>2010-03-08 11:44:05.858 Current MythTV Schema Version (DBSchemaVer): 1215<br>
2010-03-08 11:44:05.860 MythTV database schema is old. Waiting to see if DB is being upgraded.<br>2010-03-08 11:44:06.862 New DB connection, total: 2<br>2010-03-08 11:44:06.864 Connected to database 'mythconverg' at host: localhost<br>
2010-03-08 11:44:06.867 Current MythTV Schema Version (DBSchemaVer): 1215<br>2010-03-08 11:44:07.870 Current MythTV Schema Version (DBSchemaVer): 1215<br>2010-03-08 11:44:08.873 Current MythTV Schema Version (DBSchemaVer): 1215<br>
2010-03-08 11:44:09.876 Current MythTV Schema Version (DBSchemaVer): 1215<br>2010-03-08 11:44:10.879 Current MythTV Schema Version (DBSchemaVer): 1215<br>2010-03-08 11:44:10.880 Timed out waiting.<br>2010-03-08 11:44:10.886 Backing up database with script: '/usr/share/mythtv/<a href="http://mythconverg_backup.pl/" target="_blank">mythconverg_backup.pl</a>'<br>
2010-03-08 11:44:16.535 Database Backup complete.<br>2010-03-08 11:44:16.540 Backed up database to file: '/video/recordings/<div id=":f" class="ii gt">mythconverg-1215-20100308114410.sql.gz'<br>2010-03-08 11:44:16.550 Console is non-interactive, can't prompt user...<br>
2010-03-08 11:44:16.551 Upgrading.<br>2010-03-08 11:44:16.553 Newest MythTV Schema Version : 1244<br>2010-03-08 11:44:16.980 Database corruption detected. Unable to proceed with database upgrade. (Table: people, Warnings: 269)<br>
2010-03-08 11:44:16.982 Your database must be fixed before you can upgrade beyond 0.21-fixes. Please see <a href="http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding" target="_blank">http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding</a> for information on fixing your database.<br>
2010-03-08 11:44:16.984 Database Schema upgrade FAILED, unlocking.<br>2010-03-08 11:44:16.985 Couldn't upgrade database to new schema<br><br><br><br>At this point, if I stop the backend and do another mysql status, it now says:<br>
<br>--------------<br>mysql Ver 14.12 Distrib 5.0.84, for pc-linux-gnu (x86_64) using readline 6.0<br><br>Connection id: 21<br>Current database: mythconverg<br>Current user: root@localhost<br>SSL: Not in use<br>
Current pager: stdout<br>Using outfile: ''<br>Using delimiter: ;<br>Server version: 5.0.84 Gentoo Linux mysql-5.0.84-r1<br>Protocol version: 10<br>Connection: Localhost via UNIX socket<br>
Server characterset: latin1<br>Db characterset: utf8<br>Client characterset: latin1<br>Conn. characterset: latin1<br>UNIX socket: /var/run/mysqld/mysqld.sock<br>Uptime: 31 min 35 sec<br>
<br>Threads: 1 Questions: 4172 Slow queries: 0 Opens: 1103 Flush tables: 1 Open tables: 64 Queries per second avg: 2.202<br>--------------<br><br><br>(note the Db characterset changed from latin1 to utf8 - it seems that starting 0.22 actually corrupts the character set?) <br>
<br>Is this the dreaded partial corruption? I've tried doing a
partial restore on top of the 0.21 blank.sql file posted here a few
months ago and it still is complaining - this time only 1 warning, in
the oldrecorded table. Is there any way to find the "bad" characters
in the database backup and fix them by hand? I really don't want to
lose all my recordings but I'm somewhat at a loss as to what to try
next (besides re-installing 0.21...)<br>
<br>Thanks,<br><font color="#888888">Scott</font></div>