CiviCRM Community Forums (archive)

Hi, I'm doing a dry run of an upgrade on my local host prior to attempting it on the production server.

I've successfully upgrade drupal to 6.4 and my environment ticks all the boxes (php5.x, mysql5.x)

When I run the update script I get this error with these details:

DB Error: already exists

Database Error Code: Duplicate entry 'preferred_communication_method' for key 2, 1062

Details...

Array
(
    [callback] => Array
        (
           

• => CRM_Core_Error
[1] => handle
        )

   

=> -5
    [message] => DB Error: already exists
    [mode] => 16
    [debug_info] => ALTER TABLE `civicrm_option_group`
    ADD UNIQUE `UI_name` (name) [nativecode=1062 ** Duplicate entry 'preferred_communication_method' for key 2]
    [type] => DB_Error
    [user_info] => ALTER TABLE `civicrm_option_group`
    ADD UNIQUE `UI_name` (name) [nativecode=1062 ** Duplicate entry 'preferred_communication_method' for key 2]
    [to_string] => [db_error: message="DB Error: already exists" code=-5 mode=callback callback=CRM_Core_Error::handle prefix="" info="ALTER TABLE `civicrm_option_group`
    ADD UNIQUE `UI_name` (name) [nativecode=1062 ** Duplicate entry 'preferred_communication_method' for key 2]"]
)


Thanks for the reply

What worries me about this is that there are three entries for each option group: one for each domain. These are not arbitrary duplications and all have corresponding entries in option_value.

Just for the sake of experimentation

First I removed the duplicated entries (though they are not actually duplications having different id's and domain id's)...

same result

Then

I deleted all communication preferences entries and started again....

Now the error is with activity type, which of course is the next entry in the table.

Should I drop the table, or delete all entries?

I'll experiment later tonight or tomorrow (daughter's birthday meal this evening)

PS for anyone else experimenting you have to reinstate the old database since otherwise the upgrade is partial and leaves the database corrupted.

OK thanks. I'll give that a go. That's ok for me for testing purposes, but on the production site it gives me a problem since at least two domains (sites) are going to get stuffed.

What are other people with more that one site running off the same code base doing?

Does anyone have smart ways of migrating from multiple domains to multiple databases?