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) »
  • Problem upgrading from 1.9 to 2.0 beta
Pages: [1] 2

Author Topic: Problem upgrading from 1.9 to 2.0 beta  (Read 5489 times)

depace

  • Guest
Problem upgrading from 1.9 to 2.0 beta
February 19, 2008, 07:07:38 am
Hey...

I've a test site running drupal 5.7 + civicrm 1.9

n' i've been trying to upgrade civicrm 1.9 to 2.0 beta

but unfortunately i'm gettin this error everytime i press "Upgrade & Continue" button...


Sorry. A non-recoverable error has occurred.
Database check failed - the current database is not v1.9.



any clue on this ???
Thanks...

Server info:
Open Suse
Apache 2.2.4
MySql 5.0
PHP 5.2

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: Problem upgrading from 1.9 to 2.0 beta
February 19, 2008, 09:32:42 am

most likely you are not running 1.9 :)

we check that:

1. the civicrm_mailing_spool table exists
2. there is no column called version in civicrm_domain

can u manually check your db and verify that the above is true?

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

depace

  • Guest
Re: Problem upgrading from 1.9 to 2.0 beta
February 19, 2008, 09:55:34 pm
hi

i just checked.. n' the table civicrm_mailing_spool table exists
and the table civicrm_domain has a field called version with value as 1.91

Deepak Srivastava

  • Moderator
  • Ask me questions
  • *****
  • Posts: 677
  • Karma: 65
Re: Problem upgrading from 1.9 to 2.0 beta
February 19, 2008, 11:29:31 pm
Quote
and the table civicrm_domain has a field called version with value as 1.91
Thats the reason for the fatal error.

The version number-1.91 is an indication of, coming out of upgrade wizard after running step1.

If you have the backup of your database (not having version column in civicrm_domain table), use that database to run the upgrade wizard on.

And if not (worst case), you will have to manually undo the process done by the upgrade wizard in step1. And then run the upgrade process.
« Last Edit: February 19, 2008, 11:38:15 pm by Deepak Srivastava »
Found this reply helpful? Contribute NOW and help us improve CiviCRM with the Make it Happen! initiative.

depace

  • Guest
Re: Problem upgrading from 1.9 to 2.0 beta
February 20, 2008, 04:18:56 am
hey thanks.. .

now i got this error

Sorry. A non-recoverable error has occurred.
Database consistency check failed for step 2. FK constraint names not in the required format.

Scenario:
1. Drupal 5.1 + civicrm 1.8
2. Upgraded to drupal 5.7
3. Upgraded to civicrm 1.8
4. Upgraded to civicrm 1.9 (with upgrade sql file)
5. replaced civicrm codebase with 2.0beta...
6. hit to ?q=civicrm/upgrade&reset=1 and press "Upgrade & Continue" button
« Last Edit: February 20, 2008, 04:53:42 am by depace »

Deepak Srivastava

  • Moderator
  • Ask me questions
  • *****
  • Posts: 677
  • Karma: 65
Re: Problem upgrading from 1.9 to 2.0 beta
February 20, 2008, 08:12:44 am
The error says that your database schema is not inline with civicrm 1.9 db schema (some foreign keys have not been assigned the expected names).

This means you will again have to start the process by doing the dump / reload to empty 1.9 schema manually.

General instructions for this are on the wiki at: http://wiki.civicrm.org/confluence/display/CRMDOC/Ensuring+Schema+Integrity+on+Upgrades
(make sure you do it for 1.9)

And after having done that, you can run the upgrade wizard ( hopefully without any problem ). Please report back your results here! This will help us figure out if / what improvements might be needed in the final version of the upgrade wizard.
« Last Edit: February 20, 2008, 09:37:09 am by Dave Greenberg »
Found this reply helpful? Contribute NOW and help us improve CiviCRM with the Make it Happen! initiative.

Deepak Srivastava

  • Moderator
  • Ask me questions
  • *****
  • Posts: 677
  • Karma: 65
Re: Problem upgrading from 1.9 to 2.0 beta
February 21, 2008, 12:10:47 am
Also consider visiting "Rebuild your 1.9 Database to Ensure Schema Integrity" section of http://wiki.civicrm.org/confluence/display/CRMDOC/Upgrade+Drupal+Sites+to+2.0, which has been recently updated.
Found this reply helpful? Contribute NOW and help us improve CiviCRM with the Make it Happen! initiative.

depace

  • Guest
Re: Problem upgrading from 1.9 to 2.0 beta
February 21, 2008, 01:24:00 am
hi
i tried again as stated in
4. Rebuild your 1.9 Database to Ensure Schema Integrity

now i can get to the next step ... but i got another issue...

CiviCRM 2.0 Upgrade: Step Two (Location Data Upgrade)

Sorry. A non-recoverable error has occurred.

Database Error Code: Cannot add or update a child row: a foreign key constraint fails (`civicrm19fix/#sql-bec_122`, CONSTRAINT `FK_civicrm_group_contact_contact_id` FOREIGN KEY (`contact_id`) REFERENCES `civicrm_contact` (`id`) ON DELETE CASCADE), 1452

Deepak Srivastava

  • Moderator
  • Ask me questions
  • *****
  • Posts: 677
  • Karma: 65
Re: Problem upgrading from 1.9 to 2.0 beta
February 21, 2008, 01:41:00 am
Just run this query on 1.9 db ( just to confirm ).
Code: [Select]
DELETE gc.*
FROM civicrm_group_contact gc
LEFT JOIN civicrm_contact cc ON cc.id = gc.contact_id
WHERE cc.id IS NULL

And start the upgrade again. And if you still get the same error, means your 1.9 db is still not inline with 1.9 schema.
« Last Edit: February 21, 2008, 01:44:20 am by Deepak Srivastava »
Found this reply helpful? Contribute NOW and help us improve CiviCRM with the Make it Happen! initiative.

depace

  • Guest
Re: Problem upgrading from 1.9 to 2.0 beta
February 21, 2008, 02:15:21 am
humm

Code: [Select]
DELETE gc.*
FROM civicrm_group_contact gc
LEFT JOIN civicrm_contact cc ON cc.id = gc.contact_id
WHERE cc.id IS NULL

now it says
Database check failed - the current database is not v1.9.


I've followed all the schema integrity check processes ... over n' over again :-)



« Last Edit: February 21, 2008, 02:39:03 am by depace »

Deepak Srivastava

  • Moderator
  • Ask me questions
  • *****
  • Posts: 677
  • Karma: 65
Re: Problem upgrading from 1.9 to 2.0 beta
February 21, 2008, 02:29:19 am
Hope you following this order.

1) Take 1.9 schema corrected db ( not having version column in civicrm_domain table ).
2) Run the query (i submitted in my last post) on 1.9 corrected db.
3) Run the upgrade wizard ( starting from step1 ).
Found this reply helpful? Contribute NOW and help us improve CiviCRM with the Make it Happen! initiative.

depace

  • Guest
Re: Problem upgrading from 1.9 to 2.0 beta
February 21, 2008, 03:37:44 am
I'm back to same situation

Database Error Code: Cannot add or update a child row: a foreign key constraint fails (`civicrm19fix/civicrm_email`, CONSTRAINT `FK_civicrm_email_contact_id` FOREIGN KEY (`contact_id`) REFERENCES `civicrm_contact` (`id`) ON DELETE CASCADE), 1452

are u in irc?

Deepak Srivastava

  • Moderator
  • Ask me questions
  • *****
  • Posts: 677
  • Karma: 65
Re: Problem upgrading from 1.9 to 2.0 beta
February 21, 2008, 03:57:09 am
Is it possible for you to give / send me the dump of 1.9 schema corrected db ( not having version column in civicrm_domain table ) ?

My email ID : deepak at webaccess dot co dot in

This would also help us correct / improve our upgrade process.
Found this reply helpful? Contribute NOW and help us improve CiviCRM with the Make it Happen! initiative.

Deepak Srivastava

  • Moderator
  • Ask me questions
  • *****
  • Posts: 677
  • Karma: 65
Re: Problem upgrading from 1.9 to 2.0 beta
February 21, 2008, 07:47:53 am
depace,

Thanks a lot for the db.

Though it had few inconsistencies, it really helped us A LOT (more than i expected) to improve the "cleanup step" of upgrade process.
Found this reply helpful? Contribute NOW and help us improve CiviCRM with the Make it Happen! initiative.

depace

  • Guest
Re: Problem upgrading from 1.9 to 2.0 beta
February 25, 2008, 12:29:42 am
hi deepak..

is there any fix released for this ?

Pages: [1] 2
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • Problem upgrading from 1.9 to 2.0 beta

This forum was archived on 2017-11-26.