CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • Problems Upgrading from 1.9 --> 2.0.3 and now 2.0.4
Pages: [1]

Author Topic: Problems Upgrading from 1.9 --> 2.0.3 and now 2.0.4  (Read 1645 times)

mwilliams

  • Guest
Problems Upgrading from 1.9 --> 2.0.3 and now 2.0.4
June 03, 2008, 01:47:06 pm
Hi. I've been having foreign key issues attempting to upgrade from 1.9.13019 to 2.0.3 and now 2.0.4. We're using MySQL 5.0.45 and PHP   5.2 (5.2.3-1ubuntu6.3). Despite numerous attempts to move forward with this (normalizing the schema/rebuilding database as instructed in documentation, filling and/or removing FK data, removing/modding existing table structures) --- I constantly get this error message:

"Sorry. A non-recoverable error has occurred.

Database consistency check failed for step 1. FK constraint names not in the required format. Please rebuild your 1.9 database to ensure schema integrity.

Return to home page."

I've searched hard for answers (ex. followed this thread and references - http://forum.civicrm.org/index.php/topic,3180.0.html) to no avail. Wasn't able to get any relevant info from insert debugging code in the DAO.php file either. Like similar posts, is there any way to narrow this down to specific tables or get a more detail error message? Is there anyway that my database can be looked at?

I feel like I'm losing my grip on reality at this point and could really use some outside eyes/hands here.  ::) Thanks in advance  :).


Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Problems Upgrading from 1.9 --> 2.0.3 and now 2.0.4
June 03, 2008, 01:59:00 pm

Check this post: http://forum.civicrm.org/index.php/topic,2647.msg11397.html#msg11397

and check your DB for those FK keys

also in civicrm_activity

FK_civicrm_activity_source_contact_id
FK_civicrm_activity_parent_id

Those FK's are supposed to exist with those specific names in a valid 1.9 db

if you still need someone to look at the db and do the upgrade, you might want to contact web access from http://civicrm.org/professional/

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

mwilliams

  • Guest
Re: Problems Upgrading from 1.9 --> 2.0.3 and now 2.0.4
June 03, 2008, 03:21:34 pm
Thanks for the quick reply. I've checked my databases (both production and dev) for the noted keys and see that they all exist with those exact names. Should they all be changed to a particular type or assigned a standard value? Are those the only FK keys that should be present in a 1.9 database?

This is my third CiviCRM upgrade and I'm pretty solid with SQL & PHP, so I don't think that I exactly need professional services like that. I just need to get some clarification on what needs to done to my database's structure to get to the next step of this upgrade (ultra frustrating at this point). For as much as I've seen in the Forums here regarding upgrade problems, I'm kinda surprised that it's so hard to find detailed feedback about this particular or particular type of problem (not a knock on another or anything, just a general point).

Thanks again for any response in advance!!!

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: Problems Upgrading from 1.9 --> 2.0.3 and now 2.0.4
June 03, 2008, 03:46:06 pm

Your best bet would be to add debug statements to:

CRM/Upgrade/TwoZero/Form/Step1.php, line 84 and see which of the FK's is missing and throwing the error

You should probably add a debug statement in CRM/Core/DAO.php, checkFKConstraintInFormat to find the missing FK

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • Problems Upgrading from 1.9 --> 2.0.3 and now 2.0.4

This forum was archived on 2017-11-26.