Top Menu

Jump to content
Home
    Modules
      • Projects
      • Activity
      • Work packages
      • Gantt charts
      • Calendars
      • Team planners
      • Boards
      • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.
    • Help and support
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Enterprise support
    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
    Activity
  • Roadmap
  • Work packages
    Work packages
  • Gantt charts
    Gantt charts
  • Calendars
    Calendars
  • Team planners
    Team planners
  • Boards
    Boards
  • News
  • Forums
  • Feature tour
    Feature tour

Content

You are here:
  1. Forums
  2. Support Installation & Updates

Migration 2.4->3.0

Added by Chau Thai over 10 years ago

Hi,

I’m migrating from 2.4 to 3.0 and notice some errors in your guide (https://www.openproject.org/projects/openproject/wiki/Migration_24_to_30).
In the “Change timestamps timezone to UTC” section, you need to execute
“bundle exec rake migrations:change_timestamps_to_utc FROM= SECRET_TOKEN=irrelevanthere RAILS_ENV=production”
otherwise there will be an error.

Also I had problems with the utf enconding of the open project tables while migrating:
http://pastebin.com/NVe3PCpe

So I tried convert all Open Project database tables to to unicode_ci in the mysql prompt:

SELECT CONCAT ("ALTER TABLE ",TABLE_SCHEMA,".",TABLE_NAME," CHARACTER SET utf8 COLLATE utf8_unicode_ci; ",
"ALTER TABLE ",TABLE_SCHEMA,".",TABLE_NAME," CONVERT TO CHARACTER SET utf8 COLLATE utf8_unicode_ci; ")
AS alter_sql
FROM information_schema.TABLES
WHERE TABLE_SCHEMA = ‘openproject’;

The migration still doesn’t work and stops at the exact same error.
Maybe you can help me out!


Replies (4)

RE: Migration 2.4->3.0 - Added by Chau Thai over 10 years ago

Ok,
I solved my problem!
With these 2 commands:
mysql> show variables like “collation_database”;

and

mysql> show table status;

I’ve taken look at the collation of the tables and they were totally screwed up. (see attachment 1)
So I converted every ut8_general_ci table to utf8_unicode_ci with
alter table done_statuses_for_project convert to character set utf8 collate utf8_unicode_ci;

I hope I could help someone with this tip;-)

RE: Migration 2.4->3.0 - Added by mab internet about 9 years ago

Hi Chau Thai,

I am trying to migrate from ChiliProject to OpenProject but I am facing some problems. I found that you did the migration from OP2.4 to OP3.0. I have some problems with this step and I was wondering if you could help me.
After the migration, the history of the wiki pages is not working. After a lot of work I found that some entries in the table “wiki_content_journals” are duplicated and others have error in the field “page_id”. I still do not manage to fix the error; I could only use some SQL queries to try to fix the database after the error is there.
Did you have the same error during the migration?

Cheers
Luis

RE: Migration 2.4->3.0 - Added by Chau Thai about 9 years ago

Hi Luis,

we didn’t use the wiki in our instance of OpenProject.
Could you paste your error log of OpenProject when accessing a wiki page?
Without an error log it’s hard to figure out the problem.

Bye
Chau

RE: Migration 2.4->3.0 - Added by mab internet about 9 years ago

Hi Chau,

I have created another message with the whole information.

https://community.openproject.org/topics/5061

But if you did not use the wiki, then you have not seen the problem. It is basically when the journals are migrated and placed in different tables.
The table with the wiki content journals (in OP3.0) has duplicated entries and some errors in one field. This wrong information (generated with the execution of “bundle exec rake db:migrate SECRET_TOKEN=irrelevanthere RAILS_ENV=production” to migrate the database from OP2.4 to OP3.0) produces the error in OP3.0.
The execution of “bundle exec rake db:migrate SECRET_TOKEN=irrelevanthere RAILS_ENV=production” shows that it finishes successfully (with apparently no errors); nevertheless, the generated database has the duplicated and erroneous entries.

In any case, if you need more information I can provide it.

Cheers
Luis

  • (1 - 4/4)
Loading...