Thread

So I’m testing the upgrade for a client site. We’re using a development server, upgrading from EE 1.7.3 to EE 2.5.2. The process was running smoothly, until we hit a database size issue

Your database is too large to perform this part of the upgrade via a web request. 
Please contact your system administrator and have them run the script located at: 
/serverpath/expressionengine/cache/installer/update.sh

We contacted our host, EngineHosting, and they ran the update.sh file for us. Going back to the page we left off on, I then (1) Refreshed the page [it said return to the page, but didn’t say if I should go back start over, or what, so I just refreshed.

From there, it started running into the script steps that were obviously already performed from the update.sh command. Most of them were on tables, that were relatively unimportant (in terms of client content)— things like parse smileys, and add field content type. But now the system wants to

ALTER TABLE `exp_weblog_data` CHANGE `field_id_1` `field_id_1` text NULL

I can’t just drop the field and let the system re-add it, since this contains clients data. So I’m wondering how best to proceed.

The client database is fairly large, I believe 500MB total, with about 150MB of that probably being revisions of publications. They maintain a large publications library. So I was expecting that some of the process would need to occur via shell, what I’m not certain of is if updates/ud_200.php was completed during the shell script run, or if components of it need to be ran in the web browser.

If something needs to be run via shell, can I then skip the update file I was in and move to the next file, in this case ud_201.php.

This is all in a testing environment, because we expected to run into issues with the database size, plus we have some secondary conversations (like moving items from Solspace’s Related Items to Pixel & Tonic’ Playa), so the issue is urgent, but NOT super urgent. The client is still up and running, it’s just our deadline for developing a bullet proof upgrade method that’s running out of time.

Any ideas? I’m hoping to have resolved by Monday or Tuesday of next week.

Hi allgood2,

Be on the lookout for an email from me. I want to work with you privately while we try this upgrade again.

Thanks Kevin, sent you the email.

Just posting a note here to let onlookers know that we’re working with allgood2 privately on this for the time being. I’ll post an update back here once we have something to share!