Fehler bei Update 3.2.5 -> 3.2.10

[skrueger]

Hi !

beim Update auf 3.2.10 kommt beim Befehl:
DBUpdate-to-3.2.mysql.sql | mysql -p -f -u root otrs

diese Meldungen:

ERROR 1091 (42000) at line 7: Can't DROP 'group_read'; check that column/key exists
ERROR 1091 (42000) at line 11: Can't DROP 'group_write'; check that column/key exists
ERROR 1091 (42000) at line 15: Can't DROP 'other_read'; check that column/key exists
ERROR 1091 (42000) at line 19: Can't DROP 'other_write'; check that column/key exists
ERROR 1091 (42000) at line 20: Can't DROP 'ticket_answered'; check that column/key exists
ERROR 1091 (42000) at line 24: Can't DROP 'ticket_answered'; check that column/key exists
ERROR 1091 (42000) at line 29: Can't DROP 'group_id'; check that column/key exists
ERROR 1050 (42S01) at line 34: Table 'pm_process' already exists
ERROR 1050 (42S01) at line 51: Table 'pm_activity' already exists
ERROR 1050 (42S01) at line 66: Table 'pm_activity_dialog' already exists
ERROR 1050 (42S01) at line 81: Table 'pm_transition' already exists
ERROR 1050 (42S01) at line 96: Table 'pm_transition_action' already exists
ERROR 1050 (42S01) at line 111: Table 'pm_entity' already exists
ERROR 1050 (42S01) at line 118: Table 'pm_entity_sync' already exists
ERROR 1060 (42S21) at line 129: Duplicate column name 'internal_field'
ERROR 1062 (23000) at line 135: Duplicate entry 'ProcessManagementProcessID' for key 'dynamic_field_name'
ERROR 1062 (23000) at line 141: Duplicate entry 'ProcessManagementActivityID' for key 'dynamic_field_name

Fährt man dann trotzdem mit dem Update fort, erscheint beim "DBUpdate-to-3.2.pl" folgende Fehler:

Step 1 of 10: Refresh configuration cache...
If you see warnings about 'Subroutine Load redefined', that's fine, no need to worry!
Subroutine Load redefined at /opt/otrs/Kernel/Config/Files/ZZZAuto.pm line 7.
done.

Step 2 of 10: Check framework version... done.
Step 3 of 10: Cleanup UserPreferences... done.
Step 4 of 10: Updating toolbar configuration... done.
Step 5 of 10: Updating AgentTicketZoom window configuration... done.
Step 6 of 10: Dropping obsolete columns from article_search... Check if columns exist.
Columns are not present, no need to drop them.
done.

Step 7 of 10: Dropping unused indexes on article_flag... SET @FKExists := (SELECT COUNT(*) FROM information_schema.table_constraints WHERE table_schema = DATABASE() AND table_name = 'article_flag' AND constraint_name = 'FK_article_flag_article_id_id')
OK
SET @FKSQLStatement := IF( @FKExists > 0, 'ALTER TABLE article_flag DROP FOREIGN KEY FK_article_flag_article_id_id', 'SELECT ''INFO: Foreign key constraint FK_article_flag_article_id_id does not exist, skipping.''' )
OK
PREPARE FKStatement FROM @FKSQLStatement
OK
EXECUTE FKStatement
OK
SET @FKExists := (SELECT COUNT(*) FROM information_schema.table_constraints WHERE table_schema = DATABASE() AND table_name = 'article_flag' AND constraint_name = 'FK_article_flag_create_by_id')
OK
SET @FKSQLStatement := IF( @FKExists > 0, 'ALTER TABLE article_flag DROP FOREIGN KEY FK_article_flag_create_by_id', 'SELECT ''INFO: Foreign key constraint FK_article_flag_create_by_id does not exist, skipping.''' )
OK
PREPARE FKStatement FROM @FKSQLStatement
OK
EXECUTE FKStatement
OK
DROP INDEX article_flag_create_by ON article_flag
DBD::mysql::db do failed: Can't DROP 'article_flag_create_by'; check that column/key exists at /opt/otrs-3.2.10/Kernel/System/DB.pm line 475.
ERROR: OTRS-DBUpdate-to-3.2-68 Perl: 5.10.1 OS: linux Time: Thu Sep 12 15:08:22 2013

Message: Can't DROP 'article_flag_create_by'; check that column/key exists, SQL: 'DROP INDEX article_flag_create_by ON article_flag'

Traceback (2497):
Module: main::_DropArticleFlagIndexes (unknown version) Line: 488
Module: ./DBUpdate-to-3.2.pl (unknown version) Line: 109

Index was not present
DROP INDEX article_flag_article_id_article_key ON article_flag
DBD::mysql::db do failed: Can't DROP 'article_flag_article_id_article_key'; check that column/key exists at /opt/otrs-3.2.10/Kernel/System/DB.pm line 475.
ERROR: OTRS-DBUpdate-to-3.2-68 Perl: 5.10.1 OS: linux Time: Thu Sep 12 15:08:22 2013

Message: Can't DROP 'article_flag_article_id_article_key'; check that column/key exists, SQL: 'DROP INDEX article_flag_article_id_article_key ON article_flag'

Traceback (2497):
Module: main::_DropArticleFlagIndexes (unknown version) Line: 488
Module: ./DBUpdate-to-3.2.pl (unknown version) Line: 109

Index was not present
ALTER TABLE article_flag ADD CONSTRAINT FK_article_flag_article_id_id FOREIGN KEY (article_id) REFERENCES article (id)
OK
ALTER TABLE article_flag ADD CONSTRAINT FK_article_flag_create_by_id FOREIGN KEY (create_by) REFERENCES users (id)
OK

Step 8 of 10: Migration cache backend configuration... done.
Step 9 of 10: Clean up the cache... done.
Step 10 of 10: Refresh configuration cache another time...
If you see warnings about 'Subroutine Load redefined', that's fine, no need to worry!
Subroutine Load redefined at /opt/otrs/Kernel/Config/Files/ZZZAAuto.pm line 7.
Subroutine Load redefined at /opt/otrs/Kernel/Config/Files/ZZZAuto.pm line 7.
done.
Migration completed!


Hat jemand dazu vielleicht eine Idee ?
Jeder Tip ist gern genommen.

Stefanie

[Wolfgangf]

du musst das upgrade für jede Version machen
3.2.5 -> 3.2.6
3.2.6 -> 3.2.7
...

[skrueger]

echt
In der Vergangenheit hatte wir auch schonmal "grössere" Sprünge innerhalb der Version gemacht, ohne Probleme.
Hm, ok, werden wir mal testen.

Danke

[wurzel]

Hi,

nein, Minor Upgrades können übersprungen werden.

was sagt denn die Ausgabe otrs.CheckDB.pl bevor Du migrierst?

Flo

[skrueger]

der check war ok, (ohne Fehler).
Aber wir haben uns die Meldungen nochmal angesehen und haben sie als "nicht kritisch" bewertet

[wurzel]

Hi,

ich hätte sie jetzt auch als "nicht kritisch" betrachtet. Was zu droppen was schon weg ist, oder was createn was schon da ist...

aber das mit den Indexes musst Du ggf. nochmal anschauen. Evtl. hast Du (aus vorherigen Migrationen?) das bekannte MyISAM/InnoDB
Thema, welches hier angemeckert wird?

Also die Storage Enginge faslch?

Flo

[skrueger]

Leider haben wir nach dem Update folgendes Problem, beim Erstellen von Anworten aus einem Ticket.
Erstellt wird die Antwort trotzdem!

Es kommt die folgende Meldung:

Backend ERROR: OTRS-CGI-68 Perl: 5.10.1 OS: linux Time: Mon Sep 16 08:41:25 2013 Message: Table './otrs/article_plain' is marked as crashed and last (automatic?) repair failed, SQL: 'INSERT INTO article_plain (article_id, body, create_time, create_by, change_time, change_by) VALUES (?, ?, '2013-09-16 08:41:25' , ?, '2013-09-16 08:41:25' , ?)'
RemoteAddress: 10.98.38.46 RequestURI: /otrs/index.pl Traceback (6160): Module: Kernel::System::Ticket::ArticleStorageDB::ArticleWritePlain (OTRS 3.2.10) Line: 214 Module: Kernel::System::Ticket::Article::ArticleSend (OTRS 3.2.10) Line: 2081 Module: Kernel::Modules::AgentTicketCompose::Run (OTRS 3.2.10) Line: 765 Module: Kernel::System::Web::InterfaceAgent::Run (OTRS 3.2.10) Line: 863 Module:ModPerl::ROOT::ModPerl::Registry::opt_otrs_bin_cgi_2dbin_index_2epl::handler (unknown version) Line: 41 Module: (eval) (v1.99) Line: 204 Module: ModPerl::RegistryCooker::run (v1.99) Line: 204 Module: ModPerl::RegistryCooker::default_handler (v1.99) Line: 170 Module: ModPerl::Registry::handler (v1.99) Line: 31

[KlausNehrer]

https://ixquick.com/do/search?q=mysql+t ... &l=deutsch