Upgrade from 3.0.10 to 3.3.10

[mibrowni]

I just move my OTRS from one server and domain to another. The old version was 3.0.10 and the new version is 3.3.10. After installing 3.3.10 I did a mysqldump from the old to the new. I now can not login with root.localhost. I even tried creating an new user with the otrs.Adduser.pl and still can not login.

Any ideas?

[jojo]

you have to follow all upgrade steps from 3.0.x to 3.1.latest, to 3.2.latest, to 3.3.10

[mibrowni]

Can you point me to where I can find those?

Thanks

[jojo]

https://github.com/OTRS/otrs/blob/rel-3_1/UPGRADING
https://github.com/OTRS/otrs/blob/rel-3_2/UPGRADING.md
https://github.com/OTRS/otrs/blob/rel-3_3/UPGRADING.md

[mibrowni]

Ok, I download 3.1.1, 3.2.1, and 3.3.10.

Started with going from 3.0.10 to 3.1.1
SCHEMA UPDATE PART 1:
=====================
MySQL:
shell> cat scripts/DBUpdate-to-3.1.mysql.sql | mysql -p -f -u root otrs

Ran this with no problems from the otrs-3.1.1 directory

DATABASE MIGRATION SCRIPT
=========================

shell> scripts/DBUpdate-to-3.1.pl

When running this I get the following errors:

Step 8 of 22: Verify if article data was successfully migrated...
Verified 0 articles of 0 (with Free fields data).
done.

ERROR: OTRS-DBUpdate-to-3.1-67 Perl: 5.20.1 OS: linux Time: Tue Nov 25 08:17:24 2014

Message: Need Label!

Traceback (2997):
Module: Kernel::System::DynamicField::DynamicFieldUpdate (v1.50) Line: 378
Module: main::_MigrateFreeFieldsConfiguration (v1.71) Line: 1174
Module: scripts/DBUpdate-to-3.1.pl (v1.71) Line: 139

Could not migrate configuration for dynamic field: TicketFreeTime1 at scripts/DBUpdate-to-3.1.pl line 1182.

Any ideas?

Thanks
Michael

[jojo]

please use the latest versions of the minor releases.

3.1.21
3.2.16
3.3.10

[mibrowni]

Download 3.1.21 and when running scripts/DBUpdate-to-3.1.pl I get the following errors:

bash-3.2$ scripts/DBUpdate-to-3.1.pl
Can't load '/auto/uscmweb/perl5/lib/arch/auto/DBI/DBI.so' for module DBI: /auto/uscmweb/perl5/lib/arch/auto/DBI/DBI.so: undefined symbol: PL_phase at /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/DynaLoader.pm line 230.
at /auto/uscmweb/perl5/lib/arch/DBI.pm line 284
BEGIN failed--compilation aborted at /auto/uscmweb/perl5/lib/arch/DBI.pm line 284.
Compilation failed in require at /auto/uscmweb/wwwin-nacmci/otrs-3.1.21/otrs-3.1.21/Kernel/System/DB.pm line 17.
BEGIN failed--compilation aborted at /auto/uscmweb/wwwin-nacmci/otrs-3.1.21/otrs-3.1.21/Kernel/System/DB.pm line 17.
Compilation failed in require at scripts/DBUpdate-to-3.1.pl line 41.
BEGIN failed--compilation aborted at scripts/DBUpdate-to-3.1.pl line 41.

[mibrowni]

Is there a way to reset 3.3.10 so I can run the installer.pl again to create a blank dbase?

[mibrowni]

Ok was able to convert from 3.0.10 to 3.1.21 with out problems.

When going form 3.1.21 to 3.2.16 I got the following traceback when running scripts/DBUpdate-to-3.2.pl,however at the end it does say
Migration completed!

My question is can I ignore this?


DROP INDEX article_flag_create_by ON article_flag
DBD::mysql::db do failed: Can't DROP 'article_flag_create_by'; check that column/key exists at /auto/uscmweb/wwwin-nacmci/otrs-3.2.16/otrs-3.2.16/Kernel/System/DB.pm line 476.
ERROR: OTRS-DBUpdate-to-3.2-10 Perl: 5.20.1 OS: linux Time: Tue Nov 25 11:28:52 2014

Message: Can't DROP 'article_flag_create_by'; check that column/key exists, SQL: 'DROP INDEX article_flag_create_by ON article_flag'

Traceback (28747):
Module: main::_DropArticleFlagIndexes (unknown version) Line: 486
Module: scripts/DBUpdate-to-3.2.pl (unknown version) Line: 107

Index was not present

[crythias]

Upgrade problems related to DROP columns or INDEXes should likely be safely ignored as long as it can be confirmed the next step is applied. (If it stops there, problems. If it continues, no big deal.)

Dropping is deleting. So if it can't find what it needs to drop, that's not inherently a problem as the task is already complete.