CiviCRM Community Forums (archive)

3rd one

Deepak,

Oh yeah - duh. Thanks....so I ran your query again but this time for civicrm_acl_entity_role table instead. Upon doing so, I get this mysql error:
ALTER TABLE `civicrm_acl_entity_role` ADD CONSTRAINT `FK_civicrm_acl_domain_id` FOREIGN KEY ( `domain_id` ) REFERENCES `civicrm_domain` ( `id` )

MySQL said: Documentation
#1005 - Can't create table './cctvcivicrm_v2/#sql-6cb_c81b.frm' (errno: 121)
appears to be the same kind of error that the upgrade is giving me. here's a screenshot of my civicrm_acl_entity_role table.

OK, thanks to some big help from Deepak, this is all sorted out.

Essentially, my 2.0 db was corrupted, and even though it looked like it had all the correct FK constraints, it didn't. Because there were too many to fix manually we had to reload my whole db into a properly structured 2.0 db. Here are the steps we followed:

1. Dumped all of the data only from my db
2. I had some custom value fields in my db (custom value tables start with civicrm_value_), and since a new CiviCRM 2.0 database wouldn't have these tables, I needed to dump just the structure of my custom value tables. i did not dump the structure for any other tables.
3. I created a new, empty database
4. Import civicrm/sql/civicrm.mysql into my empty database from CiviCRM 2.0 (NOT 2.1). This gave me the correct 2.0 database structure.
5. Imported my structure dump from step 2 into my new database.
6. Ran the following query on my new database to add a column that existed at one point in 2.0 but no longer does. Without this step, the next step was failing for me.
ALTER TABLE civicrm_group_contact ADD loc_block_id int(10) unsigned default NULL;7. Imported the data dump from step 1 to my new database. This gives me a correct 2.0 database with all of my data in it.
8. Ran the upgrade script, which completed successfully.
9. Ran the following query to remove the column I added in step 6:
ALTER TABLE `civicrm_group_contact`
  DROP `loc_block_id`;
10. Followed the rest of the Drupal upgrade to 2.1 instructions to complete the upgrade.

Hi Emily,

When I am trying to do step 7 its giving me following error.

#1452 - Cannot add or update a child row: a foreign key constraint fails (`imtaDataNew/civicrm_activity`, CONSTRAINT `FK_civicrm_activity_source_contact_id` FOREIGN KEY (`source_contact_id`) REFERENCES `civicrm_contact` (`id`) ON DELETE CASCADE)
I am updating 2.0 to 2.1.2 stable.

Can you please help.

Thanks

Thanks Emily,

Got the problem resolved through some professional services.