Datenbank-Upgrade von 7.0.19 auf 7.1.2 schlägt fehl

Hilfe zu Znuny Problemen aller Art
Post Reply
oSIRus
Znuny newbie
Posts: 37
Joined: 28 Aug 2013, 16:55
Znuny Version: 7.1.6
Real Name: Jörg

Datenbank-Upgrade von 7.0.19 auf 7.1.2 schlägt fehl

Post by oSIRus »

Hallo zusammen,

wollte gerade von Znuny 7.0.19 auf 7.1.1 upgraden, aber leider schlägt das Datenbank-Upgrade fehl. Jemand eine Idee wo hier das Problem liegen könnte? Siehe Bild in der Anlage.

Danke!
oSIRus
You do not have the required permissions to view the files attached to this post.
Last edited by oSIRus on 25 Jul 2024, 22:42, edited 1 time in total.
oSIRus
Znuny newbie
Posts: 37
Joined: 28 Aug 2013, 16:55
Znuny Version: 7.1.6
Real Name: Jörg

Re: Datenbank-Upgrade von 7.0.19 auf 7.1.1 schlägt fehl

Post by oSIRus »

Fixed it with instructions on this page: https://stackoverflow.com/questions/700 ... ne-command
root
Administrator
Posts: 4250
Joined: 18 Dec 2007, 12:23
Znuny Version: Znuny and Znuny LTS
Real Name: Roy Kaldung
Company: Znuny
Contact:

Re: Datenbank-Upgrade von 7.0.19 auf 7.1.1 schlägt fehl

Post by root »

Hi,

What is your database version?

- Roy
Znuny and Znuny LTS running on CentOS / RHEL / Debian / SLES / MySQL / PostgreSQL / Oracle / OpenLDAP / Active Directory / SSO

Use a test system - always.

Do you need professional services? Check out https://www.znuny.com/

Do you want to contribute or want to know where it goes ?
oSIRus
Znuny newbie
Posts: 37
Joined: 28 Aug 2013, 16:55
Znuny Version: 7.1.6
Real Name: Jörg

Re: Datenbank-Upgrade von 7.0.19 auf 7.1.1 schlägt fehl

Post by oSIRus »

It's 10.11.6-MariaDB
root
Administrator
Posts: 4250
Joined: 18 Dec 2007, 12:23
Znuny Version: Znuny and Znuny LTS
Real Name: Roy Kaldung
Company: Znuny
Contact:

Re: Datenbank-Upgrade von 7.0.19 auf 7.1.1 schlägt fehl

Post by root »

oSIRus wrote: 25 Jul 2024, 21:11 It's 10.11.6-MariaDB
Thank you. We will try to reproduce this and adjust the migration script if needed. I'm just wondering because dynamic is the default row format. Have you changed this setting?
What is the result of this query?
show variables like 'innodb_default_row_format';

- Roy
Znuny and Znuny LTS running on CentOS / RHEL / Debian / SLES / MySQL / PostgreSQL / Oracle / OpenLDAP / Active Directory / SSO

Use a test system - always.

Do you need professional services? Check out https://www.znuny.com/

Do you want to contribute or want to know where it goes ?
oSIRus
Znuny newbie
Posts: 37
Joined: 28 Aug 2013, 16:55
Znuny Version: 7.1.6
Real Name: Jörg

Re: Datenbank-Upgrade von 7.0.19 auf 7.1.1 schlägt fehl

Post by oSIRus »

Yes I have changed this setting for every table like this:

Code: Select all

ALTER TABLE `otrs`.`queue_standard_template` ROW_FORMAT=DYNAMIC;        
ALTER TABLE `otrs`.`ticket_number_counter` ROW_FORMAT=DYNAMIC;          
ALTER TABLE `otrs`.`smime_signer_cert_relations` ROW_FORMAT=DYNAMIC;    
ALTER TABLE `otrs`.`ticket_lock_type` ROW_FORMAT=DYNAMIC;               
ALTER TABLE `otrs`.`queue` ROW_FORMAT=DYNAMIC;                          
ALTER TABLE `otrs`.`sysconfig_deployment_lock` ROW_FORMAT=DYNAMIC;      
ALTER TABLE `otrs`.`signature` ROW_FORMAT=DYNAMIC;                      
ALTER TABLE `otrs`.`valid` ROW_FORMAT=DYNAMIC;                          
ALTER TABLE `otrs`.`gi_debugger_entry` ROW_FORMAT=DYNAMIC;              
ALTER TABLE `otrs`.`sessions` ROW_FORMAT=DYNAMIC;                       
ALTER TABLE `otrs`.`mail_queue` ROW_FORMAT=DYNAMIC;                     
ALTER TABLE `otrs`.`ticket` ROW_FORMAT=DYNAMIC;                         
ALTER TABLE `otrs`.`sysconfig_deployment` ROW_FORMAT=DYNAMIC;           
ALTER TABLE `otrs`.`article_search_index` ROW_FORMAT=DYNAMIC;           
ALTER TABLE `otrs`.`sysconfig_default` ROW_FORMAT=DYNAMIC;              
ALTER TABLE `otrs`.`article_data_mime_plain` ROW_FORMAT=DYNAMIC;        
ALTER TABLE `otrs`.`dynamic_field_obj_id_name` ROW_FORMAT=DYNAMIC;      
ALTER TABLE `otrs`.`service_preferences` ROW_FORMAT=DYNAMIC;            
ALTER TABLE `otrs`.`calendar_appointment` ROW_FORMAT=DYNAMIC;           
ALTER TABLE `otrs`.`notification_event_item` ROW_FORMAT=DYNAMIC;        
ALTER TABLE `otrs`.`communication_channel` ROW_FORMAT=DYNAMIC;          
ALTER TABLE `otrs`.`pm_entity_sync` ROW_FORMAT=DYNAMIC;                 
ALTER TABLE `otrs`.`ticket_loop_protection` ROW_FORMAT=DYNAMIC;         
ALTER TABLE `otrs`.`virtual_fs_preferences` ROW_FORMAT=DYNAMIC;         
ALTER TABLE `otrs`.`notification_event` ROW_FORMAT=DYNAMIC;             
ALTER TABLE `otrs`.`standard_attachment` ROW_FORMAT=DYNAMIC;            
ALTER TABLE `otrs`.`link_relation` ROW_FORMAT=DYNAMIC;                  
ALTER TABLE `otrs`.`gi_webservice_config` ROW_FORMAT=DYNAMIC;           
ALTER TABLE `otrs`.`customer_preferences` ROW_FORMAT=DYNAMIC;           
ALTER TABLE `otrs`.`postmaster_filter` ROW_FORMAT=DYNAMIC;              
ALTER TABLE `otrs`.`system_address` ROW_FORMAT=DYNAMIC;                 
ALTER TABLE `otrs`.`gi_debugger_entry_content` ROW_FORMAT=DYNAMIC;      
ALTER TABLE `otrs`.`communication_log` ROW_FORMAT=DYNAMIC;              
ALTER TABLE `otrs`.`queue_preferences` ROW_FORMAT=DYNAMIC;              
ALTER TABLE `otrs`.`ticket_flag` ROW_FORMAT=DYNAMIC;                    
ALTER TABLE `otrs`.`sysconfig_default_version` ROW_FORMAT=DYNAMIC;      
ALTER TABLE `otrs`.`service_customer_user` ROW_FORMAT=DYNAMIC;          
ALTER TABLE `otrs`.`pm_activity` ROW_FORMAT=DYNAMIC;                    
ALTER TABLE `otrs`.`ticket_lock_index` ROW_FORMAT=DYNAMIC;              
ALTER TABLE `otrs`.`package_repository` ROW_FORMAT=DYNAMIC;             
ALTER TABLE `otrs`.`roles` ROW_FORMAT=DYNAMIC;                          
ALTER TABLE `otrs`.`sysconfig_modified` ROW_FORMAT=DYNAMIC;             
ALTER TABLE `otrs`.`pm_process` ROW_FORMAT=DYNAMIC;                     
ALTER TABLE `otrs`.`article_data_otrs_chat` ROW_FORMAT=DYNAMIC;         
ALTER TABLE `otrs`.`dynamic_field_value` ROW_FORMAT=DYNAMIC;            
ALTER TABLE `otrs`.`article` ROW_FORMAT=DYNAMIC;                        
ALTER TABLE `otrs`.`link_object` ROW_FORMAT=DYNAMIC;                    
ALTER TABLE `otrs`.`personal_queues` ROW_FORMAT=DYNAMIC;                
ALTER TABLE `otrs`.`ticket_type` ROW_FORMAT=DYNAMIC;                    
ALTER TABLE `otrs`.`auto_response_type` ROW_FORMAT=DYNAMIC;             
ALTER TABLE `otrs`.`gi_webservice_config_history` ROW_FORMAT=DYNAMIC;   
ALTER TABLE `otrs`.`pm_transition_action` ROW_FORMAT=DYNAMIC;           
ALTER TABLE `otrs`.`link_state` ROW_FORMAT=DYNAMIC;                     
ALTER TABLE `otrs`.`scheduler_task` ROW_FORMAT=DYNAMIC;                 
ALTER TABLE `otrs`.`ticket_history_type` ROW_FORMAT=DYNAMIC;            
ALTER TABLE `otrs`.`article_data_mime_send_error` ROW_FORMAT=DYNAMIC;   
ALTER TABLE `otrs`.`acl_sync` ROW_FORMAT=DYNAMIC;                       
ALTER TABLE `otrs`.`xml_storage` ROW_FORMAT=DYNAMIC;                    
ALTER TABLE `otrs`.`web_upload_cache` ROW_FORMAT=DYNAMIC;               
ALTER TABLE `otrs`.`acl` ROW_FORMAT=DYNAMIC;                            
ALTER TABLE `otrs`.`sla_preferences` ROW_FORMAT=DYNAMIC;                
ALTER TABLE `otrs`.`calendar_appointment_ticket` ROW_FORMAT=DYNAMIC;    
ALTER TABLE `otrs`.`process_id` ROW_FORMAT=DYNAMIC;                     
ALTER TABLE `otrs`.`pm_transition` ROW_FORMAT=DYNAMIC;                  
ALTER TABLE `otrs`.`group_user` ROW_FORMAT=DYNAMIC;                     
ALTER TABLE `otrs`.`group_customer_user` ROW_FORMAT=DYNAMIC;            
ALTER TABLE `otrs`.`calendar` ROW_FORMAT=DYNAMIC;                       
ALTER TABLE `otrs`.`system_data` ROW_FORMAT=DYNAMIC;                    
ALTER TABLE `otrs`.`communication_log_obj_lookup` ROW_FORMAT=DYNAMIC;   
ALTER TABLE `otrs`.`group_customer` ROW_FORMAT=DYNAMIC;                 
ALTER TABLE `otrs`.`permission_groups` ROW_FORMAT=DYNAMIC;              
ALTER TABLE `otrs`.`pm_activity_dialog` ROW_FORMAT=DYNAMIC;             
ALTER TABLE `otrs`.`link_type` ROW_FORMAT=DYNAMIC;                      
ALTER TABLE `otrs`.`salutation` ROW_FORMAT=DYNAMIC;                     
ALTER TABLE `otrs`.`communication_log_object_entry` ROW_FORMAT=DYNAMIC; 
ALTER TABLE `otrs`.`customer_company` ROW_FORMAT=DYNAMIC;               
ALTER TABLE `otrs`.`queue_auto_response` ROW_FORMAT=DYNAMIC;            
ALTER TABLE `otrs`.`search_profile` ROW_FORMAT=DYNAMIC;                 
ALTER TABLE `otrs`.`virtual_fs` ROW_FORMAT=DYNAMIC;                     
ALTER TABLE `otrs`.`article_data_mime` ROW_FORMAT=DYNAMIC;              
ALTER TABLE `otrs`.`personal_services` ROW_FORMAT=DYNAMIC;              
ALTER TABLE `otrs`.`standard_template_attachment` ROW_FORMAT=DYNAMIC;   
ALTER TABLE `otrs`.`auto_response` ROW_FORMAT=DYNAMIC;                  
ALTER TABLE `otrs`.`article_data_mime_attachment` ROW_FORMAT=DYNAMIC;   
ALTER TABLE `otrs`.`customer_user` ROW_FORMAT=DYNAMIC;                  
ALTER TABLE `otrs`.`form_draft` ROW_FORMAT=DYNAMIC;                     
ALTER TABLE `otrs`.`article_sender_type` ROW_FORMAT=DYNAMIC;            
ALTER TABLE `otrs`.`system_maintenance` ROW_FORMAT=DYNAMIC;             
ALTER TABLE `otrs`.`ticket_state_type` ROW_FORMAT=DYNAMIC;              
ALTER TABLE `otrs`.`scheduler_recurrent_task` ROW_FORMAT=DYNAMIC;       
ALTER TABLE `otrs`.`scheduler_future_task` ROW_FORMAT=DYNAMIC;          
ALTER TABLE `otrs`.`group_role` ROW_FORMAT=DYNAMIC;                     
ALTER TABLE `otrs`.`follow_up_possible` ROW_FORMAT=DYNAMIC;             
ALTER TABLE `otrs`.`ticket_watcher` ROW_FORMAT=DYNAMIC;                 
ALTER TABLE `otrs`.`service_sla` ROW_FORMAT=DYNAMIC;                    
ALTER TABLE `otrs`.`virtual_fs_db` ROW_FORMAT=DYNAMIC;                  
ALTER TABLE `otrs`.`communication_log_object` ROW_FORMAT=DYNAMIC;       
ALTER TABLE `otrs`.`role_user` ROW_FORMAT=DYNAMIC;                      
ALTER TABLE `otrs`.`user_preferences` ROW_FORMAT=DYNAMIC;               
ALTER TABLE `otrs`.`sysconfig_modified_version` ROW_FORMAT=DYNAMIC;
After that the migration script worked flawlessly.

Maybe the server is older than this was a default before... I changed it with:

Code: Select all

SET GLOBAL innodb_default_row_format=DYNAMIC;
oSIRus
Znuny newbie
Posts: 37
Joined: 28 Aug 2013, 16:55
Znuny Version: 7.1.6
Real Name: Jörg

Re: Datenbank-Upgrade von 7.0.19 auf 7.1.2 schlägt fehl

Post by oSIRus »

Ebenso sorry, dass ich wieder ins Englische verfalle im deutschen Forum. Aber habe gerade noch auf Github bzgl. des neuen Dark Theme gepostet und dann kommt man schnell durcheinander.
Post Reply