CiviCRM Community Forums (archive)

This is going to be a thread of my hell-ride to upgrade CiviCRM.

Part 1
------

After running the upgrade script, I see this:

Sorry. A non-recoverable error has occurred.

Database check failed - it looks like you have already upgraded to the latest version (v3.0.4) of the database. OR If you think this message is wrong, it is very likely that this a partially upgraded db and you will need to reload the correct db on which upgrade was never tried.

The message is wrong. I have no idea what "reload the correct db" means.  My
setup uses a combined Drupal/CiviCRM database. That's the _only_ database;
so I assume that is the "correct" database, for there is no other.

I then decided to try using the CiviCRM tools.  First civicrm_db_integrity.php.  I get these
errors when running this:

php civicrm_db_integrity.php -u username -ppassword -h localhost apgn_drupal

PHP Notice:  Undefined index:  USER in /home/xxxx/clients/apgn/civicrm_dbtools-1.2/civicrm_db_utils.php on line 2164

Notice: Undefined index:  USER in /home/xxxx/clients/apgn/civicrm_dbtools-1.2/civicrm_db_utils.php on line 2164

I checked the code and see that it's trying to use the environment to ascertain the user.  Well the database user in this case does not have a shell account, so I merely added the username in the appropriate place in civicrm_db_utils.php.  It then gets past the above error, but then there's a new one (and note: I had to remove the password from the command line because it contains characters the php command line can't handle:

PHP Notice:  Use of undefined constant apgn_drupal - assumed 'apgn_drupal' in /home/xxxx/clients/apgn/civicrm_dbtools-1.2/civicrm_db_utils.php on line 2165

Notice: Use of undefined constant apgn_drupal - assumed 'apgn_drupal' in /home/xxxx/clients/apgn/civicrm_dbtools-1.2/civicrm_db_utils.php on line 2165
Password:
Can't connect to MySQL server on localhost:
   could not find driver


So now I'm up a creek without a paddle.

I assume the last bit about a "driver" has something to do with the environment, but I'm not sure what.

All I'm trying to do is upgrade a working system. I tried to upgrade a couple of months ago and finally gave up.  Now I'm trying again, because some core functionality errors with regard to accessing pariticipant data which I reported earlier here on the forums. I was told the only solution was to upgrade because no one could help me solve the stated problems with such an old version of CiviCRM (2.2.7).

I'm not expecting any help, just thought I'd let off some steam.

Cheers,
Russ

Database check failed - it looks like you have already upgraded to the latest version (v3.0.4) of the database. OR If you think this message is wrong, it is very likely that this a partially upgraded db and you will need to reload the correct db on which upgrade was never tried.

The message indicates that the upgrade script came across few tables / columns in your 2.2.7 database that it was expecting to be present only in v3.0.x database.

This generally happens when upgrade in first step attempt fails for some reason, AND the user tries to re-run the upgrade by either refreshing the page or visiting the upgrade url again.

Solution is to replace your database with the backup you had taken before hitting upgrade, and then try visiting upgrade again. Thats what is meant by "reload the correct db".
And if you don't have the backup, you are on your own to fire queries (by looking at the code) to bring your database back in pre-upgrade state.

I assume you made a backup of the entire database in line with the Upgrade Instructions before you started the upgrade? Is that correct? Because that is the database you should go back to. If that reports errors too than I would almost think that someone tried to upgrade to 3 without making a backup first?

Hi Erik --

If that reports errors too than I would almost think that someone tried to upgrade to 3 without making a backup first?

Thanks for the reply. In fact I did make a full backup per the instructions given in the wiki, but I just realized that I had tried to upgrade last December and gave up and that is the backup.  I do have a production site DB I will try tomorrow.  

My last attempt to upgrade with a pre-upgrade 2.2.7 DB was met with the following error.  Have any suggestions, Erik?

Followed instructions to the T.  Click on Upgrade and then this:

Error Details:

Array
(
    [callback] => Array
        (
          

    * => CRM_Core_Error
      [1] => handle
              )

          

[c ode] => a515ac9c2796ca0e23adbe92c68fc9fc
    [message] => DB Error: a515ac9c2796ca0e23adbe92c68fc9fc
    [mode] => 16
    [debug_info] => DROP TRIGGER civicrm_report_instance_before_insert [nativecode=1360 ** Trigger does not exist]
    [type] => DB_Error
    [user_info] => DROP TRIGGER civicrm_report_instance_before_insert [nativecode=1360 ** Trigger does not exist]
    [to_string] => [db_error: message="DB Error: a515ac9c2796ca0e23adbe92c68fc9fc" code=0 mode=callback callback=CRM_Core_Error::handle prefix="" info="DROP TRIGGER civicrm_report_instance_before_insert [nativecode=1360 ** Trigger does not exist]"]
)

I have no idea where to start trying to fix this problem. In our setup the Drupal
and Civicrm Databases are in the same database.

Thanks for any ideas.

    [message] => DB Error: a515ac9c2796ca0e23adbe92c68fc9fc
    [mode] => 16
    [debug_info] => DROP TRIGGER civicrm_report_instance_before_insert [nativecode=1360 ** Trigger does not exist]

I see that you had posted this problem here - http://forum.civicrm.org/index.php/topic,11250.0.html
Not sure if you had tried the suggested solution.