Thread

I read in a post (a reply to another user having similar issues) that there was an alternate method for upgrading large sites.  Could someone point me in that direction - I am having no luck moving from 1.7 to 2.3 and the issues I am having seem to relate to the size of my member tables.

Hi Philip,

the recommended route is what we have currently in the docs

We also have an upgrade troubleshooting page

What is your particular issue surrounding the size of this table?

Do you get errors, timeouts?

Can you describe your issues in detail please and we will do our best to help

Thanks John

I am getting the usual errors reported by numerous users in the forum.

The latest is:
A Database Error Occurred
Error Number: 1068

Multiple primary key defined

ALTER TABLE `exp_member_data` ADD PRIMARY KEY `member_id` (`member_id`)

Filename: updates/ud_200.php

Line Number: 1704

Each time I try to run the update I go back and clear my database completely, restore from an old backup.  Replace the config file again, check permissions etc..

I am not able to get past the install routine.

to further diagnose:

I am not getting any visual indication of a timeout, but as part of the my troubleshooting I did increase my MaxExec time in php-ini to 60 seconds.

I have followed the upgrade troubleshooting page point by point several times with no success.

I have performed many upgrades to v2 - perhaps 5 or 6 by now.  THis is the first one that is giving me issues.

When I delete the exp_member_data field, and continue the script it then stops at another:

A Database Error Occurred
Error Number: 1060

Duplicate column name ‘field_content_type’

ALTER TABLE `exp_weblog_fields` ADD COLUMN `field_content_type` VARCHAR(20) NOT NULL default ‘any’

Filename: updates/ud_200.php

Line Number: 1704

I then seem to get into a loop which takes me back to the exp_member_data issue, back to another field, back to member data etc..  ad infinitum (or so it seems)

so I have just spent yesterday afternoon and this morning building a brand new test environment.  Brought in my 1.6.8 site, brought it up to 1.7.1

It is running perfectly.

Did a full backup of the files and DB

Checked permissions on all web files.  Re-entered permissions for EE files (cache, config etc)

Zipped the webfolder as an additional backup so that I can roll back easily.

Check the site was still running as expected - yes.

Performed the update to v2 as instructed on the update page.  Performed locally on my own XServe (Snow Leopard Server), using Safari.

Same error as before:

A Database Error Occurred
Error Number: 1068

Multiple primary key defined

ALTER TABLE `exp_member_data` ADD PRIMARY KEY `member_id` (`member_id`)

Filename: updates/ud_200.php

Line Number: 1704

Is there anyone who can call me and walk me through an alternate method for updating?  I am spending way too much time on this, and it needs to be solved by end of week.

Thanks.

We are using three additional fields created in the member_data table.  This is the only thing that I can think of that is different from my other updated EE sites.

Is there anything peculiar about upgrading from a site with custom fields?

Philip

Does the error message indicate a duplicate key field ID, or two fields defined as key fields?
I have checked the data and so far not able to find any duplicate keys, and only one field (MemberID) is defined as a key field int he mySQL table.

A Database Error Occurred
Error Number: 1068

Multiple primary key defined

ALTER TABLE `exp_member_data` ADD PRIMARY KEY `member_id` (`member_id`)

Filename: updates/ud_200.php

Line Number: 1704

I rolled back to my safety set of files, loaded my backup DB, and removed the key from the memberID field in exp_memberData.  Also removed some duplicate entries in the uploadNoAccess table.

This time The update got all the way through and I am able to connect to the control panel.  The site is severely broken though.  I am going to have a look at it to see if it can be fixed, or whether I have to stay on 1.7..

Feels kinda like talking to myself here, but in the absence of EE support I suppose someone else might find these comments useful..

Philip

Hi Philip,

sorry for lack of response. Not sure how you kept slipping through in your responses like that.

What initially seems to be broken for you? Is it visual? Can you provide a screenshot?

Do you have any hardcoded theme paths in your config.php file?

Do you see any errors?

Do you save templates as files?
Is your template basepath still correct?

Did you login to control panel via new admin.php?

No worries about the delayed responses yesterday - I also have a support role and I know that you sometimes need focus to solve another problem.  I should have posted here earlier in the process, but I thought I should be able to figure it out using the KB articles.  Once I focused on the actual error messages I was able to find the issues.  It is interesting that you need to roll back completely (DB AND files) after each try.  Is there a single file somewhere that tracks the update progress so that you don;t have to replace everything?

I am not terribly worried about the broken state of the site at this point - we are undergoing a major redesign, and have an EE consultant who is doing that part of the work.  Since the CP is OK, he should be able to get pages displaying.  If he spots more trouble, I’ll create another thread.

Thanks again.

Hi Philip,

Have you seen the information about Retrying After a Failed Upgrade

Could you follow the instructions there and try one more time. If that doesn’t work, then be on the lookout for an email from me regarding accessing your site directly.

Sean