upgrade from otrs 3.3.0 to 3.3.1 and up gives dbase error

[alfl]

I am upgrading my running 3.2.2 otrs to newer version of 3.3 by using small steps. When upgrading from version 3.2.4 to version 3.3.0rc1 al seems to be well and upgrades incl. database upgrades run smooth without errors.

When upgrading from version 3.3.0rc1 to version 3.3.1 i receive errors during database upgrade as shown bellow

Everything seems to be working after these error messages, but can i ignore the errors shown ?

I checked if mysql database needs to be changed to InnoDB but this config seems to be correct and i don't have tables in the database which needs to be converted .....

-------

otrs@helpdesk2:/opt/otrs$ scripts/DBUpdate-to-3.3.pl

Migration started...

Step 1 of 13: Refresh configuration cache...
If you see warnings about 'Subroutine Load redefined', that's fine, no need to worry!
done.

Step 2 of 13: Check framework version... done.

Step 3 of 13: Generate MessageID md5sums... done.

Step 4 of 13: Migrate old settings... done.

Step 5 of 13: Migrate OTRSExternalTicketNumberRecognition... done.

Step 6 of 13: Checking Standard Template table columns...
Check if 'template_type' columns exists.
'template_type' column exists, set new default value.
ALTER TABLE standard_template CHANGE template_type template_type VARCHAR (100) NULL
ALTER TABLE standard_template ALTER template_type DROP DEFAULT
UPDATE standard_template SET template_type = 'Answer' WHERE template_type IS NULL
ALTER TABLE standard_template CHANGE template_type template_type VARCHAR (100) DEFAULT 'Answer' NOT NULL
done.

Step 7 of 13: Updating Queue Standard Template relations table...
Cleaning queue_standard_template table
Creating new Foreign Keys for queue_standard_template table

--- Note: ---
If you have already run this script before then the Foreign Keys are already set and you might see errors regarding 'duplicate key' or 'constrain already exists', that's fine, no need to worry!
---

ALTER TABLE queue_standard_template ADD CONSTRAINT FK_queue_standard_template_standard_template_id_id FOREIGN KEY (standard_template_id) REFERENCES standard_template (id)
[Mon Jun 8 23:36:41 2015] DBUpdate-to-3.3.pl: DBD::mysql::db do failed: Can't create table 'otrs.#sql-47e_32' (errno: 121) at /opt/otrs/Kernel/System/DB.pm line 495.
ERROR: OTRS-DBUpdate-to-3.3-10 Perl: 5.18.2 OS: linux Time: Mon Jun 8 23:36:41 2015

Message: Can't create table 'otrs.#sql-47e_32' (errno: 121), SQL: 'ALTER TABLE queue_standard_template ADD CONSTRAINT FK_queue_standard_template_standard_template_id_id FOREIGN KEY (standard_template_id) REFERENCES standard_template (id)'

Traceback (1776):
Module: main::_AddQueueStandardTemplateForeignKeys (unknown version) Line: 557
Module: scripts/DBUpdate-to-3.3.pl (unknown version) Line: 133

ERROR: OTRS-DBUpdate-to-3.3-10 Perl: 5.18.2 OS: linux Time: Mon Jun 8 23:36:41 2015

Message: Error during execution of 'ALTER TABLE queue_standard_template ADD CONSTRAINT FK_queue_standard_template_standard_template_id_id FOREIGN KEY (standard_template_id) REFERENCES standard_template (id)'!

Traceback (1776):
Module: main::_AddQueueStandardTemplateForeignKeys (unknown version) Line: 559
Module: scripts/DBUpdate-to-3.3.pl (unknown version) Line: 133

done.

Step 8 of 13: Migrate OTRSGenericStandardTemplates... done.

Step 9 of 13: Checking if ACL tables already exist... Check if ACL table exists.
ACL tables are present, no need to create them.
done.

Step 10 of 13: Uninstall Merged Feature Add-Ons... done.

Step 11 of 13: Delete the files that are not longer needed... done.

Step 12 of 13: Clean up the cache... done.

Step 13 of 13: Refresh configuration cache another time...
If you see warnings about 'Subroutine Load redefined', that's fine, no need to worry!
[Mon Jun 8 23:36:44 2015] DBUpdate-to-3.3.pl: Subroutine Load redefined at /opt/otrs/Kernel/Config/Files/ZZZAAuto.pm line 7.
done.

Migration completed!

--------------

[root]

Which storage engine do you use? MyISAM or InnoDB?
Why are you upgrading each minor version? You can go straight to the latest 3.3.

[alfl]

I use InnoDB on MySQL and if i follow the upgrade manual it says to do each upgrade step by step (or did i missed something as this takes a lot of time ? )

[crythias]

You do have to change the dB structure. There is a script to do that in the distribution.