[mythtv-users] Upgrade issue, unable to upgrade music schema from 1023 to 1024

[Oz Dror]

Thanks it is now fixed

On Thu, Apr 28, 2016 at 6:44 PM, Michael T. Dean <mtdean at thirdcontact.com>
wrote:

> On 04/28/2016 02:02 PM, Oz Dror wrote:
>
>> Hi
>>
>> I have upgraded my Ubuntu 15.10 to 16.04
>> In this process mythtv was upgraded from 0.27 to 0.28
>>
>> The database was upgraded from 1317 to 1344.
>>
>> When running mythfrontend
>>
>> I get the warning:
>> Mythtv wants to upgrade your database,
>> for the Music schema, from 1023 to 1024.
>>
>> When I try to upgrade I get the message:
>> There are also other clients using this database. They should be shut
>> down first.
>>
>> I actually have no other clients. So I am not able to do this minor
>> upgrade.
>>
>> I also get this error in the terminal:
>>
>> 2016-04-28 10:40:22.908033 N  Upgrading to MythMusic schema version 1024
>> 2016-04-28 10:40:22.908293 E  DB Error (Performing database upgrade):
>> Query was: DROP INDEX station ON music_radios;
>> Error was: Driver error was [2/1146]:
>> QMYSQL: Unable to execute query
>> Database error was:
>> Table 'mythconverg.music_radios' doesn't exist
>> new version: 1024
>>
>>
>> The music schema never upgrades, because when I restart mytyhfrontend I
>> get the same warning.
>>
>> When looking at the mysql (mariadb)  database I do not have
>> mythconverg.music_radios.
>>
>> Any help will be appreciated.
>>
>
> Your database is corrupt.  Since the music data is easily re-creatable
> (unlike TV data, where the database is the primary storage for the data,
> the music data is generally in the files), the easiest thing is to start
> your music schema again from scratch. Ideally, shut down your MythTV system
> (at minimum, I highly recommend shutting down all mythfrontend processes on
> all hosts, but if you'd like to be extra careful, shut down all the
> mythbackends, etc, too).  Then, back up your database (
> https://www.mythtv.org/wiki/Database_Backup_and_Restore --but if it
> fails, you'll have to do the following to make it succeed, in which case,
> you may want to just copy the binary data files, or just continue without a
> backup).  Finally, at the shell (as any non-root user), issue the command:
>
> cat << "EOF" | mysql -umythtv -p mythconverg
> DROP TABLE IF EXISTS musicmetadata;
> DROP TABLE IF EXISTS musicplaylist;
> DROP TABLE IF EXISTS smartplaylistcategory;
> DROP TABLE IF EXISTS smartplaylist;
> DROP TABLE IF EXISTS smartplaylistitem;
> DROP TABLE IF EXISTS music_albums;
> DROP TABLE IF EXISTS music_artists;
> DROP TABLE IF EXISTS music_genres;
> DROP TABLE IF EXISTS music_playlists;
> DROP TABLE IF EXISTS music_songs;
> DROP TABLE IF EXISTS music_stats;
> DROP TABLE IF EXISTS music_directories;
> DROP TABLE IF EXISTS music_albumart;
> DROP TABLE IF EXISTS music_radios;
> DROP TABLE IF EXISTS music_streams;
> DROP TABLE IF EXISTS music_smartplaylists;
> DROP TABLE IF EXISTS music_smartplaylist_items;
> DROP TABLE IF EXISTS music_smartplaylist_categories;
> DELETE FROM settings WHERE value = 'MusicDBSchemaVer';
> EOF
>
> when you copy and paste, my recommendation is to exclude the EOF line and
> type EOF (all caps eee-oh-eff, as in end-of-file--with nothing before or
> after on the line) and hit enter.  If you copy the EOF line and the e-mail
> client adds in any extra characters (including tabs or spaces or even
> non-visible characters), it will prevent the command from being submitted
> properly.
>
> Then, restart mythfrontend and it should create the music database schema
> for you.  Then, you can go back into MythMusic to repopulate it/rescan your
> music.
>
> Mike
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20160429/a930fa16/attachment.html>