Thread

Trying an upgrade on a test subdomain and getting this error:

A Database Error Occurred
Error Number: 1050

Table 'exp_comment_subscriptions' already exists

CREATE TABLE `exp_comment_subscriptions` ( `subscription_id` int(10) UNSIGNED AUTO_INCREMENT, `entry_id` int(10) UNSIGNED, `member_id` int(10) DEFAULT '0', `email` varchar(50), `subscription_date` varchar(10), `notification_sent` char(1) DEFAULT 'n', `hash` varchar(15), PRIMARY KEY `subscription_id` (`subscription_id`), KEY `entry_id` (`entry_id`), KEY `member_id` (`member_id`) ) DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;

Filename: updates/ud_211.php

Line Number: 101

« Back

Following the user guide so not sure where I went wrong.

So i’ve taken a look at the upgrading failures wiki and am confused on how to clean out / dump the database.

Iam working on a test subdomain, wouldn’t dumping the database interrupt the live site?

Hi tsfexhibit,

I know upgrading issues can be frustrating, and I’m sorry to see this causing trouble for you. Are the test subdomain and the live site sunning from the *same* database? If they are running on separate databases, you would want to ensure that you make all your changes to the database driving the test subdomain and not the live site. Do you have a backup of the database from before attempting the upgrade?

Best,

I’m not 100% sure. Not very familiar with databases but I can answer this:

1 - Same database
2 - I backed up the database.php but not sure what else needs to be backed up.

Hey tsfexhibit,

Since both the test and live site share a database, anything you manipulate on the test domain will impact the live site. When updating EE, changes are made to the database. So any updates you ran on the test domain, impacted the database for both your test and live sites.

I assume the live site is experiencing issues too since the update was not successful?

Typically, before updating, you’ll want to backup your entire database, not just the database.php file. You can do this by using something like phpMyAdmin to do a database dump. That way, in case things go awry, you have something to rollback to.

Can you let me know what version you were updating to and from? Also, when running the upgrade, did you refresh the page during the process, or click the upgrade button more than once?

Sorry you are experiencing these issues, and we hope to get this resolved for you ASAP.

Thanks.

I was on version 1.7.1 and going to 2.2.1.

The live site is actually not experiencing any problems (knock on wood).

I pressed the upgrade button when trying it again.

Hi tsfexhibit,

My suggestion here is to bring in someone to help you out who can bring you up to speed on how databases interact with web applications like ExpressionEngine. Like Kyle said, if you’re running both your live site and test site off the same database, any changes to one could potentially show up on the other. Thus, you really need to be running one database for the live site and another, completely separate database for the test site. That will allow you to upgrade the test site and completely test it out before migrating those changes to the live site.

Are those things you feel comfortable with doing?

Thanks

No problem. I’ll go ahead and close this thread out for now. If you need some more help after bringing in someone to assist with the upgrade, please feel free to open up a new related thread by clicking the button below!