Hi, I'm testing 3.1.0.beta2. Therefore, I have to upgrade from v2.3. UPGRADING says (as usual): If you are running a lower version of OTRS you have to follow the upgrade path to 3.0 first (1.1->1.2->1.3->2.0->2.1->2.2->2.3->2.4->3.0->3.1 ...)! The problem: ALL the mysql-sql-upgrade- and post-scripts AND DBUpdate-to-3.1.pl are still present in ~otrs/scripts, but DBUpdate-to-2.4.pl and DBUpdate-to-3.0.pl are missing. I applied DBUpdate-to-2.4.mysql.sql and then tried DBUpdate-to-2.4.pl (from v3.0-sources), but this results in the following errors: ERROR: OTRS-DBUpdate-to-2.4-40 Perl: 5.10.0 OS: linux Time: Wed Dec 7 16:24:28 2011 Message: Unknown column 'state_notify' in 'field list', SQL: 'SELECT state_notify, move_notify, owner_notify FROM queue WHERE id = ?' Traceback (2148): Module: main::MigrateCustomerNotification (v1.13) Line: 184 Module: ./DBUpdate-to-2.4.pl (v1.13) Line: 101 DBD::mysql::st fetchrow_array failed: fetch() without execute() at /opt/otrs_v3.0/Kernel/System/DB.pm line 616. NOTICE: Migrate queue based customer notifications... done. And ideas? Is it necessary to install v3.0, upgrade from v2.3 to v3.0, and then upgrade to v3.1? That can't be true... Bye, Alex Richter+Frenzel GmbH + Co. KG Sitz: Wuerzburg Registergericht: Wuerzburg HRA 220 Geschaeftsfuehrer: Dr. Bernd-Michael Brunck, Wilhelm Schuster (Vorsitzender) Komplementaer: WUE Richter + Frenzel Verwaltung GmbH, Amtsgericht Augsburg, HRB 22447
Hi Alex, you need to install 2.4, then 3.0, then 3.1. The reason is that there are data upgrading scripts which sometimes use the API of OTRS for complex operations. These need a defined/consistent state of the code base. The fact that OTRS contained the old upgrading files was actually an error. Best regards, mg Am 07.12.11 16:28, schrieb Alexander Scholler:
Hi,
I'm testing 3.1.0.beta2. Therefore, I have to upgrade from v2.3. UPGRADING says (as usual): If you are running a lower version of OTRS you have to follow the upgrade path to 3.0 first (1.1->1.2->1.3->2.0->2.1->2.2->2.3->2.4->3.0->3.1 ...)! The problem: ALL the mysql-sql-upgrade- and post-scripts AND DBUpdate-to-3.1.pl are still present in ~otrs/scripts, but DBUpdate-to-2.4.pl and DBUpdate-to-3.0.pl are missing.
I applied DBUpdate-to-2.4.mysql.sql and then tried DBUpdate-to-2.4.pl (from v3.0-sources), but this results in the following errors:
ERROR: OTRS-DBUpdate-to-2.4-40 Perl: 5.10.0 OS: linux Time: Wed Dec 7 16:24:28 2011
Message: Unknown column 'state_notify' in 'field list', SQL: 'SELECT state_notify, move_notify, owner_notify FROM queue WHERE id = ?'
Traceback (2148): Module: main::MigrateCustomerNotification (v1.13) Line: 184 Module: ./DBUpdate-to-2.4.pl (v1.13) Line: 101
DBD::mysql::st fetchrow_array failed: fetch() without execute() at /opt/otrs_v3.0/Kernel/System/DB.pm line 616. NOTICE: Migrate queue based customer notifications... done. And ideas?
Is it necessary to install v3.0, upgrade from v2.3 to v3.0, and then upgrade to v3.1? That can't be true...
Bye, Alex
Richter+Frenzel GmbH + Co. KG Sitz: Wuerzburg Registergericht: Wuerzburg HRA 220 Geschaeftsfuehrer: Dr. Bernd-Michael Brunck, Wilhelm Schuster (Vorsitzender) Komplementaer: WUE Richter + Frenzel Verwaltung GmbH, Amtsgericht Augsburg, HRB 22447
--------------------------------------------------------------------- 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 Europaring 4 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 Schalten Sie hoch! Der Turbo für Ihr OTRS - Exklusive Feature Add-Ons: http://www.otrs.com/de/solutions/subscriptions/feature-add-ons/
participants (2)
-
Alexander Scholler -
Martin Gruner