OTRS Upgrade Failed - SQL Problem

[brice]

Hi all,

First time I have to upgrade OTRS in my company, for the moment we have OTRS 2.4.7 and we want to upgrade it to 3.0.4.

I followed the Upgrade steps with the official documentation, but the Database Schema Upgrade failed.

Our OTRS Database if MyISAM Only, but with the SQL upgrade script new tables (virtual_fs%) are created with InnoDB Engine. Engine is not supplied in the Query so I think SQL statements are used only by InnoDB.

It failed when it tried to add the Foreign Key Constraint at the end of the upgrade script:

[code]
ALTER TABLE ticket_flag ADD CONSTRAINT FK_ticket_flag_ticket_id_id FOREIGN KEY (ticket_id) REFERENCES ticket (id);
[/code]

I'm not a big fan of InnoDB, so my knowledge of it is not great. To add the constraint, the target table must also be in the InnoDB Engine ? Ticket table is in MyISAM Engine.

My point is, does OTRS 3 needs only InnoDB database now ? So I'll have to alter my tables with the InnoDB Engine ?

Thank you for your time.

[brice]

I just saw that there are 2.4.8 and 2.4.9, must I upgrade to those version before upgrading to the 3.0.4 ?

[brice]

I could solve the problem.

In fact our server is InnoDB by default and when creating a new table it'll be in the engine. So when it tried to add the constraint it broke up because the other tables where in MyISAM Engine.

Lesson from this:
- Beware when 2 different admin manage the same server differently and doesn't communicate
- Check your tables storage engine and the default storage engine before upgrading the DB!

PS: I still tried with full InnoDB database but it didn't work. This is for information, not a question ;)