Dear OTRS community,
I'm in the middle of an upgrade from version 3.3.5 to version 4.
This all is going on on a linux VM with CentOS 6.5.
Following the following guide: http://otrs.github.io/doc/manual/admin/ ... ading.html
Everything went surprisingly well, up until Step 6. Apply the database changes.
I don't have alot of linux or SQL knowledge, and SQL seems to be evolving into the bane of my existence.
Following the guide I run the script otrs.CheckDB.pl
==> Successful
cat scripts/DBUpdate-to-4.mysql.sql | mysql -p -f -u root otrs
==> Foreign key constraint INFO: on valid_id_id and history_valid_id_id
I tried ignoring this part (how foolish of me) and tried to run the DBUpdate script to migrate DB.
At this point I had to add otrs user to the sudoers group, and after that I had to roll back to snapshot because I broke the sudoers group.
Can anyone give any pointers on what I might be missing? I love learning about this, but it seems to be hard without SQL knowledge.
Thanks in advance, and have a great day!
Matt
[SOLVED] Migration from 3.3.5 to 4.0
Moderator: crythias
-
- Znuny newbie
- Posts: 43
- Joined: 02 Sep 2014, 15:04
- Znuny Version: 4.0.7
- Real Name: Mattias
- Company: BusSaP
- Location: Belgium
[SOLVED] Migration from 3.3.5 to 4.0
Last edited by mavrie on 01 Apr 2015, 09:37, edited 1 time in total.
Otrs 4.0.7 on CentOS 6.5
MySQL Database
MySQL Database
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: Migration from 3.3.5 to 4.0
Normally a foreign key constraint issue indicates either that duplicate entries exist in one of the indexes/tables for a linking value (likely) or that a linking value may not exist to establish the connection between the tables.
The fix is ... well, it depends. Finding and removing duplicates is key. Usually you might have some indication where to start in error logs on establishing the foreign key constraint. It might be innocuous enough to modify or remove an entry.
However INFO is not warning or ERROR, so this may not be related to your issue.
The fix is ... well, it depends. Finding and removing duplicates is key. Usually you might have some indication where to start in error logs on establishing the foreign key constraint. It might be innocuous enough to modify or remove an entry.
However INFO is not warning or ERROR, so this may not be related to your issue.
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
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
-
- Znuny newbie
- Posts: 43
- Joined: 02 Sep 2014, 15:04
- Znuny Version: 4.0.7
- Real Name: Mattias
- Company: BusSaP
- Location: Belgium
Re: Migration from 3.3.5 to 4.0
Crythias,
Thank you for your reply.
I noted that the Foreign Key info's are about a missing value.
Something I should be able to fix by messing with the database tables?
Also, starting to think it would be easier to make a clean install of otrs 4 and import our old database, with customers and tickets, into this.
Could this possibly be true? Starting to lose alot of time on this migration thing.
Thanks!
Matt
Thank you for your reply.
I noted that the Foreign Key info's are about a missing value.
Something I should be able to fix by messing with the database tables?
Also, starting to think it would be easier to make a clean install of otrs 4 and import our old database, with customers and tickets, into this.
Could this possibly be true? Starting to lose alot of time on this migration thing.
Thanks!
Matt
Otrs 4.0.7 on CentOS 6.5
MySQL Database
MySQL Database
-
- Znuny newbie
- Posts: 43
- Joined: 02 Sep 2014, 15:04
- Znuny Version: 4.0.7
- Real Name: Mattias
- Company: BusSaP
- Location: Belgium
Re: Migration from 3.3.5 to 4.0
Hello,
Does anyone have experience with installing a new machine with version 4, and importing the database from version 3.3.5?
Obviously we do not want to lose our ticket history.
Regards,
Does anyone have experience with installing a new machine with version 4, and importing the database from version 3.3.5?
Obviously we do not want to lose our ticket history.
Regards,
Otrs 4.0.7 on CentOS 6.5
MySQL Database
MySQL Database
-
- Moderator
- Posts: 10170
- Joined: 04 May 2010, 18:38
- Znuny Version: 5.0.x
- Location: SouthWest Florida, USA
- Contact:
Re: Migration from 3.3.5 to 4.0
It's not possible to "import" tickets. You migrate the database.
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
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
-
- Znuny newbie
- Posts: 43
- Joined: 02 Sep 2014, 15:04
- Znuny Version: 4.0.7
- Real Name: Mattias
- Company: BusSaP
- Location: Belgium
Re: Migration from 3.3.5 to 4.0
Crythias,
Decided to go through with the upgrade procedure.
Made a new post about new issue.
viewtopic.php?f=62&t=28638
Thanks for the help so far.
Matt
Decided to go through with the upgrade procedure.
Made a new post about new issue.
viewtopic.php?f=62&t=28638
Thanks for the help so far.
Matt
Otrs 4.0.7 on CentOS 6.5
MySQL Database
MySQL Database