Migrate OTRS from 3.1.1 to 3.1.21

Moderator: crythias

Locked
ivicav
Znuny newbie
Posts: 21
Joined: 12 Jun 2012, 14:16
Znuny Version: 5.0.1
Real Name: Ivica Vujovic
Company: BELIT

Migrate OTRS from 3.1.1 to 3.1.21

Post by ivicav »

Hi everybody!

I have problem upgrading OTRS from 3.1.1 to 3.2.x version on Windows. Since instalation is changed and Perl has some problems with IIS I just cannot force installation to work with AD as it should. So I decided to migrate platform from Windows to Linux (Centos 6.5).

First step is to upgrade mysql DB for OTRS version 3.1.1 to version 3.1.21 and there I hit the wall. When I tried to complete update script I got an errors:

Code: Select all

ERROR 1050 (42S01) at line 28: Table 'gi_webservice_config' already exists
ERROR 1050 (42S01) at line 45: Table 'gi_webservice_config_history' already exists
ERROR 1050 (42S01) at line 60: Table 'scheduler_task_list' already exists
ERROR 1050 (42S01) at line 73: Table 'gi_debugger_entry' already exists
ERROR 1050 (42S01) at line 87: Table 'gi_debugger_entry_content' already exists
ERROR 1050 (42S01) at line 101: Table 'gi_object_lock_state' already exists
ERROR 1062 (23000) at line 115: Duplicate entry 'EscalationSolutionTimeStop' for key 'ticket_history_type_name'
ERROR 1062 (23000) at line 121: Duplicate entry 'EscalationResponseTimeStart' for key 'ticket_history_type_name'
ERROR 1062 (23000) at line 127: Duplicate entry 'EscalationUpdateTimeStart' for key 'ticket_history_type_name'
ERROR 1062 (23000) at line 133: Duplicate entry 'EscalationSolutionTimeStart' for key 'ticket_history_type_name'
ERROR 1062 (23000) at line 139: Duplicate entry 'EscalationResponseTimeNotifyBefore' for key 'ticket_history_type_name'
ERROR 1062 (23000) at line 145: Duplicate entry 'EscalationUpdateTimeNotifyBefore' for key 'ticket_history_type_name'
ERROR 1062 (23000) at line 151: Duplicate entry 'EscalationSolutionTimeNotifyBefore' for key 'ticket_history_type_name'
ERROR 1062 (23000) at line 157: Duplicate entry 'EscalationResponseTimeStop' for key 'ticket_history_type_name'
ERROR 1062 (23000) at line 163: Duplicate entry 'EscalationUpdateTimeStop' for key 'ticket_history_type_name'
ERROR 1050 (42S01) at line 169: Table 'smime_signer_cert_relations' already exists
ERROR 1060 (42S21) at line 184: Duplicate column name 'process_change'
ERROR 1050 (42S01) at line 190: Table 'dynamic_field_value' already exists
ERROR 1050 (42S01) at line 205: Table 'dynamic_field' already exists
ERROR 1060 (42S21) at line 224: Duplicate column name 'imap_folder'
Where is mistake? What I did wrong?
crythias
Moderator
Posts: 10170
Joined: 04 May 2010, 18:38
Znuny Version: 5.0.x
Location: SouthWest Florida, USA
Contact:

Re: Migrate OTRS from 3.1.1 to 3.1.21

Post by crythias »

it's a 3.1.x -> 3.1.x so it should essentially be use the same database and done. (check UPGRADING for more information on steps to skip).
OTRS 6.0.x (private/testing/public) on Linux with MySQL database.
Please edit your signature to include your OTRS version, Operating System, and database type.
Click Subscribe Topic below to get notifications. Consider amending your topic title to include [SOLVED] if it is so.
Need help? Before you ask
ivicav
Znuny newbie
Posts: 21
Joined: 12 Jun 2012, 14:16
Znuny Version: 5.0.1
Real Name: Ivica Vujovic
Company: BELIT

Re: Migrate OTRS from 3.1.1 to 3.1.21

Post by ivicav »

As I understood there is no need for any alteration on database if I perform minor migration of OTRS version?

In UPGRADE section of manual it says:
Within a single minor version you can skip patch level releases if you want to upgrade. For instance you can upgrade directly from OTRS 3.1.1 to version 3.1.4. If you need to do such a "patch level upgrade", you should skip steps 9, 11 and 13-19.
And there in step 8 is suggested to perform db upgrade.

Is it proper to perform upgrade from version 3.1.1 to version 3.2.16 directly and later to 3.3.10?
reneeb
Znuny guru
Posts: 5018
Joined: 13 Mar 2011, 09:54
Znuny Version: 6.0.x
Real Name: Renée Bäcker
Company: Perl-Services.de
Contact:

Re: Migrate OTRS from 3.1.1 to 3.1.21

Post by reneeb »

ivicav wrote:Is it proper to perform upgrade from version 3.1.1 to version 3.2.16 directly and later to 3.3.10?
yes
Perl / Znuny development: http://perl-services.de
Free Znuny add ons from the community: http://opar.perl-services.de
Commercial add ons: http://feature-addons.de
Locked