CiviCRM Community Forums (archive)

Well, since nobody was able to help me, after months of hard work, here's what I did to solve my issue (http://forum.civicrm.org/index.php/topic,18186.msg75489.html#msg75489).

After more than two months of trying to repair the DB, I was unable to successfully upgrade via civicrm's upgrade script, from 3.0.3 to 3.3.2 (at the time). I was able to upgrade to 3.1 stable, and 3.1alpha1, every version after that produced more DB related errors that I was unable to resolve. I tried every stable release and alpha/beta's in between.

I finally decided to take on performing the upgrade manually. Started with a fresh install of the latest stable version of civicrm, v3.3.3, manually imported data from the 3.0.3 DB, modifying the DB as needed- adding and/or deleting fields in each table. Then, I proceeded to run the incremental.sql (located in civicrm/CRM/Upgrade/Incremental) one query at a time, for every version after 3.0.3- civicrm_option_group, civicrm_option_value tables, mssg_tpl templates, and many more. I also had a fresh install of civicrm 3.3.3 with sample data, to compare to during this process.

After a practice run in my dev environment, I was able to successfully perform the manual upgrade in production in two days. There were a few things I missed and corrected as issues presented themselves, nothing major though- mostly option_group, and option_value related issues, a views issue related to civicrm_custom_group's table, and a few others.  I will create a new topic for the few remaining issues, and will post the links in this thread when I do. I have every issue and solution fully documented. If anybody has or is planning to upgrade civicrm manually, just post your issue and I will do my best to help.

Hi,

It happened to me as well to have a broken update (mostly because I'm using svn versions and didn't run the right script at the right time, my fault).

One issue I had was that the incremental mysql scripts are templates, ie. they contain {smarty} tags that mysql doesn't like.

I've developed a while ago a command line script that generates the sql from the template, saved me some time. Can push it somewhere if someone needs it.

X+

Well, since nobody was able to help me, after months of hard work, here's what I did to solve my issue (http://forum.civicrm.org/index.php/topic,18186.msg75489.html#msg75489).

After more than two months of trying to repair the DB, I was unable to successfully upgrade via civicrm's upgrade script, from 3.0.3 to 3.3.2 (at the time). I was able to upgrade to 3.1 stable, and 3.1alpha1, every version after that produced more DB related errors that I was unable to resolve. I tried every stable release and alpha/beta's in between.

I finally decided to take on performing the upgrade manually. Started with a fresh install of the latest stable version of civicrm, v3.3.3, manually imported data from the 3.0.3 DB, modifying the DB as needed- adding and/or deleting fields in each table. Then, I proceeded to run the incremental.sql (located in civicrm/CRM/Upgrade/Incremental) one query at a time, for every version after 3.0.3- civicrm_option_group, civicrm_option_value tables, mssg_tpl templates, and many more. I also had a fresh install of civicrm 3.3.3 with sample data, to compare to during this process.

After a practice run in my dev environment, I was able to successfully perform the manual upgrade in production in two days. There were a few things I missed and corrected as issues presented themselves, nothing major though- mostly option_group, and option_value related issues, a views issue related to civicrm_custom_group's table, and a few others.  I will create a new topic for the few remaining issues, and will post the links in this thread when I do. I have every issue and solution fully documented. If anybody has or is planning to upgrade civicrm manually, just post your issue and I will do my best to help.