Error during upgrade: Duplicate key name 'i_name'

[hodel]

I recevied this error when I upgraded my version of Zimbra. Anyone else have this problem? I'm going to restore my backup and try an incremental upgrade to see if that works.

Upgrading from 3.0.0_M2_746 to 3.1.0_GA_332
Sat Apr 15 17:24:08 2006: Stopping zimbra services
Sat Apr 15 17:24:11 2006: Checking mysql status
Sat Apr 15 17:24:11 2006: Starting mysql
Sat Apr 15 17:24:12 2006: SELECT value FROM config WHERE name = 'db.version'
Sat Apr 15 17:24:13 2006: Checking logger mysql status
Sat Apr 15 17:24:13 2006: Starting logger mysql
This appears to be 3.0.0_M2
Schema upgrade required
Sat Apr 15 17:24:14 2006: Running /opt/zimbra/libexec/scripts/migrate20051021-UniqueVolume.pl
Sat Apr 15 17:24:15 2006: SELECT value FROM config WHERE name = 'db.version'
Sat Apr 15 17:24:15 2006: Verified schema version 21.
Sat Apr 15 17:24:15 2006: Updating volume table
Sat Apr 15 17:24:15 2006: ALTER TABLE volume
ADD UNIQUE i_name (name),
ADD UNIQUE i_path (path(255));


ERROR 1061 (42000) at line 1: Duplicate key name 'i_name'
Error while running '/opt/zimbra/bin/mysql --user=zimbra --password=vdDv4tC50MLqxfir_5NMQFklqIQ --database=zimbra --batch --skip-column-names'. at /opt/zimbra/libexec/scripts/Migrate.pm line 134, 
 line 1.
Sat Apr 15 17:24:16 2006: Script failed with code 1 - exiting
UPGRADE FAILED - exiting

[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.

[mubley]

That's the same error that I saw when upgrading from M2. I asked about it, but never got a response:
Mac Intel Support

I was able to restore from a backup, upgrade to 3.0.1_GA_160, and then upgrade to 3.1.0_GA_260 successfully.

[hodel]

I'll give that a try and see what happens. If it doesn't work, I'll look into what KevinH said.

Originally Posted by mubley

That's the same error that I saw when upgrading from M2. I asked about it, but never got a response:
Mac Intel Support

I was able to restore from a backup, upgrade to 3.0.1_GA_160, and then upgrade to 3.1.0_GA_260 successfully.

[mubley]

I've created Bug 7385 for this:
http://bugzilla.zimbra.com/show_bug.cgi?id=7385

See also:
Script faield upgrading from 3.0.0_M2_746 to 3.1.0_GA_332
http://www.zimbra.com/forums/showpo...81&postcount=10

[mubley]

I've updated Bug 7385 with one possible solution.

[mubley]

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:

su - zimbra

Next, launch the mysql client utility:

mysql

Tell mysql that you want to work on the zimbra database:

connect zimbra;

Drop the index called i_name:

alter table volume
drop index i_name;

Drop the index called i_path:

alter table volume
drop index i_path;

Quit the mysql client utility:

quit

Finally, switch back to the root account:

exit

You should now be able to successfully upgrade from M2 to 3.1.