Duplicate Key Name?

Hi all,

I’m attempting to upgrade from RT 3.4.5 to RT 4.

I am getting:
Processing 3.7.81
Now populating database schema.
[Mon May 9 13:30:38 2011] [crit]: DBD::mysql::st execute failed:
Duplicate key name 'CachedGroupMembers3’
at /opt/rt4/sbin/…/lib/RT/Handle.pm line 503.
(/opt/rt4/sbin/…/lib/RT.pm:340)
DBD::mysql::st execute failed: Duplicate key name 'CachedGroupMembers3’
at /opt/rt4/sbin/…/lib/RT/Handle.pm line 503.

I dropped the RT4 table to see if it was cruft, but nothings changed.
I’m running MySQL 5.1.42 on a redhat 5.4 box.

Joshua Knarr
knarrj@gsicommerce.com
Desk: 610-491-7110
Mobi: 484-636-7371

The information contained in this electronic mail transmission is
intended only for the use of the individual or entity named in this
transmission. If you are not the intended recipient of this
transmission, you are hereby notified that any disclosure, copying or
distribution of the contents of this transmission is strictly prohibited
and that you should delete the contents of this transmission from your
system immediately. Any comments or statements contained in this
transmission do not necessarily reflect the views or position of GSI
Commerce, Inc. or its subsidiaries and/or affiliates.

I am getting:
Processing 3.7.81
Now populating database schema.
[Mon May 9 13:30:38 2011] [crit]: DBD::mysql::st execute failed: Duplicate key name
’CachedGroupMembers3’ at /opt/rt4/sbin/…/lib/RT/Handle.pm line 503.
(/opt/rt4/sbin/…/lib/RT.pm:340)
DBD::mysql::st execute failed: Duplicate key name ‘CachedGroupMembers3’ at
/opt/rt4/sbin/…/lib/RT/Handle.pm line 503.

I dropped the RT4 table to see if it was cruft, but nothings changed. I’m running MySQL 5.1.42
on a redhat 5.4 box.

Did you make your own CachedGroupMembers3 at some point?

If so, you can skip 3.7.81 if you’re defining the same index.

If you defined a site-specific index with different values, you
probably want to rename it so you get our index

-kevin

This is an “inherited” box. I did a quick sqldump to fork the db and
skipped the version. Seemed to go smoothly after that until…

[root@ashprdrt01 rt-4.0.0]# /opt/rt4/sbin/rt-server --port 8080
RT since version 3.8 has new schema for MySQL versions after 4.1.0
Follow instructions in the UPGRADING.mysql file.

Turned out I had an older version of CPAN (one minor version behind)
which was throwing errors about itemify A cpan upgrade and then a cpan
-r fixed this. Then I had to follow the upgrading.mysql doc and now it’s
good to go.

Thanks for the help.On Mon, 2011-05-09 at 10:19 -0400, Kevin Falcone wrote:

On Mon, May 09, 2011 at 09:34:38AM -0400, Joshua Knarr wrote:

I am getting:
Processing 3.7.81
Now populating database schema.
[Mon May 9 13:30:38 2011] [crit]: DBD::mysql::st execute failed: Duplicate key name
’CachedGroupMembers3’ at /opt/rt4/sbin/…/lib/RT/Handle.pm line 503.
(/opt/rt4/sbin/…/lib/RT.pm:340)
DBD::mysql::st execute failed: Duplicate key name ‘CachedGroupMembers3’ at
/opt/rt4/sbin/…/lib/RT/Handle.pm line 503.

I dropped the RT4 table to see if it was cruft, but nothings changed. I’m running MySQL 5.1.42
on a redhat 5.4 box.

Did you make your own CachedGroupMembers3 at some point?

If so, you can skip 3.7.81 if you’re defining the same index.

If you defined a site-specific index with different values, you
probably want to rename it so you get our index

-kevin

Joshua Knarr
knarrj@gsicommerce.com
Desk: 610-491-7110
Mobi: 484-636-7371

The information contained in this electronic mail transmission is
intended only for the use of the individual or entity named in this
transmission. If you are not the intended recipient of this
transmission, you are hereby notified that any disclosure, copying or
distribution of the contents of this transmission is strictly prohibited
and that you should delete the contents of this transmission from your
system immediately. Any comments or statements contained in this
transmission do not necessarily reflect the views or position of GSI
Commerce, Inc. or its subsidiaries and/or affiliates.