[solved] TV Server Configuration gone after update from 1.8 pre release (1 Viewer)

[killer8]

I finally got everything to work. I upgrade my database manually with this guide http://wiki.team-mediaportal.com/1_...Server/Update_MySQL_Database_MyISAM_to_InnoDB to 5.6 prior I installed the 1.8 final update.

After that the update went just fine.

 

[killer8]

I still got a question. When running SHOW ENGINES; on the db it shows innodb as default. But when checking the tables the engine is still myisam. Is it recommended to change this manually to Innodb? I mean should the installer have made this change for me or are the tables still myisam instead of innodb?

 

[HomeY]

No... I have the older .db3 database files..
Maybe its time to reload and point it at my MySQL system... hmmmm

Keep in mind MySQL is only used for the TV Server database.
The database folder containing all the .db3 files are SQLite database files used by (default) plugins only.

 

[HomeY]

I still got a question. When running SHOW ENGINES; on the db it shows innodb as default. But when checking the tables the engine is still myisam. Is it recommended to change this manually to Innodb? I mean should the installer have made this change for me or are the tables still myisam instead of innodb?

MySQL 5.6 uses InnoDB by default, so i assume something didn't went well with the install/upgrade.
Can you post screenshots for the statements:

SHOW ENGINES

SHOW TABLE STATUS

 

[killer8]

Here is my result. Everything is still MyISAM, also the row format is dynamic where your's is compact.

Table history seems to be crashed. I will fix this table.

Should I alter table everything to be innodb?

 

[HomeY]

also the row format is dynamic where your's is compact.

That's because my Engine is set to InnoDB and yours still is MyISAM.

Did you export your settings before the upgrade process? If you have an export, i suggest to remove MySQL completely (including removing the dB folder(s) in program data & appdata folders!) and then run the DeployTool installer again to install MySQL 5.6 (+ 1.8 Final), which should have InnoDB as default engine. No clue why you are on MyISAM. Are you sure your MySQL install is 5.6?

 

[killer8]

Yes I'm sure. I upgraded it manually because the 1.8 upgrade with the upgrade from mysql 5.1 to 5.6 removed all settings from my db.

So I upgrade my db to 5.6 when mediaportal was still on 1.7 after that upgrade mediaportal to 1.8.

I also tried export the configuration while install was 1.7 before(did a couple of system restores to see what the impact of different upgrades was) and import after the upgrade to 1.8 but this broke the complete db and made the tv server configuration usless because all menu items are gone and the logs shows errors.

I will migrate it by alter tableing the tables. I think that will give the same result and give me a proper database for the future right? Do I have to change anything else to get the correct db for mediaportal 1.8?

 

[HomeY]

Please run the attached query. That should fix the dB.

 

[killer8]

Thank you I just wrote something like that myself but some column changes were missing. The USE %TvLibrary%; in your script is wrong since the db is called mptvdb.

My db looks exactly like yours now (see screenshot) So I think it's fine for future updates now right?

Thank you, I really appreciate your help.

 

[HomeY]

The USE %TvLibrary%; in your script is wrong since the db is called mptvdb.

My bad, missed that part It's executed from C# so that's why that reference was in there.

My db looks exactly like yours now (see screenshot) So I think it's fine for future updates now right?

Yeps, looking good so should be fine now.