Mailing List Archive: MythTV: Users

major db problem upgrading from 0.21-fixes to 0.22

Index | Next | Previous | View Threaded

da_audiophile at yahoo

Mar 6, 2010, 3:23 PM

Post #1 of 8 (921 views)
Permalink

major db problem upgrading from 0.21-fixes to 0.22

I'm running a LinHES box (distro based on Arch) and have experienced a horrible problem while upgrading from 0.21-fixes to 0.22. I have all the packages installed, but for some reason my database contains errors that prevent it from being upgraded to 0.22.

Here is a clip of my /var/log/mythtv/mythbackend.log

2010-03-06 18:08:58.534 Using runtime prefix = /usr
2010-03-06 18:08:58.633 Using configuration directory = /home/mythtv/.mythtv
2010-03-06 18:08:58.659 Empty LocalHostName.
2010-03-06 18:08:58.683 Using localhost value of mythtv
2010-03-06 18:08:58.714 New DB connection, total: 1
2010-03-06 18:08:58.737 Connected to database 'mythconverg' at host: localhost
2010-03-06 18:08:58.759 Closing DB connection named 'DBManager0'
2010-03-06 18:08:58.784 Connected to database 'mythconverg' at host: localhost
2010-03-06 18:08:58.811 Current MythTV Schema Version (DBSchemaVer): 1215
2010-03-06 18:08:58.834 MythTV database schema is old. Waiting to see if DB is being upgraded.
2010-03-06 18:08:59.859 New DB connection, total: 2
2010-03-06 18:08:59.908 Connected to database 'mythconverg' at host: localhost
2010-03-06 18:08:59.952 Current MythTV Schema Version (DBSchemaVer): 1215
2010-03-06 18:09:00.977 Current MythTV Schema Version (DBSchemaVer): 1215
2010-03-06 18:09:02.017 Current MythTV Schema Version (DBSchemaVer): 1215
2010-03-06 18:09:03.083 Current MythTV Schema Version (DBSchemaVer): 1215
2010-03-06 18:09:04.156 Current MythTV Schema Version (DBSchemaVer): 1215
2010-03-06 18:09:04.220 Timed out waiting.
2010-03-06 18:09:04.251 Backing up database with script: '/usr/share/mythtv/mythconverg_backup.pl'
2010-03-06 18:09:08.404 Database Backup complete.
2010-03-06 18:09:08.484 Backed up database to file: '/myth/tv/mythconverg-1215-20100306180904.sql.gz'
2010-03-06 18:09:08.516 Console is non-interactive, can't prompt user...
2010-03-06 18:09:08.548 Upgrading.
2010-03-06 18:09:08.649 Newest MythTV Schema Version : 1244
2010-03-06 18:09:10.425 New DB connection, total: 3
2010-03-06 18:09:10.483 Connected to database 'mythconverg' at host: localhost
2010-03-06 18:09:10.505 Upgrading to MythTV schema version 1216
2010-03-06 18:09:12.808 DB Error (Performing database upgrade):
Query was: ALTER TABLE program MODIFY title varbinary(128) NOT NULL default '', MODIFY subtitle varbinary(128) NOT NULL default '', MODIFY description blob NOT NULL, MODIFY category varbinary(64) NOT NULL default '', MODIFY category_type varbinary(64) NOT NULL default '', MODIFY title_pronounce varbinary(128) NOT NULL default '', MODIFY seriesid varbinary(40) NOT NULL default '', MODIFY showtype varbinary(30) NOT NULL default '', MODIFY colorcode varbinary(20) NOT NULL default '', MODIFY syndicatedepisodenumber varbinary(20) NOT NULL default '', MODIFY programid varbinary(40) NOT NULL default '';
Error was: Driver error was [2/1054]:
QMYSQL3: Unable to execute statement
Database error was:
Unknown column 'title_pronounce' in 'program'

new version: 1216
2010-03-06 18:09:12.841 DB charset conversions update failed! Your database seems to be partially corrupted. Please move the backup to a safe place. Your database must be fixed before you can upgrade beyond 0.21-fixes. Please see http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding for information.
2010-03-06 18:09:12.866 Database Schema upgrade FAILED, unlocking.
2010-03-06 18:09:12.891 Couldn't upgrade database to new schema
2010-03-06 18:09:13.049 mythbackend version: branches/release-0-22-fixes [23566M] www.mythtv.org

I have no idea what these errors are nor how to resolve them. Any advise is greatly appreciated.

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

knowledgejunkie at gmail

Mar 6, 2010, 3:41 PM

Post #2 of 8 (898 views)
Permalink

Re: major db problem upgrading from 0.21-fixes to 0.22 [In reply to]

On 6 March 2010 23:23, Audio Phile <da_audiophile [at] yahoo> wrote:

> new version: 1216
> 2010-03-06 18:09:12.841 DB charset conversions update failed! Your database seems to be partially corrupted. Please move the backup to a safe place. Your database must be fixed before you can upgrade beyond 0.21-fixes. Please see http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding for information.
> 2010-03-06 18:09:12.866 Database Schema upgrade FAILED, unlocking.
> 2010-03-06 18:09:12.891 Couldn't upgrade database to new schema
> 2010-03-06 18:09:13.049 mythbackend version: branches/release-0-22-fixes [23566M] www.mythtv.org
>
> I have no idea what these errors are nor how to resolve them. Any advise is greatly appreciated.

If you haven't already, I suggest you start by reading the relevant
wiki entry (the URL is purposefully provided in the error message
above).

Cheers,
Nick

--
Nick Morrott

MythTV Official wiki: http://mythtv.org/wiki/
MythTV users list archive: http://www.gossamer-threads.com/lists/mythtv/users

"An investment in knowledge always pays the best interest." - Benjamin Franklin
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mtdean at thirdcontact

Mar 6, 2010, 10:16 PM

Post #3 of 8 (881 views)
Permalink

Re: major db problem upgrading from 0.21-fixes to 0.22 [In reply to]

On 03/06/2010 06:41 PM, Nick Morrott wrote:
> On 6 March 2010 23:23, Audio Phile wrote:
>
>> new version: 1216
>> 2010-03-06 18:09:12.841 DB charset conversions update failed! Your database seems to be partially corrupted. Please move the backup to a safe place. Your database must be fixed before you can upgrade beyond 0.21-fixes. Please see http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding for information.
>> 2010-03-06 18:09:12.866 Database Schema upgrade FAILED, unlocking.
>> 2010-03-06 18:09:12.891 Couldn't upgrade database to new schema
>> 2010-03-06 18:09:13.049 mythbackend version: branches/release-0-22-fixes [23566M] www.mythtv.org
>>
>> I have no idea what these errors are nor how to resolve them. Any advise is greatly appreciated.
>>
> If you haven't already, I suggest you start by reading the relevant
> wiki entry (the URL is purposefully provided in the error message
> above).
>

Normally, this would be the right advice, but in this case, the error is
due to a corrupt database /schema/, not corrupt data. Your program
table is missing the title_pronounce column. The only supported fix is
for you to use the "only use if your database is corrupt beyond repair"
partial-restore (since yours is corrupt beyond repair--meaning even if
you fix the problems you see, you'll likely leave a broken DB schema or
at the least broken DB data: if one thing is broken in a way that
MythTV could /never/ have broken it, there's likely far more broken than
what you'll notice).
http://www.mythtv.org/wiki/Database_Backup_and_Restore#Partial_restore_of_a_backup
(and I highly recommend you don't use the partial restore with plugin data)

You'll need to take your 0.21-fixes database backup (the
pre-all-the-upgrade-attempts backup you made before attempting the first
upgrade--do not try to use the partially-upgraded version you have now,
as it is now corrupt because of the upgrade failure), create a blank
0.21-fixes database schema (no data, but all tables intact), and do a
partial restore of the data. Basically, you want the opposite of:
http://www.mythtv.org/wiki/Database_Backup_and_Restore#Partial_restore_when_upgrading_MythTV
(rather than upgrade, backup, create blank DB, do partial restore;
you'll have use a pre-upgrade blank DB, do a partial restore, then
upgrade since your database is not upgradeable)

Since you need MythTV 0.21-fixes installed to create a blank DB schema,
you'll probably want to use the blank DB schema I posted to the list, as
described at:
http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding#Partial_vs_.22equal.22_corruption

So, long story short, the answer to your problem is on the page
referenced in the error message and that Nick highlighted for you--but
the problem you have is far more serious than the problem that page
describes, so you'll need to use the partial corruption fix (which,
fortunately, should fix the issues you're seeing).

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mtdean at thirdcontact

Mar 6, 2010, 10:26 PM

Post #4 of 8 (880 views)
Permalink

Re: major db problem upgrading from 0.21-fixes to 0.22 [In reply to]

On 03/07/2010 01:16 AM, Michael T. Dean wrote:
> On 03/06/2010 06:41 PM, Nick Morrott wrote:
>> On 6 March 2010 23:23, Audio Phile wrote:
>>> new version: 1216
>>> 2010-03-06 18:09:12.841 DB charset conversions update failed! Your
>>> database seems to be partially corrupted. Please move the backup to
>>> a safe place. Your database must be fixed before you can upgrade
>>> beyond 0.21-fixes. Please see
>>> http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding for
>>> information.
>>> 2010-03-06 18:09:12.866 Database Schema upgrade FAILED, unlocking.
>>> 2010-03-06 18:09:12.891 Couldn't upgrade database to new schema
>>> 2010-03-06 18:09:13.049 mythbackend version:
>>> branches/release-0-22-fixes [23566M] www.mythtv.org
>>>
>>> I have no idea what these errors are nor how to resolve them. Any
>>> advise is greatly appreciated.
>> If you haven't already, I suggest you start by reading the relevant
>> wiki entry (the URL is purposefully provided in the error message
>> above).
> Normally, this would be the right advice, but in this case, the error
> is due to a corrupt database /schema/, not corrupt data.

BTW, I just realized this sounds like I'm saying Nick's advice is bad.
What I was trying to say is that the error message itself isn't the
right advice--i.e. you don't have partially corrupt database character
encoding, but you have a completely corrupt schema.

Nick's advice is correct--follow the instructions provided by the error
message, even though your issue is different, the same "partial
corruption" solution applies.

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

da_audiophile at yahoo

Mar 7, 2010, 2:30 AM

Post #5 of 8 (859 views)
Permalink

Re: major db problem upgrading from 0.21-fixes to 0.22 [In reply to]

Thank you both for the advice.
@mtdean - I attempted your procedure (http://www.gossamer-threads.com/lists/mythtv/users/406111#406111) but ran into trouble:

I can drop the db okay but I couldn't use your code with the echo << "EOF", I had to type out each step as shown:

$ mysql -umythtv -p mythconverg
Enter password:
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 535
Server version: 5.0.75 Source distribution

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> DROP DATABASE IF EXISTS mythconverg;
Query OK, 54 rows affected (0.01 sec)

mysql> CREATE DATABASE IF NOT EXISTS mythconverg;
Query OK, 1 row affected (0.00 sec)

mysql> ALTER DATABASE mythconverg DEFAULT CHARACTER SET latin1;
Query OK, 1 row affected (0.01 sec)

mysql> quit
Bye

I can restore the blank one okay:
[mythtv [at] mytht ~]$ /usr/share/mythtv/mythconverg_restore.pl --dir=$HOME --file=mythconverg-1214-blank.sql.gz --verbose

Configuring environment:
- username: mythtv
- HOME: /home/mythtv
- MYTHCONFDIR: /home/mythtv/.mythtv

Parsing configuration files:
- checking: /home/mythtv/.mythtv/config.xml
parsing: /home/mythtv/.mythtv/config.xml
- checking: /home/mythtv/.mythtv/backuprc

Applying command-line arguments.

Checking configuration.

Database Information:
DBHostName: localhost
DBPort: 0
DBUserName: mythtv
DBPassword: XXX
DBName: mythconverg
DBSchemaVer:
DBBackupDirectory: /home/mythtv
DBBackupFilename: mythconverg-1214-blank.sql.gz
create_database:

Executables:
mysql_client: mysql
uncompress: gzip -d

Miscellaneous:
partial_restore: no
restore_xmltvids: no
change_hostname: no

Checking database.

Found 0 tables in the database.

Backup file is compressed.
- Uncompressing backup file with IO::Uncompress::Gunzip.

Attempting to use supplied password for mysql command-line client.
Any [client] or [mysql] password specified in the MySQL options file will
take precedence.

Executing command:
'mysql' --defaults-extra-file='/tmp/RCfj5LUMX4' --host='localhost' --user='mythtv' 'mythconverg'

mysql exited with status: 0

Restored 1553 of 1553 lines.

Successfully restored backup.

But I can't restore my backup:

[mythtv [at] mytht ~]$ /usr/share/mythtv/mythconverg_restore.pl --dir=$HOME --file=mythconverg-1215-20100306190349.sql.gz --verbose

Configuring environment:
- username: mythtv
- HOME: /home/mythtv
- MYTHCONFDIR: /home/mythtv/.mythtv

Parsing configuration files:
- checking: /home/mythtv/.mythtv/config.xml
parsing: /home/mythtv/.mythtv/config.xml
- checking: /home/mythtv/.mythtv/backuprc

Applying command-line arguments.

Checking configuration.

Database Information:
DBHostName: localhost
DBPort: 0
DBUserName: mythtv
DBPassword: XXX
DBName: mythconverg
DBSchemaVer:
DBBackupDirectory: /home/mythtv
DBBackupFilename: mythconverg-1215-20100306190349.sql.gz
create_database:

Executables:
mysql_client: mysql
uncompress: gzip -d

Miscellaneous:
partial_restore: no
restore_xmltvids: no
change_hostname: no

Checking database.

Found 54 tables in the database.
WARNING: Database not empty.

ERROR: Unable to do a full restore. The database contains data.

Can you advise?

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

da_audiophile at yahoo

Mar 7, 2010, 4:31 AM

Post #6 of 8 (853 views)
Permalink

Re: major db problem upgrading from 0.21-fixes to 0.22 [In reply to]

OK! The problem was that I didn't add the --partial_restore switch to the last step. Doing that fixed it and I can now use the 0.22 except that my mythvideo plugin now doesn't work. The GUI tells me that mythtvideo plugin isn't configured but I don't see where I am able to do so.

$ ./mythconverg_restore.pl --dir=$HOME --file=mythconverg-1214-20100307062803.sql.gz --partial_restore --verbose

Configuring environment:
- username: mythtv
- HOME: /home/mythtv
- MYTHCONFDIR: /home/mythtv/.mythtv

Parsing configuration files:
- checking: /home/mythtv/.mythtv/config.xml
parsing: /home/mythtv/.mythtv/config.xml
- checking: /home/mythtv/.mythtv/backuprc
parsing: /home/mythtv/.mythtv/backuprc

Applying command-line arguments.

Checking configuration.

Database Information:
DBHostName: localhost
DBPort: 0
DBUserName: mythtv
DBPassword: XXX
DBName: mythconverg
DBSchemaVer:
DBBackupDirectory: /home/mythtv
DBBackupFilename: mythconverg-1214-20100307062803.sql.gz
create_database:

Executables:
mysql_client: mysql
uncompress: gzip -d

Miscellaneous:
partial_restore: yes
with_plugin_data: no
restore_xmltvids: no
change_hostname: no

Checking database.

Found 54 tables in the database.

Backup file is compressed.
- Uncompressing backup file with IO::Uncompress::Gunzip.

Attempting to use supplied password for mysql command-line client.
Any [client] or [mysql] password specified in the MySQL options file will
take precedence.

Restoring partial backup with filter:
(40101 SET NAMES |^INSERT INTO \`?(oldrecorded|record|recorded|recordedmarkup|recordedprogram|recordedrating|recordedseek)\`? )

Executing command:
'mysql' --defaults-extra-file='/tmp/kUypOugWIw' --host='localhost' --user='mythtv' 'mythconverg'

mysql exited with status: 0

Restored 13 of 3383 lines.

Successfully restored backup.

--- On Sun, 3/7/10, Audio Phile <da_audiophile [at] yahoo> wrote:

> From: Audio Phile <da_audiophile [at] yahoo>
> Subject: Re: major db problem upgrading from 0.21-fixes to 0.22
> To: mythtv-users [at] mythtv
> Date: Sunday, March 7, 2010, 5:30 AM
> Thank you both for the advice.
> @mtdean - I attempted your procedure (http://www.gossamer-threads.com/lists/mythtv/users/406111#406111)
> but ran into trouble:
>
> I can drop the db okay but I couldn't use your code with
> the echo << "EOF", I had to type out each step as
> shown:
>
> $ mysql -umythtv -p mythconverg
> Enter password:
> Reading table information for completion of table and
> column names
> You can turn off this feature to get a quicker startup with
> -A
>
> Welcome to the MySQL monitor. Commands end with ; or
> \g.
> Your MySQL connection id is 535
> Server version: 5.0.75 Source distribution
>
> Type 'help;' or '\h' for help. Type '\c' to clear the
> buffer.
>
> mysql> DROP DATABASE IF EXISTS mythconverg;
> Query OK, 54 rows affected (0.01 sec)
>
> mysql> CREATE DATABASE IF NOT EXISTS mythconverg;
> Query OK, 1 row affected (0.00 sec)
>
> mysql> ALTER DATABASE mythconverg DEFAULT CHARACTER SET
> latin1;
> Query OK, 1 row affected (0.01 sec)
>
> mysql> quit
> Bye
>
> I can restore the blank one okay:
> [mythtv [at] mytht ~]$ /usr/share/mythtv/mythconverg_restore.pl
> --dir=$HOME --file=mythconverg-1214-blank.sql.gz --verbose
>
> Configuring environment:
> - username: mythtv
> - HOME: /home/mythtv
> - MYTHCONFDIR: /home/mythtv/.mythtv
>
> Parsing configuration files:
> - checking: /home/mythtv/.mythtv/config.xml
>    parsing:
> /home/mythtv/.mythtv/config.xml
> - checking: /home/mythtv/.mythtv/backuprc
>
> Applying command-line arguments.
>
> Checking configuration.
>
> Database Information:
>    DBHostName:
> localhost
>
>    DBPort: 0
>    DBUserName: mythtv
>    DBPassword: XXX
>
>    DBName: mythconverg
> DBSchemaVer:
> DBBackupDirectory: /home/mythtv
>    DBBackupFilename:
> mythconverg-1214-blank.sql.gz
> create_database:
>
> Executables:
>    mysql_client: mysql
>    uncompress: gzip -d
>
> Miscellaneous:
> partial_restore: no
>    restore_xmltvids: no
> change_hostname: no
>
> Checking database.
>
> Found 0 tables in the database.
>
> Backup file is compressed.
> - Uncompressing backup file with IO::Uncompress::Gunzip.
>
> Attempting to use supplied password for mysql command-line
> client.
> Any [client] or [mysql] password specified in the MySQL
> options file will
> take precedence.
>
> Executing command:
> 'mysql' --defaults-extra-file='/tmp/RCfj5LUMX4'
> --host='localhost' --user='mythtv' 'mythconverg'
>
> mysql exited with status: 0
>
> Restored 1553 of 1553 lines.
>
> Successfully restored backup.
>
> But I can't restore my backup:
>
> [mythtv [at] mytht ~]$ /usr/share/mythtv/mythconverg_restore.pl
> --dir=$HOME --file=mythconverg-1215-20100306190349.sql.gz
> --verbose
>
> Configuring environment:
> - username: mythtv
> - HOME: /home/mythtv
> - MYTHCONFDIR: /home/mythtv/.mythtv
>
> Parsing configuration files:
> - checking: /home/mythtv/.mythtv/config.xml
>    parsing:
> /home/mythtv/.mythtv/config.xml
> - checking: /home/mythtv/.mythtv/backuprc
>
> Applying command-line arguments.
>
> Checking configuration.
>
> Database Information:
>    DBHostName:
> localhost
>
>    DBPort: 0
>    DBUserName: mythtv
>    DBPassword: XXX
>
>    DBName: mythconverg
> DBSchemaVer:
> DBBackupDirectory: /home/mythtv
>    DBBackupFilename:
> mythconverg-1215-20100306190349.sql.gz
> create_database:
>
> Executables:
>    mysql_client: mysql
>    uncompress: gzip -d
>
> Miscellaneous:
> partial_restore: no
>    restore_xmltvids: no
> change_hostname: no
>
> Checking database.
>
> Found 54 tables in the database.
> WARNING: Database not empty.
>
> ERROR: Unable to do a full restore. The database contains
> data.
>
> Can you advise?

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

mtdean at thirdcontact

Mar 7, 2010, 5:29 AM

Post #7 of 8 (851 views)
Permalink

Re: major db problem upgrading from 0.21-fixes to 0.22 [In reply to]

On 03/07/2010 05:30 AM, Audio Phile wrote:
> Thank you both for the advice.
> @mtdean - I attempted your procedure (http://www.gossamer-threads.com/lists/mythtv/users/406111#406111) but ran into trouble:
>
> I can drop the db okay but I couldn't use your code with the echo<< "EOF",

You almost definitely had something (like a space) after the EOF (bad
copy/paste).

> I can restore the blank one okay:
> [mythtv [at] mytht ~]$ /usr/share/mythtv/mythconverg_restore.pl --dir=$HOME --file=mythconverg-1214-blank.sql.gz --verbose
>
...
> Successfully restored backup.
>
> But I can't restore my backup:
>
> [mythtv [at] mytht ~]$ /usr/share/mythtv/mythconverg_restore.pl --dir=$HOME --file=mythconverg-1215-20100306190349.sql.gz --verbose
>

[Look closely at the above. What's missing?] ...

> Found 54 tables in the database.
> WARNING: Database not empty.
>
> ERROR: Unable to do a *full* restore. The database contains data.
>

[emphasis added]

Hmmm... Unable to do a *full* restore because the database is not
empty. What were we trying to do?

> Can you advise?
>

Re-read the 2 sets of instrucitons you were given (my e-mail and
http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding#Partial_vs_.22equal.22_corruption
). You're doing something wrong

Mike "I can write the instructions, but I don't want to also have to
read them to you" Dean
_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

DEPontius at edgehp

Mar 7, 2010, 7:23 PM

Post #8 of 8 (791 views)
Permalink

Re: major db problem upgrading from 0.21-fixes to 0.22 [In reply to]

Michael T. Dean wrote:
> On 03/07/2010 05:30 AM, Audio Phile wrote:
>> Thank you both for the advice.
>> @mtdean - I attempted your procedure
>> (http://www.gossamer-threads.com/lists/mythtv/users/406111#406111) but
>> ran into trouble:
>>
>> I can drop the db okay but I couldn't use your code with the echo<<
>> "EOF",
>
> You almost definitely had something (like a space) after the EOF (bad
> copy/paste).
>
>> I can restore the blank one okay:
>> [mythtv [at] mytht ~]$ /usr/share/mythtv/mythconverg_restore.pl
>> --dir=$HOME --file=mythconverg-1214-blank.sql.gz --verbose
>>
> ...
>> Successfully restored backup.
>>
>> But I can't restore my backup:
>>
>> [mythtv [at] mytht ~]$ /usr/share/mythtv/mythconverg_restore.pl
>> --dir=$HOME --file=mythconverg-1215-20100306190349.sql.gz --verbose
>>
>
> [Look closely at the above. What's missing?] ...
>
>> Found 54 tables in the database.
>> WARNING: Database not empty.
>>
>> ERROR: Unable to do a *full* restore. The database contains data.
>>
>
> [emphasis added]
>
> Hmmm... Unable to do a *full* restore because the database is not
> empty. What were we trying to do?
>
>> Can you advise?
>>
>
> Re-read the 2 sets of instrucitons you were given (my e-mail and
> http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding#Partial_vs_.22equal.22_corruption
> ). You're doing something wrong

The instructions at
http://www.gossamer-threads.com/lists/mythtv/users/406111#406111
are missing the "--partial_restore" flag on step 4. That fact gets
picked up by reading the
http://www.mythtv.org/wiki/Fixing_Corrupt_Database_Encoding#Partial_vs_.22equal.22_corruption
link, then following the "partial restore" link on that page.

In other words, it takes a bit more careful reading than it would if the
flag weren't missing from the first reference. It also takes realizing
that there is an omission on the first reference. Figuring that out was
what it took to get my database migrated.

Dale Pontius
>
> Mike "I can write the instructions, but I don't want to also have to
> read them to you" Dean
> _______________________________________________
> mythtv-users mailing list
> mythtv-users [at] mythtv
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

_______________________________________________
mythtv-users mailing list
mythtv-users [at] mythtv
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads