upgrade 2.2.2 to 3.2 - error message during upgrade relating to civicrm_activit

[tobiaseigen]

Hi all,

I am currently upgrading my site from 2.2.2 to 3.2 and am stuck with the error below and when I browse to the civicrm backend from now on I see "Database check failed - the database looks to have been partially upgraded. You may want to reload the database with the backup and try the upgrade process again."

I've tried this twice and got the same error.  Any advice would be much appreciated.

Thanks,

Tobias

Code: [Select]

Additional Details:
Array
(
    [callback] => Array
        (
            [0] => CRM_Core_Error
            [1] => handle
        )

    [code] => -5
    [message] => DB Error: already exists
    [mode] => 16
    [debug_info] => ALTER TABLE civicrm_activity
ADD INDEX UI_source_record_id(source_record_id),
ADD INDEX UI_activity_type_id (activity_type_id),
ADD INDEX index_medium_id (medium_id),
ADD INDEX index_is_current_revision (is_current_revision),
ADD INDEX index_is_deleted (is_deleted) [nativecode=1061 ** Duplicate key name 'UI_activity_type_id']
    [type] => DB_Error
    [user_info] => ALTER TABLE civicrm_activity
ADD INDEX UI_source_record_id(source_record_id),
ADD INDEX UI_activity_type_id (activity_type_id),
ADD INDEX index_medium_id (medium_id),
ADD INDEX index_is_current_revision (is_current_revision),
ADD INDEX index_is_deleted (is_deleted) [nativecode=1061 ** Duplicate key name 'UI_activity_type_id']
    [to_string] => [db_error: message="DB Error: already exists" code=-5 mode=callback callback=CRM_Core_Error::handle prefix="" info="ALTER TABLE civicrm_activity
ADD INDEX UI_source_record_id(source_record_id),
ADD INDEX UI_activity_type_id (activity_type_id),
ADD INDEX index_medium_id (medium_id),
ADD INDEX index_is_current_revision (is_current_revision),
ADD INDEX index_is_deleted (is_deleted) [nativecode=1061 ** Duplicate key name 'UI_activity_type_id']"]
)[/code]

[xavier]

You are upgrading to 3.2.1 ?

There is a bug in the upgrade code. A patch will be published soon (and probably a new version of civicrm)

X+

[tobiaseigen]

hi xavier - thanks for the tip. should I be upgrading to a different version? do you know when the new patch will be published?

thanks,

tobias

[xavier]

Hi,

Yes, you should. The patch is basically ready. An issue about what is the proper index.

I'd guess it will be published soon.

X+

[tobiaseigen]

thanks - now I've basically upgraded civicrm on my sandbox and the standard features all appear to be working. now to get the custom code up to speed....

-t

[Eileen]

I'm hitting an error on the same entry but a different key:


 [debug_info] => ALTER TABLE civicrm_activity
ADD INDEX UI_source_record_id(source_record_id),
ADD INDEX index_medium_id (medium_id),
ADD INDEX index_is_current_revision (is_current_revision),

ADD INDEX index_is_deleted (is_deleted) [nativecode=1061 ** Duplicate key name 'index_medium_id']

[tobiaseigen]

Hi Eileen - I stopped getting this error when upgrading to the most recent release.

[TallDavid]

Same problem trying to upgrade CiviCRM from 3.2.0 to 3.2.3
Getting:

DB Error: already exists
Database Error Code: Duplicate key name 'index_medium_id', 1061

^{Note to self: tp.org}

[Eileen]

How odd - I don't have a long history with the site I was upgrading but it seemed OK.

[TallDavid]

Eileen, do you recall what versions (from/to) you were upgrading when you got the error and which versions worked?

[Eileen]

No, I don't actually - it was a test version so I 'bullied it through' & then when I did it on live I dropped the indexes first

[TallDavid]

Eileen, you gave me a thought.  Previously I had tried DROPing index_medium_id, but, would still get the same error.  After reading your post, I DROPped the indexes:

• index_medium_id
• index_is_current_revision
• index_is_deleted

from TABLE civicrm_activity, re-ran the update and it completed without error.  Hope this helps the next person to encounter this error.

[Eileen]

Yeah - the other option is to comment those lines out of the upgrade file if your mysql / phpadmin access is limited. It's in the upgrade folder under incremental (off the top of my head). There should be a file per point version in there

[ehowland]

I am upgrading from version 3.1.5 to 3.2.3

First I got the duplicate index message.  I deleted the indexes as suggested by TallDavid

Then I got the cannot create table - already exists error for table civicrm_entity_financial_trxn.  

I then had to re-restore the database and both delete the indexes and drop the civicrm_entity_financial_trxn table.

Now I get  "DB Error: already exists" but there is no detail in the Error Details box so I am a bit at sea as for what to do next.

[Eileen]

I'm guessing the reason you had to re-restore is that the extra table was not deleted when you did your restore. If you have a good backup & you didn't last time I would drop the DB/ restore it & then drop the indexes & try again.

The error message IS a bit mysterious