Author Topic: Error Upgrading 3.3.1 -> 3.3.2 on Drupal 6.20 (Read 682 times)

vshura · January 10, 2011, 10:48:55 am

Hi all.

I just updated Drupal from 6.19 to 6.20. Then I updated CiviCRM 3.2.1 to 3.2.2 and got a non-recoverable error (which I didn't record unfortunately).

I restored by 3.2.1 database and code and cleared the cache and rebuilt the menus, just in case it was something to do with the Drupal upgrade, and then tried to upgrade to 3.2.2 again. I got another non-recoverable error:

Code: [Select]

Sorry. A non-recoverable error has occurred.
DB Error: can not create

Database Error Code: Can't create table 'dublin_civicrm.#sql-594a_65d711' (errno: 121), 1005
Additional Details:

Array
(
    [callback] => Array
        (
            [0] => CRM_Core_Error
            [1] => handle
        )

    [code] => -15
    [message] => DB Error: can not create
    [mode] => 16
    [debug_info] => ALTER TABLE civicrm_mailing_job
DROP FOREIGN KEY parent_id, 
DROP INDEX parent_id ,
ADD CONSTRAINT FK_civicrm_mailing_job_parent_id 
FOREIGN KEY (parent_id) REFERENCES civicrm_mailing_job (id) ON DELETE CASCADE [nativecode=1005 ** Can't create table 'dublin_civicrm.#sql-594a_65d711' (errno: 121)]
    [type] => DB_Error
    [user_info] => ALTER TABLE civicrm_mailing_job
DROP FOREIGN KEY parent_id, 
DROP INDEX parent_id ,
ADD CONSTRAINT FK_civicrm_mailing_job_parent_id 
FOREIGN KEY (parent_id) REFERENCES civicrm_mailing_job (id) ON DELETE CASCADE [nativecode=1005 ** Can't create table 'dublin_civicrm.#sql-594a_65d711' (errno: 121)]
    [to_string] => [db_error: message="DB Error: can not create" code=-15 mode=callback callback=CRM_Core_Error::handle prefix="" info="ALTER TABLE civicrm_mailing_job
DROP FOREIGN KEY parent_id, 
DROP INDEX parent_id ,
ADD CONSTRAINT FK_civicrm_mailing_job_parent_id 
FOREIGN KEY (parent_id) REFERENCES civicrm_mailing_job (id) ON DELETE CASCADE [nativecode=1005 ** Can't create table 'dublin_civicrm.#sql-594a_65d711' (errno: 121)]"]
)

Any ideas what's going on? In particular, why would there need to be a table called' #sql-594a_65d711' created?

With thanks,
Vshura

Hershel · January 10, 2011, 11:31:48 am

That is a name of a temporary table used by MySQL I think.

When you restored the database, did you first empty it? I would recommend that you completely empty your CiviCRM database and then restore it to make sure that no remnants of the failed upgrade process are left.

Then run the upgrader again and be sure to capture any errors.

vshura · January 10, 2011, 11:36:39 am

Hi Hershel,

Yep, I dropped all the tables repeatedly until the database was completely empty before trying to upgrade again to 3.2.2.

I was using phpMyAdmin. There's no such thing as hidden tables, is there? I've never seen the likes of #sql-594a_65d711 before when poking around in phpMyAdmin.

Thanks,
Vshura.

Hershel · January 10, 2011, 12:04:58 pm

Hi. No, MySQL doesn't have hidden tables. You will never see such a table because I think it's a temporary one that MySQL uses internally and then destroys.

I am not sure what your error is however. It appears to be a foreign key constraint problem but I'm not clear as to what precisely it is.

I could attempt to debug it manually, but perhaps someone else here has a better idea.

vshura · January 10, 2011, 12:09:43 pm

Ok, thanks Hershel.

I just reverted to the Drupal 6.19 and CiviCRM 3.2.1 and then tried to upgrade to 3.2.2 but got the same error.

Anyone got any more ideas?

CiviCRM Community Forums (archive)

News:

Author Topic: Error Upgrading 3.3.1 -> 3.3.2 on Drupal 6.20 (Read 682 times)

vshura

Error Upgrading 3.3.1 -> 3.3.2 on Drupal 6.20

Hershel

Re: Error Upgrading 3.3.1 -> 3.3.2 on Drupal 6.20

vshura

Re: Error Upgrading 3.3.1 -> 3.3.2 on Drupal 6.20

Hershel

Re: Error Upgrading 3.3.1 -> 3.3.2 on Drupal 6.20

vshura

Re: Error Upgrading 3.3.1 -> 3.3.2 on Drupal 6.20