Re: [otrs] upgrading from otrs 2.0.4 to 3.0.11

You'll have to get the 2.3 tarball, then upgrade 2.0 > 2.1 > 2.2 > 2.3, then use the 2.4 tarball, then upgrade 2.3 > 2.4, then get the 3.0 tarball, and upgrade 2.4 > 3.0. The problem is that the migration scripts DBUpdate-to-2.3.pl and such (that you actually don't seem to be using) use the API and the API expects some fields to be present, which will not be there, because you have not yet completed the migration. -- Mike On Tue, Dec 6, 2011 at 16:24, Luca Domenella wrote:

Hi Michiel,****

** **

i’ve seen it and read it before to start, but its very unclear to me whats needed to do.****

** **

Anyway what happened to me looks different, I found that there is an extra mysql|postgres patch that add the 2 fields on the ticket table…****

I will apply that manually and also reapply the create index that failed manually L****

** **

Could you explain to me what is the workaround described in the link you sent me ? because I haven’t understood it L****

** **

Br,**

*Luca Domenella*****

T: +39 0698962316 E: luca.domenella@bwinparty.com****

*bwin Italia* Via Adolfo Ravà, 124 00142 Roma (RM)****

www.bwinparty.com****

****

This email and any attachments are confidential, and may be legally privileged and protected by copyright. If you are not the intended recipient dissemination or copying of this email is prohibited. If you have received this in error, please notify the sender by replying by email and then delete the email completely from your system.

Any views or opinions are solely those of the sender. This communication is not intended to form a binding contract unless expressly indicated to the contrary and properly authorised. Any actions taken on the basis of this email are at the recipient's own risk.****

** **

*From:* otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] *On Behalf Of *Michiel Beijen *Sent:* martedì 6 dicembre 2011 16:19

*To:* User questions and discussions about OTRS. *Subject:* Re: [otrs] upgrading from otrs 2.0.4 to 3.0.11****

** **

Hi, please note this warning in UPGRADING:

"Please note that if you upgrade from OTRS 2.2 or earlier, you have to take an extra step; please read http://bugs.otrs.org/show_bug.cgi?id=6798"

-- Mike****

On Tue, Dec 6, 2011 at 15:16, Luca Domenella wrote:****

Hi,

doing the database upgrade i've got the following error, maybe its normal but id like some info about it.

Performing the upgrade with the following steps: 1. cat DBUpdate-to-2.1.mysql.sql | mysql -p -f -u root otrs2 OK 2. cat DBUpdate-to-2.2.mysql.sql | mysql -p -f -u root otrs2 OK 3. cat DBUpdate-to-2.3.mysql.sql | mysql -p -f -u root otrs2 the errors iìve got are: ERROR 1072 (42000) at line 116: Key column 'escalation_response_time' doesn't exist in table ERROR 1072 (42000) at line 117: Key column 'escalation_solution_time' doesn't exist in table

There is not any field named 'escalation_response_time' and 'escalation_solution_time' in the table... is this an expected behavior ?

Br,****

Luca Domenella T: +39 0698962316 E: luca.domenella@bwinparty.com bwin Italia Via Adolfo Ravà, 124 00142 Roma (RM) www.bwinparty.com

This email and any attachments are confidential, and may be legally privileged and protected by copyright. If you are not the intended recipient dissemination or copying of this email is prohibited. If you have received this in error, please notify the sender by replying by email and then delete the email completely from your system.

Any views or opinions are solely those of the sender. This communication is not intended to form a binding contract unless expressly indicated to the contrary and properly authorised. Any actions taken on the basis of this email are at the recipient's own risk.

-----Original Message-----****

From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Luca Domenella Sent: martedì 6 dicembre 2011 14:20 To: User questions and discussions about OTRS. Subject: Re: [otrs] upgrading from otrs 2.0.4 to 3.0.11

Hi Ugo,

i will perform some tests, will let you know

thanks !

Luca Domenella T: +39 0698962316 E: luca.domenella@bwinparty.com bwin Italia Via Adolfo Ravà, 124 00142 Roma (RM) www.bwinparty.com

This email and any attachments are confidential, and may be legally privileged and protected by copyright. If you are not the intended recipient dissemination or copying of this email is prohibited. If you have received this in error, please notify the sender by replying by email and then delete the email completely from your system.

Any views or opinions are solely those of the sender. This communication is not intended to form a binding contract unless expressly indicated to the contrary and properly authorised. Any actions taken on the basis of this email are at the recipient's own risk.

-----Original Message----- From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Ugo Bellavance Sent: martedì 6 dicembre 2011 13:27 To: otrs@otrs.org Subject: Re: [otrs] upgrading from otrs 2.0.4 to 3.0.11

On 2011-12-06 06:41, Luca Domenella wrote:

...

Hi, i installed from source OTRS, the other stuff from rpm

Ok,

I installed via RPM (RHEL5), so YMMV, but here is what I did:

On the old server:

- Create a backup using /opt/otrs/scripts/backup.pl

On the new server:

- install perl-LDAP, mysql-server, httpd - copy the 2.3 rpm from old server - install the 2.3 rpm - edit my.cnf to set max_allowed_packet=512M and query_cache_size=48M (this is a server dedicated to otrs) - start mysql - create the mysql user - enable port 80, 443, 3306 in iptables - run the restore script (/opt/otrs/scripts/restore.pl -b /root/2011-07-04_05-11/ -d /opt/otrs/) - /opt/otrs/bin/otrs.RebuildConfig.pl - start httpd - est if index.pl is working - make sure all services come up at boot

Then, cycle through the upgrade operations

- install new dependencies perl-Net-DNS perl-XML-Parser - upgrade the rpm to 2.4 (rpm -Uvhf) - run the DBUpdate-to-2.4.mysql.sql script - get back to root and run /opt/otrs/bin/SetPermissions.sh /opt/otrs/ otrs apache apache apache - su - otrs - run the DBUpdate-do-2.4.pl script - test

done for 2.4, repeat for 3.0 (dependency: perl-TimeDate) Other stuff for 3.0

- Change the otrs DB and tables to UTF-8 charset - test - Go to the admin interface, support assessment and fix things there

Optional:

- Go to the - install perl-GD perl-GDGraph perl-GDTextUtil perl-JSON-XS perl-Apache-DBI

If something looks broken, try: /opt/otrs/bin/otrs.RebuildConfig.pl restart apache

Of course, you may have to adapt this procedure to your environment, but it should help.

--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs****

--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs****

** **

--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs