Migrate script errors during upgrade from Redmine 0.8.2.stable (MySQL) ruby 1.8.6 to the latest redmine stack 1.0.1.
Added by paul brook about 14 years ago
— create_table(:member_roles)
rake aborted!
An error has occurred, all later migrations canceled:
Mysql::Error: Table ‘member_roles’ already exists: CREATE TABLE `member_roles` (
`id` int(11) DEFAULT NULL auto_increment PRIMARY KEY,
`member_id` int(11) NOT NULL, `role_id` int(11) NOT NULL) ENGINE=InnoDB
It seems that this is important. I located the ruby file that was failing and moved it out of the folder and re ran the rake. The script got to another error and I removed that one as well. In the end I removed 4 scripts and then the rake process ran to completion and I was able to access my data. The 4 files were:
20090503121501_create_member_roles.rb
20090704172355_create_groups_users.rb
20090704172358_add_member_roles_inherited_from.rb
20091017213716_add_missing_indexes_to_member_roles.rb
I am upgrading from Redmine 0.8.2.stable (MySQL) ruby 1.8.6 to the latest redmine stack 1.0.1.
Any help would be appreciated, however, so far it seems like I'm in good shape just don't know for sure.
Replies (2)
RE: Migrate script errors during upgrade from Redmine 0.8.2.stable (MySQL) ruby 1.8.6 to the latest redmine stack 1.0.1. - Added by Felix Schäfer about 14 years ago
Some of those migrations are needed, you can't just take them out and expect things to work… Revert to the backup from your 0.8.2 installation and follow the upgrade guide, it especially states what to do with the member_roles table if errors arise: RedmineUpgrade.
RE: Migrate script errors during upgrade from Redmine 0.8.2.stable (MySQL) ruby 1.8.6 to the latest redmine stack 1.0.1. - Added by paul brook about 14 years ago
Thanks for the help.
It all makes sense.
I'll post a followup when I get it running.