CiviCRM Community Forums (archive)

Yay

Sure, my original database was stuck at 4.3.3 and had gone through many upgrades and a couple times had some errors on the upgrade. Even after switching to civihosting my 4.3.3 database gave a trigger error that triggers weren't enabled. We (Hershel and I) determined that it had to be with the db. So I got the bright idea to do  compare the structures of the corrupt db with a clean 4.3.3 structure. Here are the steps I took:

• I did a structure dump of the Corrupt DB minus the custom tables.
• I imported the civicrm.mysql file from the 4.3.3 build into a clean db
• I did a structure dump of the clean import and then compared the files using a Diff tool. There were alot of issues that confirmed for me it was the db. I ensured that all column names matched between the two db's.
• I then did a structure dump of the custom tables in the corrupt db, then a data dump of the custom tables in the corrupt db, then a data dump of all the other tables in the corrupt db.
• Then I imported into the clean db in the following order: the structure of the custom tables, the data of the custom tables, the data of the other tables.
• Then I ran the upgrade to 4.3.5 and it upgraded without any errors

I'm not sure why the Foreign Keys got mixed up. It's very possible that it was my fault because I had tried to do some clean up on the database that didn't work.  But now everything works great and as expected.