Quantcast
Channel: Znuny Open Source Ticketsystem
Viewing all articles
Browse latest Browse all 310

Upgrade OTRS 5 to 6

$
0
0
I'm trying to update an OTRS5 to znuny 6.0.48. When I run the DBUpdate-to-6.pl script I get the following output:

Code:

 Migration started ... Checking requirements ...    Requirement check for: Check framework version ...    Requirement check for: Check required Perl version ...    Requirement check for: Check required database version ...    Requirement check for: Check database charset ...    Requirement check for: Check required Perl modules ...    Requirement check for: Check if database has been backed up ...        Did you backup the database? [Y]es/[N]o: y    Requirement check for: Migrate PostMaster pre-filters that execute system commands ...    Requirement check for: Migrate dashboard widgets that execute system commands ...    Requirement check for: Upgrade database structure ...    Requirement check for: Migrating time zone configuration ...    Requirement check for: Update calendar appointment future tasks ...    Requirement check for: Migrate GenericAgent jobs configuration ...    Requirement check for: Migrate TicketAppointment rules configuration ...    Requirement check for: Create entries in new article table ...    Requirement check for: Migrate ArticleType in ProcessManagement Data ...    Requirement check for: Migrate ArticleType in PostMaster filters ...    Requirement check for: Remove Generic Agent system commands ... Executing tasks ...    Step 1 of 49: Check framework version ...    Step 2 of 49: Check required Perl version ...    Step 3 of 49: Check required database version ...    Step 4 of 49: Check database charset ...    Step 5 of 49: Check required Perl modules ...    Step 6 of 49: Check installed CPAN modules for known vulnerabilities ...    Step 7 of 49: Check if database has been backed up ...    Step 8 of 49: Migrate PostMaster pre-filters that execute system commands ...    Step 9 of 49: Migrate dashboard widgets that execute system commands ...    Step 10 of 49: Upgrade database structure ...    Step 11 of 49: Migrate configuration ...    Step 12 of 49: Refresh configuration cache after migration of OTRS 5 settings ...    Step 13 of 49: Migrating ticket storage configuration ...    Step 14 of 49: Migrating article search index configuration ...    Step 15 of 49: Migrating ticket zoom customer information widget configuration ...    Step 16 of 49: Drop deprecated table gi_object_lock_state ...    Step 17 of 49: Migrate PossibleNextActions setting ...    Step 18 of 49: Migrate ZoomExpand setting ...    Step 19 of 49: Migrating time zone configuration ...    Step 20 of 49: Migrating modified settings ...    Step 21 of 49: Create appointment calendar tables ...    Step 22 of 49: Create ticket number counter tables ...    Step 23 of 49: Update calendar appointment future tasks ...    Step 24 of 49: Add basic appointment notification for reminders ...    Step 25 of 49: Create Form Draft tables ...    Step 26 of 49: Clean and drop group_user permission_value column ...    Step 27 of 49: Migrate GenericAgent jobs configuration ...    Step 28 of 49: Migrate TicketAppointment rules configuration ...    Step 29 of 49: Migrate Merged Ticket history name values ...    Step 30 of 49: Migrate ticket statistics ...    Step 31 of 49: Migrate ticket notifications ...    Step 32 of 49: Create entries in new article table ...    Step 33 of 49: Post changes on article related tables ...[Thu Feb 20 10:11:24 2025] DBUpdate-to-6.pl: DBD::mysql::db do failed: Cannot delete or update a parent row: a foreign key constraint fails at /opt/znuny-6.0.48/Kernel/System/DB.pm line 471.ERROR: OTRS-otrs.Console.pl-Dev::Code::CPANAudit-55 Perl: 5.34.0 OS: linux Time: Thu Feb 20 13:11:25 2025 Message: Cannot delete or update a parent row: a foreign key constraint fails, SQL: 'DROP TABLE IF EXISTS article_type' Traceback (803163):   Module: scripts::DBUpdateTo6::Base::ExecuteXMLDBString Line: 396   Module: scripts::DBUpdateTo6::Base::ExecuteXMLDBArray Line: 344   Module: scripts::DBUpdateTo6::PostArticleTableStructureChanges::_DropArticleTypeTable Line: 388   Module: scripts::DBUpdateTo6::PostArticleTableStructureChanges::Run Line: 68   Module: scripts::DBUpdateTo6::_ExecuteComponent Line: 156   Module: scripts::DBUpdateTo6::Run Line: 68   Module: scripts/DBUpdate-to-6.pl Line: 88ERROR: OTRS-otrs.Console.pl-Dev::Code::CPANAudit-55 Perl: 5.34.0 OS: linux Time: Thu Feb 20 13:11:25 2025 Message: Error during execution of 'DROP TABLE IF EXISTS article_type'! Traceback (803163):   Module: scripts::DBUpdateTo6::Base::ExecuteXMLDBString Line: 399   Module: scripts::DBUpdateTo6::Base::ExecuteXMLDBArray Line: 344   Module: scripts::DBUpdateTo6::PostArticleTableStructureChanges::_DropArticleTypeTable Line: 388   Module: scripts::DBUpdateTo6::PostArticleTableStructureChanges::Run Line: 68   Module: scripts::DBUpdateTo6::_ExecuteComponent Line: 156   Module: scripts::DBUpdateTo6::Run Line: 68   Module: scripts/DBUpdate-to-6.pl Line: 88 Not possible to complete migration, check previous messages for more information.
I verified that the ticket table still has references to the ticket_type table, so the database is correct in preventing DROP

Any help?

Statistics: Posted by artursampaio — 20 Feb 2025, 16:25 — Replies 5 — Views 365



Viewing all articles
Browse latest Browse all 310

Trending Articles