Thread

I need some help with this error message I got while upgrading a large database from ee1 to ee2.

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: 

/local_path/expressionengine/cache/installer/update.sh 

Then access this page again.

Once I got that error, I tried this command from the command line:

$ sh /local_path/expressionengine/cache/installer/update.sh

This is the output I got from that command:

Starting Large Database Conversion
UTF-8 Conversion (Step 1: Dumping database with current charset)
/local_path/expressionengine/cache/installer/update.sh: line 10: mysqldump: command not found
UTF-8 Conversion (Step 2: Importing database with UTF-8 charset)
/local_path/expressionengine/cache/installer/update.sh: line 17: mysql: command not found
UTF-8 Conversion (Step 3: Removing database dump)
DST Conversion (Step 1: Reading queries)
DST Conversion (Step 2: Writing temporary SQL file)
DST Conversion (Step 3: Importing temp file, this may take several minutes)
/local_path/expressionengine/cache/installer/update.sh: line 247: mysql: command not found
DST Conversion (Step 4: Removing temp file)
Large Database Conversion Completed: Please return to the browser to finish your upgrade.

Here are my questions:

1. What does it mean to “Then access this page again”? Does that mean I simply refresh the url that gave me the above error?

2. I am doing this upgrade locally on my computer. Is the command correct? Does the output look right? Am I doing this right?

NOTE: In the above snippets, I replaced the actual local path with local_path

Hi Mark,

This is an alternative upgrade function that we recently included in the Upgrade Wizard for large EE databases. Previously, large EE databases would very likely run into issues during their upgrade from 1.x to 2.x because the UTF8 conversion in the database would take a long time and the browser’s connection would drop before the conversion was complete. The result was that it would leave your database corrupted halfway through an upgrade.

This new feature alleviates that issue by having you run the UTF8 conversion in the command line where the same timeout constraints that would plague you in the browser won’t be a problem.

The output you posted from running that script tells me that you need to work with your host to ensure that you have the ability to run mysql and mysqldump commands from the command line. Since you’re doing this locally, you may want to perform a Google search for “mysqldump: command not found” and “mysql: command not found” and how to resolve those responses within your server environment.

“Then access this page again” just means you should reload that page in your browser once you’ve run the shell script successfully.

Does this help?

Thanks for the pointers, Kevin. That’s what I needed. I think I might have it working now. I had to update a few lines in the update.sh file.

For example, line 10 needed to be changed from this:

mysqldump -h localhost -u root

To this:

/Applications/MAMP/Library/bin/mysqldump -h localhost -u root

So if you’re working locally using MAMP, you need to include the local path to the command. And there are multiple commands like that in the update.sh file that need to be edited for this to work locally.

Great, thanks for posting back with your solution!

If there’s anything else that comes up, please let us know. We’ll be glad to help.