Thread

I’m upgrading a local copy of 1.7 to 2.1.3 before moving servers & getting the following error… please help!

Error Number: 1068

Multiple primary key defined

ALTER TABLE `exp_weblog_data` ADD PRIMARY KEY `entry_id` (`entry_id`)

Filename: updates/ud_200.php

Line Number: 1382

Please let me know what additional information you need.

BrunoBoys,

Can you tell us what version of PHP and MySQL are you using please?

PHP 5.3.2

MySQL 5.1.44

Let me also tell you that I first successfully upgraded from 1.6.8 to 1.7, then when trying to go to 2.1.3, that is when this error was thrown at me.

Hi, BrunoBoys. If you look at your 1.70 database *before* attempting to upgrade, does exp_weblog_data have a primary key of entry_id?

Mine does.. hmmmm.. I haven’t tried a 1.7.0 upgrade to 2.1.3 in a while. Let me go see if the same thing happens to me. Thanks in advance for your patience.

Hi Sue,

I rolled back to 1.6.8 when I got the error, only because I didn’t sql dump at 1.7.

To answer your question, yes it does have a primary of entry_id.

Hi, BrunoBoys.

I just upgraded from 1.7.0 to EE2.1.4Beta, and didn’t run into that particular issue - can you test locally to see if timing out could be an issue? How big is your .sql file?

Hey Sue,

Unzipped, it’s close to 100mb.

This was actually my 2nd time trying to go to ee2 & got an err, so that’s when I decided to reach out to you guys.

I can try to up again & duplicate.

P.S. all of these upgrades have been local.

BrunoBoys,

Can you try the upgrade again please but beforehand backup your database and go in and do a repair and optimize first. See if that makes a difference

I will try again, but I did actually repair & optimize prior to upgrading the 2nd time. I read through the forum & saw that suggested many times, so I did as well. This post was after reading through all the threads & your suggestions when it came to db errors.

I should be able to attempt again tonight & I will let you guys know.

Very good; we’ll be here. Thanks.

Well, I ran into a different issue this time.

It seems as though something on the live site changed with the addition of the new dev site.
Let me explain a little further.

Lets say on Wednesday I did a new sql dump from the live site.
On Thursday some forum topics were deleted on the live site.
On Friday I created a new database on a dev site & imported Wednesday’s dump. Afterward, I updated all the system prefs (so I thought) to point to the new server paths & dev domain name.

Today, the topics are back in the forum of the live site.

Do you guys have a checklist of all system pref locations that need paths to be updated when switching servers?
Is there an order of each that needs to be completed so the dev site & the live site don’t cross each others paths?

BrunoBoys,

Do you guys have a checklist of all system pref locations that need paths to be updated when switching servers?

Usually, this consists of the path information found in the following areas: Admin, Channel Management, File Upload Preferences, Global Channel Preferences, Membership Preferences, CAPTCHA Preferences, Emoticon Preferences and Forum preferences.  If you save templates as text files, update the ‘Basepath to Template File Directory’ in ‘Design >Templates> Global Template Preferences’.

Is there an order of each that needs to be completed so the dev site & the live site don’t cross each others paths?

There is no particular order. The main thing to make sure of is that if an EE1.x site that the db settings are right in your config.php file and if EE2.x that they are right in your database.php file

Is there an order of each that needs to be completed so the dev site & the live site don’t cross each others paths?

The only way I can see those deleted forum items appearing again is if you imported your dump back into the same live database again.

Deeploy Helper is a nice add-on that puts all those paths in one place in your control panel

Ok, thanks. It must have been a path that wasn’t updated or something.

One last question (I think) :D

To reiterate: I’m starting at 1.6.8, going to 1.7, then 2

Should I upgrade the forum to the latest after upgrading to 1.7 or after 2?

Do you have the 1.x latest version of the forum? If possible, upgrade the forum at the same time as your incremental upgrade to 1.7, and then finish out to 2.1.3.

Does that make sense?

The forum I’m on now is 2.1.1, so now I’ve up’d EE to 1.7. 

Are you saying that there a 2.1.2 for the forum that I need to go to?

Then go to ee 2, then up the forum to 2.1.3?