Error on upgrade from 4.0.16 to 5.0.7-01

[arestas]

Hello all,

Iam getting the following error when executing DBUpdate-to-5.pl


Step 7 of 17: Migrate notifications to event based notifications...ERROR: OTRS-DBUpdate-to-5.pl-9 Perl: 5.10.1 OS: linux Time: Tue Mar 29 22:33:36 2016

Message: Can't add notification 'Old Ticket new note notification ( Duplicate Name )', notification already exists!

Traceback (2091):
Module: Kernel::System::NotificationEvent::NotificationAdd Line: 271
Module: main::_MigrateNotifications Line: 1109
Module: ./DBUpdate-to-5.pl Line: 162

error.

[Tue Mar 29 22:33:36 2016] DBUpdate-to-5.pl: Died at ./DBUpdate-to-5.pl line 167.


Can anyone help with this?

Tks

[arestas]

Can anyone help me with this??

Can i comment in the DBUpdate-to-5.pl the part where it will check the step 7??
Is this a good workaround?

Regards,

Lostrans

[arestas]

Can anyone help me with this? :

Regards,

Lostrans

[jojo]

Did you run the migration script more than one time? You can not comment anything in the migration script as it will lead at least to data loss.

[arestas]

YEap, Have run it a few times and always stops with this error.

[arestas]

YEap, Have run it a few times and always stops with this error.
Have made a few checks like permissions and database configuration and all is ok...

[jojo]

did you revert to original 4.0.x database before running again?

[arestas]

In my first upgrade try ive made v3 to v4 and v4 to v5. this upgrade failed. So ive decided to roll back. Have put the snapshot on the otrs vm and have restore the backup i have made from the otrs database.

After i understand what went wrong in the first upgrade (it were the packages versions) ive decided to upgrade the OTRS platform again.
The upgrade from V3 to V4 went well but the upgrade from v4 to v5 is returning the reported error. Notice that this error didn't happen on the first upgrade from v4 to v5.
Because upgrade from v4 to v5 has failed i have installed just the v4 and that the current production version.

So what i am thinking is that the V5 adds new columns to the db. when running the upgrade script to v5 it returns the reported error because the field that script is trying to create already exists.
If this is what is happening i could comment this lines and skip step 7.

Could really use some help here

[arestas]

This error still happening when i try to upgrade to V5.

Can anyone help me with this?

[arestas]

Well, Solved it.
This happens because the table already have the record.

i had 'Old Ticket new note notification' and Old Ticket new note notification ( Duplicate Name ) rows in the table.
Ive deleted and have rerun the upgrade script.

This solved my problem.

Regards