Nils told me how to reproduce: The problem was, one of our devs added the smime_signer_cert tables to 2.4 after we already released 2.4.11, then rolled it back because it should not be added on a patch level release. He failed to roll back the database upgrade files however.. We created 2.4.12 which contained these new database files, and now there is an issue if you do the upgrade from 2.3 > 2.4 > 3.0 > 3.1.
I rolled back his changes. If you'll use the database upgrade files from http://source.otrs.org/viewvc.cgi/otrs/scripts/?hideattic=1&sortby=date&pathrev=rel-2_4 you would be good. I vcreated a bug report for it: http://bugs.otrs.org/show_bug.cgi?id=8300 - Database upgrade issue when upgrading from 2.3 > 2.4 > 3.0 > 3.1: table smime_signer_cert_relations' already exists. thanks! -- Mike On Thu, Mar 8, 2012 at 03:04, Ugo Bellavance <u...@lubik.ca> wrote: > On 2012-03-07 12:21, Michiel Beijen wrote: >> >> Hi Steven, >> >> We do not use a specific engine. This means that we'll use whatever >> engine your MySQL uses as default. For instance on Windows the default >> engine is InnoDB, and I guess more and more InnoDB is becoming the >> default storage engine for MySQL. >> >> So I guess you simply set up MySQL with MyISAM as a storage engine, >> then installed OTRS, then the MySQL default storage engine switched to >> InnoDB beause of an OS or MySQL upgrade, then you upgraded OTRS and >> now you'll have tables with different storage engines in one database. >> >> So I'll understand your issue but you should probably complain with >> your OS vendor, and not with OTRS. >> >> As for the foreign keys: MyISAM does not USE foreign keys but you can >> specify one. It will just not be enforced. This to support people like >> us who have ONE create table statement for MySQL regardless of the >> storage engine. Ref: >> http://dev.mysql.com/doc/refman/5.1/en/ansi-diff-foreign-keys.html >> >> The error message you have is that the table >> "smime_signer_cert_relations" is already there, and the upgrade script >> tries to create it a second time and then fails. This table is added >> in OTRS 3.1, and you should really only have that after you ran the >> update script "DBUpdate-to-3.1.mysql.sql" -- my idea is you simply >> tried to run this script two times. >> >> If you can reproduce this error, obviously I would be interested to >> know how you got this. > > > I'll definitely try to reproduce the issue I got. > > Thanks, > > Ugo > > > --------------------------------------------------------------------- > OTRS mailing list: otrs - Webpage: http://otrs.org/ > Archive: http://lists.otrs.org/pipermail/otrs > To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
