View Single Post
  #7 (permalink)  
Old 04-27-2006, 08:57 AM
mubley mubley is offline
Senior Member
 
Join Date: Dec 2005
Posts: 44
mubley is on a distinguished road
Default Workaround

Quote:
Originally Posted by KevinH
Seems you've got a dup path in the volume table. Can you login to MySQL manually and dump that table. Might have to remove a path to get the update to run.
Here's the detail of how to implement KevinH's suggested workaround:

NOTE: If you have already attempted to upgrade to 3.1, you will need to revert to a backup of your M2 installation before continuing.

First, switch to the zimbra account:
Code:
su - zimbra
Next, launch the mysql client utility:
Code:
mysql
Tell mysql that you want to work on the zimbra database:
Code:
connect zimbra;
Drop the index called i_name:
Code:
alter table volume
drop index i_name;
Drop the index called i_path:
Code:
alter table volume
drop index i_path;
Quit the mysql client utility:
Code:
quit
Finally, switch back to the root account:
Code:
exit
You should now be able to successfully upgrade from M2 to 3.1.
Reply With Quote