Upgrading from 3.1.21 to 3.3.10
Hello everyone, We wanted to upgrade our 3.1.21 to 3.3.10. Any intermediate upgrades required first? Thanks //M
Hi, On 19.11.2014 12:14, Muhammad El-Sergani wrote:
Hello everyone,
We wanted to upgrade our 3.1.21 to 3.3.10. Any intermediate upgrades required first?
Yes, you have to upgrade to 3.2.latest first (where latest is 16 at the moment). - Renée -- Perl / OTRS development: http://perl-services.de OTRS AddOn repository: http://opar.perl-services.de
Thanks Renee.
Thanks
//M
Sent from my Galaxy Note
On Nov 19, 2014 1:19 PM, "Renee B"
Hi,
On 19.11.2014 12:14, Muhammad El-Sergani wrote:
Hello everyone,
We wanted to upgrade our 3.1.21 to 3.3.10. Any intermediate upgrades required first?
Yes, you have to upgrade to 3.2.latest first (where latest is 16 at the moment).
- Renée
-- Perl / OTRS development: http://perl-services.de OTRS AddOn repository: http://opar.perl-services.de
--------------------------------------------------------------------- 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
Hi,
We wanted to upgrade our 3.1.21 to 3.3.10. Any intermediate upgrades required first?
Yes, you have to upgrade to 3.2.latest first (where latest is 16 at the moment).
It is actually suffucient to apply the database upgrades in order. I upgrade from an old largely unmaintained Debian wheezy package to Debain jessie recently. I upgraded the package using apt, then grabbed the upgrade *.sql from the 3.2 package, applied that, and then applied the upgrade SQL from 3.3. You do not need to double-upgrade the whole installation. Cheers, Nik -- Dominik George Service & Wartung Telefon: +49 228 54881 319 Mobil: +49 178 54881 81 tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg
Hello.
Hi,
We wanted to upgrade our 3.1.21 to 3.3.10. Any intermediate upgrades required first?
Yes, you have to upgrade to 3.2.latest first (where latest is 16 at the moment).
It is actually suffucient to apply the database upgrades in order.
I upgrade from an old largely unmaintained Debian wheezy package to Debain jessie recently. I upgraded the package using apt, then grabbed the upgrade *.sql from the 3.2 package, applied that, and then applied the upgrade SQL from 3.3.
You do not need to double-upgrade the whole installation.
I¹m quite sure this is not correct. Probably it¹s not necessary to update all the files. But beside the SQL there are other pre- and post-DB scripts you should run. They are responsible for doing conversions (like the one from FreeText to DynamicFields with upgrade 3.0->3.1), as well as other important tasks (installing scheduler, Š). In short: to be sure, just do the complete upgrade path. Jan Dreyer IT Administrator ‹ Operations ‹ A-SCM-IT NMD Expert
On 24.11.14 14:03, Jan.Dreyer@bertelsmann.de wrote:
Hello.
Hi,
We wanted to upgrade our 3.1.21 to 3.3.10. Any intermediate upgrades required first?
Yes, you have to upgrade to 3.2.latest first (where latest is 16 at the moment).
It is actually suffucient to apply the database upgrades in order.
I upgrade from an old largely unmaintained Debian wheezy package to Debain jessie recently. I upgraded the package using apt, then grabbed the upgrade *.sql from the 3.2 package, applied that, and then applied the upgrade SQL from 3.3.
You do not need to double-upgrade the whole installation.
I¹m quite sure this is not correct. Probably it¹s not necessary to update all the files. But beside the SQL there are other pre- and post-DB scripts you should run. They are responsible for doing conversions (like the one from FreeText to DynamicFields with upgrade 3.0->3.1), as well as other important tasks (installing scheduler, Š). In short: to be sure, just do the complete upgrade path.
AFAIK this process /is/ correct. E.g. a "clean migration" to an other system would consist of * Do a clean install of the newest OTRS version * Transfer your settings files * Replace DB of fresh installation by the one from the old install * Run through all (!) required DB upgrade steps (3.1->3.2->3.3-> etc.) This also makes sure you don't drag along lots of outdated files with your installation. If that works, the update procedure described by Dominik George should work, too. The crucial point is that no matter how big the (file) upgrade step is, the database upgrade procedure /always/ has to be followed to the point. AFAIK there are no pre- or post-DB scripts to consider. Everything is done by the main database upgrade script. E.g. in the OTRS 3.1 manual it says "A database update script will transform historic FreeText fields and related configuration settings into the new structure". HTH Frank -- Frank Thommen - Structures IT Management and Support - EMBL Heidelberg frank.thommen@embl-heidelberg.de - +49 6221 387 8353
I agree. And the DBUpdate-to-x.pl scripts, that are definitely needed, should always run on their corresponding code base. Best regards, Martin Am 24.11.14 um 14:03 schrieb Jan.Dreyer@bertelsmann.de:
Hello.
Hi,
We wanted to upgrade our 3.1.21 to 3.3.10. Any intermediate upgrades required first?
Yes, you have to upgrade to 3.2.latest first (where latest is 16 at the moment).
It is actually suffucient to apply the database upgrades in order.
I upgrade from an old largely unmaintained Debian wheezy package to Debain jessie recently. I upgraded the package using apt, then grabbed the upgrade *.sql from the 3.2 package, applied that, and then applied the upgrade SQL from 3.3.
You do not need to double-upgrade the whole installation.
I¹m quite sure this is not correct. Probably it¹s not necessary to update all the files. But beside the SQL there are other pre- and post-DB scripts you should run. They are responsible for doing conversions (like the one from FreeText to DynamicFields with upgrade 3.0->3.1), as well as other important tasks (installing scheduler, Š). In short: to be sure, just do the complete upgrade path.
Jan Dreyer IT Administrator ‹ Operations ‹ A-SCM-IT NMD Expert
--------------------------------------------------------------------- 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
-- Martin Gruner Senior Developer R&D OTRS AG Bahnhofplatz 1a 94315 Straubing T: +49 (0)6172 681988 0 F: +49 (0)9421 56818 18 I: www.otrs.com/ Geschäftssitz: Bad Homburg, Amtsgericht: Bad Homburg, HRB 10751, USt-Nr.: DE256610065 Aufsichtsratsvorsitzender: Burchard Steinbild, Vorstand: André Mindermann (Vorsitzender), Christopher Kuhn, Sabine Riedel Service Desk-Professionalität auf höchstem Niveau – OTRS 3.4 wird zu OTRS 4! – Jetzt Beta-Version testen! http://www.otrs.com/otrs-4-beta-mit-ultra-flachem-design-und-uberarbeitetem-...
participants (6)
-
Dominik George -
Frank Thommen -
Jan.Dreyer＠bertelsmann.de -
Martin Gruner -
Muhammad El-Sergani -
Renee B