CiviCRM Community Forums (archive)

This was the solution to upgrade issues from 3.1.1 to 3.2.5 and having looked through the code that controls the upgrade I believe it is also likely to be good for other 3.1 versions - but you will have noted the disclaimer!

As always please make sure you have a backup ready to roll back!

Preliminary step - check your civicrm_location_type table - if the first two records have id's 1 and 2 then great, if not you will run foul of a feature of two of the database upgrade scripts that have location_type_id hard-coded into them - make a note of the location_type_id's and then open and edit the following two scripts:

civicrm/CRM/Upgrade/Incremental/sql/3.2.beta3.mysql.tp
civicrm/CRM/Upgrade/Incremental/sql/3.2.beta4.mysql.tp

Find the INSERT INTO civicrm_uf_field statement and edit the values that corresponds to location_type_id (I think the 9th value) in the relevant rows changing the 1 and 2 to the values of these id's in your own data, as noted before.

(thanks to jords for this)

That's the preliminary done.

Next we need to deal with the tables and indixes that are unexpectedly present in the database:

I use MySQL Workbench to run the following script (you could probably use phpMyadmin just as well):

DROP TABLE civicrm_entity_financial_trxn, civicrm_financial_account, civicrm_website, civicrm_address_format;
ALTER TABLE civicrm_activity
DROP INDEX index_medium_id,
DROP INDEX index_is_current_revision,
DROP INDEX index_is_deleted;

That's it.