upgrade to 3.1.1

[cici6160]

I'm getting the following error when running the first sql script (against mysql) >> cat scripts/DBUpdate-to-3.1.mysql.sql | mysql -p -f -u root otrs

ERROR 1062 (23000) at line 187: Duplicate entry '656-Seen-8' for key 'ticket_flag_per_user'

Any ideas?

Thanks in advance

[dddougal]

you have used that entry before, they all have to be unique

[cici6160]

This resolved my issue - not sure how it happened though:

mysql -u root -p
use otrs
select * from ticket_flag where ticket_id=656;
delete from ticket_flag where ticket_id=656 and create_by=8 LIMIT 1;

[marv]

I've got the same problem.

although i've got a lot of duplicate entries.
my "solution" was to uncomment the line 187 in the update-sql script.

any ideas what the sideeffects might be?

[Giulio Soleni]

Same problem... same questions
For me the error is the following:

# cat scripts/DBUpdate-to-3.1.mysql.sql | mysql -p -f -u root otrs
Enter password:
ERROR 1062 (23000) at line 187: Duplicate entry '292-Seen-31' for key 1

and looking at the table actually I have a duplicate entry:

mysql> select * from ticket_flag where ticket_id = '292';
+-----------+------------+--------------+---------------------+-----------+
| ticket_id | ticket_key | ticket_value | create_time | create_by |
+-----------+------------+--------------+---------------------+-----------+
| 292 | Seen | 0 | 2011-08-31 14:32:15 | 1 |
| 292 | Seen | 1 | 2011-08-31 17:05:12 | 29 |
| 292 | Seen | 0 | 2011-08-31 16:57:44 | 30 |
| 292 | Seen | 1 | 2011-09-01 09:40:26 | 31 |
| 292 | Seen | 1 | 2011-09-01 09:40:26 | 31 |
+-----------+------------+--------------+---------------------+-----------+
5 rows in set (0.00 sec)

Anyone may give some hints at least about ticket_flag table..? what's this table usage in the otrs db?

thank you

[imant1]

anyone know how to revert back to older version?

I've error while connecting to mysql..

[jojo]

you can not revert back to an old version

[LarryLevi]

Same problem here. I can't get the version 3.1.1 working right. Since it is impossible to revert back to the old version, it would probably be better to reinstall the older version, right? Version 3.0 worked like a charm for me.

[masmiskun]

can i downgrade theversion? i know upgrade is no question.

[jojo]

you can not downgrade

[earwax]

I got a very similar error when accidentally upgrading from OTRS 3.0.11 to OTRS 3.1.2. I mistaked OTRS 3.1.2 for OTRS 3.0.12. Fortunately I backed up everything and was able to revert back, but I admit I was looking forward to making the jump. Hopefully OTRS can fix this duplicate entry problem.

I've got the same problem.

although i've got a lot of duplicate entries.
my "solution" was to uncomment the line 187 in the update-sql script.

any ideas what the sideeffects might be?

I am not sure what commenting out line 187 would do in the SQL script file, but I would not do it unless OTRS officially says it is safe to do so.

you can not downgrade

jojo is correct. When the SQL script file failed with that duplicate entry error, the script has already created new tables and rows. You have essentially modified the OTRS DB.

Anyhow, let this be a lesson: BACKUP, BACKUP, BACKUP!!!!

[ferrosti]

As far as I can see, this table 'ticket_flag' holds information about seen tickets only.
In case I´d run into this error I´d empty the table BEFORE running the mySQL update script, run the script and afterwards run $OTRS_HOME/bin/otrs.MarkTicketAsSeen.pl.
The only disadvantage I see with this is that all tickets will be marked as seen, so this feature would only apply to new tickets. But I could live with it.

I do not have a copy of 3.1 here to have a look at it. I´d rather recommend to fix this kind of bug, which should not be too difficult, but xxx usually takes some time on bug fixing. Anyhow, you should open a bug report for it, in case there is none opened yet.

[marv]

I agree with you that ignoring this is not the best way to deal with it.

This is the way I went:
1) Comment line 187 in DBUpdate-to-3.1-mysql.sql:
#ALTER TABLE ticket_flag ADD CONSTRAINT ticket_flag_per_user UNIQUE INDEX (ticket_id, ticket_key, create_by);

2) do the update.
3) dump the table ticket_flag
4) empty table ticket_flag
5) execute the ALTER TABLE statement
6) import the table dump

At step 6) you will get errors because you're not allowed to import duplicates. I just skipped them and imported only the unique entries of the dump.