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) »
  • 3.2.4 or 3.2.5 to 3.3.0 Upgrade Error
Pages: [1]

Author Topic: 3.2.4 or 3.2.5 to 3.3.0 Upgrade Error  (Read 1176 times)

vasike

  • Guest
3.2.4 or 3.2.5 to 3.3.0 Upgrade Error
December 06, 2010, 03:20:57 am
Sorry. A non-recoverable error has occurred.
DB Error: a515ac9c2796ca0e23adbe92c68fc9fc
Error Details
Database Error Code: Specified key was too long; max key length is 1000 bytes, 1071
Additional Details:

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

       
Code: [Select]
=> a515ac9c2796ca0e23adbe92c68fc9fc
    [message] => DB Error: a515ac9c2796ca0e23adbe92c68fc9fc
    [mode] => 16
    [debug_info] => ALTER TABLE civicrm_option_value MODIFY COLUMN value varchar(512) [nativecode=1071 ** Specified key was too long; max key length is 1000 bytes]
    [type] => DB_Error
    [user_info] => ALTER TABLE civicrm_option_value MODIFY COLUMN value varchar(512) [nativecode=1071 ** Specified key was too long; max key length is 1000 bytes]
    [to_string] => [db_error: message="DB Error: a515ac9c2796ca0e23adbe92c68fc9fc" code=0 mode=callback callback=CRM_Core_Error::handle prefix="" info="ALTER TABLE civicrm_option_value MODIFY COLUMN value varchar(512) [nativecode=1071 ** Specified key was too long; max key length is 1000 bytes]"]
)


Michał Mach

  • Ask me questions
  • ****
  • Posts: 748
  • Karma: 59
    • CiviCRM site
  • CiviCRM version: latest
  • CMS version: Drupal and Joomla latest
  • MySQL version: numerous
  • PHP version: 5.3 and 5.2
Re: 3.2.4 or 3.2.5 to 3.3.0 Upgrade Error
December 06, 2010, 05:18:02 am
Please check the engine for your civicrm_option_value table (and others as well) - it should be InnoDB. I encountered below error with working on MyISAM CiviCRM database. If that's the reason, change the engine for your tables (on 3.2.4 db) and try the upgrade again.

Thx,
m
Found this reply helpful? Contribute NOW and help us improve CiviCRM with the Make it Happen! initiative.

My absolute favourite: Wordpress Integration!.

Donate Now!

vasike

  • Guest
Re: 3.2.4 or 3.2.5 to 3.3.0 Upgrade Error
December 07, 2010, 02:02:26 am
i tried as you said with no success, i altered all tables to innodb and then run the upgrade.
what should i do?

this is the error:

Sorry. A non-recoverable error has occurred.
DB Error: a515ac9c2796ca0e23adbe92c68fc9fc
Error Details
Database Error Code: Error on rename of './DB/civicrm_contact' to './DB/#sql2-6693-3be' (errno: 152), 1025
Additional Details:

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

       
Code: [Select]
=> a515ac9c2796ca0e23adbe92c68fc9fc
    [message] => DB Error: a515ac9c2796ca0e23adbe92c68fc9fc
    [mode] => 16
    [debug_info] => ALTER TABLE civicrm_contact DROP  FOREIGN KEY FK_civicrm_contact_mail_to_household_id [nativecode=1025 ** Error on rename of './DB/civicrm_contact' to './DB/#sql2-6693-3be' (errno: 152)]
    [type] => DB_Error
    [user_info] => ALTER TABLE civicrm_contact DROP  FOREIGN KEY FK_civicrm_contact_mail_to_household_id [nativecode=1025 ** Error on rename of './DB/civicrm_contact' to './DB/#sql2-6693-3be' (errno: 152)]
    [to_string] => [db_error: message="DB Error: a515ac9c2796ca0e23adbe92c68fc9fc" code=0 mode=callback callback=CRM_Core_Error::handle prefix="" info="ALTER TABLE civicrm_contact DROP  FOREIGN KEY FK_civicrm_contact_mail_to_household_id [nativecode=1025 ** Error on rename of './DB/civicrm_contact' to './DB/#sql2-6693-3be' (errno: 152)]"]
)


vasike

  • Guest
Re: 3.2.4 or 3.2.5 to 3.3.0 Upgrade Error
December 10, 2010, 02:30:22 am
the solution to receive no more errors on the upgrade it was:
1. convert to innodb
2. comment (delete) all the ALTER's for DROPing the FOREIGN KEYs SQL commands from upgrade mysql files
3. use 3.3.1 for upgrade

Michał Mach

  • Ask me questions
  • ****
  • Posts: 748
  • Karma: 59
    • CiviCRM site
  • CiviCRM version: latest
  • CMS version: Drupal and Joomla latest
  • MySQL version: numerous
  • PHP version: 5.3 and 5.2
Re: 3.2.4 or 3.2.5 to 3.3.0 Upgrade Error
December 14, 2010, 07:42:18 am
You might also want to take a look at this document, just in case:
http://wiki.civicrm.org/confluence/display/CRMDOC33/Ensuring+Schema+Integrity+on+Upgrades

Thx,
m
Found this reply helpful? Contribute NOW and help us improve CiviCRM with the Make it Happen! initiative.

My absolute favourite: Wordpress Integration!.

Donate Now!

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • 3.2.4 or 3.2.5 to 3.3.0 Upgrade Error

This forum was archived on 2017-11-26.