CiviCRM Community Forums (archive)

Hello,

I have a test installation soon to be demoed and become the base for a productive one.
Very small database.

When I upgraded it from 4.3.5 to 4.4.0, the database upgrade failed after the 4.4alpha1 step.

Error: Consolidate activity contacts
INSERT INTO civicrm_activity_contact (activity_id, contact_id, record_type_id) SELECT activity_id, target_contact_id, 3 as record_type_id FROM civicrm_activity_target [nativecode=1062 ** Duplicate entry '1-9-3' for key 'UI_activity_contact']

Strange, for a database with 50 activity contacts and no code changes whatsoever!
Activities I do have: registrations confirmed, cancelled and pending from later payment, email in, email out.

I spare you the backtrace (but kept it, so if necessary I'll post it)

Since everything in there is test data, I didn't mind losing some contact activity so I decided to restore the DB, remove the records in civicrm_activity_contact that are to be come duplicate keys, and rerun the upgrade.
Unfortunately there are several steps of this Consolidate Activities, so no luck - just went to the next error with entries from civicrm_activity_assignment inserted into civicrm_activity_contact

In the end I choose to sacrifice more data and truncate the source tables rather than the destination table
this turned out to be an incremental activity with an unpredictable time to finish... but, OK, just 3 tables.
civicrm_activity_target
civicrm_activity_assignment
civicrm_activity
It is surely not ok to tamper in this way with a live CRM DB!
So for me, the migration is done at last.
But what I f I had the thousands of contacts and activities I'm planning to have in a few months? I'd be stuck for good.

I do suppose not many others experience this - any idea how I have put my DB in this state?
No added code. Originally 4.1.5, changed server and upgraded to 4.3.5 then 4.4.0.

Thanks for looking into this, to prevent blocking some full-scale upgrades.

I had exactly the same error today.
Can't afford losing data so must revert...

Please announce when a workaround is found...

Yes. Data are confidential. Can I send directly to you?

I got the database file and did a quick check. That is not a valid backup file. A table: civicrm_activity_contact exists (this was introduced in 4.4), this triggers the error message.

In this case we can potentially recover and fix things, however i'm not sure what other impact the upgrade script would have. Would help to ensure you have good clean backups and do so on a regular basis (or switch to a host who can do good daily backups)

http://issues.civicrm.org/jira/browse/CRM-13665

lobo

Great!

Well, I'm in the same case as pederb and that's good news!

The DB and backup I used were made after an earlier attempt at upgrading to 4.4 alpha - I had a tablecivicrm_activity_contact in my 4.3.5 backup. Silly me as well.
I repeated the whole upgrade with a database drop, a restore from an earlier backup and the upgrade went fine.
Thanks for the help! And for CiviCRM.