CiviCRM Community Forums (archive)

Hi.

Myself and a colleague are having similar foreign key issues attempting to upgrade from 1.9 to 2.0.2. We are using MySQL 5 and PHP 5.

We have followed the instructions through step 6 [http://wiki.civicrm.org/confluence/display/CRMDOC/Upgrade+Drupal+Sites+to+2.0#UpgradeDrupalSitesto2.0-6.Unpackthe2.0package] and upon running the update script at Step 7, have encountered an error:
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.

We've searched through forum posts and found some relevant ones:
http://forum.civicrm.org/index.php?topic=2991.0
http://forum.civicrm.org/index.php/topic,3128.msg13786.html#msg13786
http://forum.civicrm.org/index.php/topic,2771.0.html
http://wiki.civicrm.org/confluence/display/CRMDOC/Upgrade+Drupal+Sites+to+2.0?focusedCommentId=7372809#comment-7372809

None of the custom data fields or groups have a name of "null". I'm having a hard time trying to figure out other ways to narrow down the issue.

Is there some way to figure out which table the error is coming from? I see some other posts where people seem to have narrowed the Foreign Key errors down to a specific table. Is there a setting that I can turn on that will spit out more verbose errors?

Any other suggestions to ensure the data is correct (or to find the orphaned or bad data)?

Thanks.

Erik.

Just to wrap this up, the upgrade has now worked for us using 2.0.3.

Also for anyone else finding this, make sure you don't confuse CIVICRM_DSN with CIVICRM_UF_DSN. Whoops.