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) »
  • CiviCRM database error after 1.7 > 1.8 upgrade
Pages: [1] 2

Author Topic: CiviCRM database error after 1.7 > 1.8 upgrade  (Read 4871 times)

Neil Adair

  • I post occasionally
  • **
  • Posts: 78
  • Karma: 4
  • CiviCRM version: 4.5.8
  • CMS version: Drupal 7
  • MySQL version: MariaDB 10
  • PHP version: 5.5 FPM
CiviCRM database error after 1.7 > 1.8 upgrade
August 22, 2007, 12:45:52 pm
Looking for clues as to what may have caused this error

Database Error Code: Incorrect information in file: './testv4mmp_crm/civicrm_domain.frm', 1033

Error Details:

[db_error: message="DB Error: unknown error" code=-1 mode=callback callback=CRM_Core_Error::handle prefix="" info="SELECT config_backend FROM civicrm_domain WHERE ( civicrm_domain.id = 1 ) [nativecode=1033 ** Incorrect information in file: './testv4mmp_crm/civicrm_domain.frm']"]

Kurund Jalmi

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4169
  • Karma: 128
    • CiviCRM
  • CiviCRM version: 4.x, future
  • CMS version: Drupal 7, Joomla 3.x
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: CiviCRM database error after 1.7 > 1.8 upgrade
August 22, 2007, 12:59:35 pm
Please check your database name specified in civcrm dsn (civicrm.settings.php)

HTH

Kurund
Found this reply helpful? Support CiviCRM

Neil Adair

  • I post occasionally
  • **
  • Posts: 78
  • Karma: 4
  • CiviCRM version: 4.5.8
  • CMS version: Drupal 7
  • MySQL version: MariaDB 10
  • PHP version: 5.5 FPM
Re: CiviCRM database error after 1.7 > 1.8 upgrade
August 22, 2007, 01:08:36 pm
They look OK. This is a test site which I upgraded to 1.8 a few days ago. We had a problem with the main site and when we went to look at the test site it started throwing this error too.

Kurund Jalmi

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4169
  • Karma: 128
    • CiviCRM
  • CiviCRM version: 4.x, future
  • CMS version: Drupal 7, Joomla 3.x
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: CiviCRM database error after 1.7 > 1.8 upgrade
August 22, 2007, 01:14:50 pm
I hope you have followed this intructions:
http://wiki.civicrm.org/confluence/display/CRMDOC/Upgrading+Drupal+Sites+from+v1.7+to+v1.8

especially clearing drupal session tables etc..
Found this reply helpful? Support CiviCRM

Neil Adair

  • I post occasionally
  • **
  • Posts: 78
  • Karma: 4
  • CiviCRM version: 4.5.8
  • CMS version: Drupal 7
  • MySQL version: MariaDB 10
  • PHP version: 5.5 FPM
Re: CiviCRM database error after 1.7 > 1.8 upgrade
August 22, 2007, 01:21:50 pm
Yes, meticulously! Reset the Drupal session and cleaned up template cache.

The site has been working fine for the last few days

Kurund Jalmi

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4169
  • Karma: 128
    • CiviCRM
  • CiviCRM version: 4.x, future
  • CMS version: Drupal 7, Joomla 3.x
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: CiviCRM database error after 1.7 > 1.8 upgrade
August 22, 2007, 01:30:56 pm
hope this will give you some clue:
http://www.phpwsforums.com/showthread.php?t=3034

kurund
Found this reply helpful? Support CiviCRM

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: CiviCRM database error after 1.7 > 1.8 upgrade
August 22, 2007, 02:06:15 pm

1. most likely your civicrm_domain table is corrupt. You will need to repair it (mysql command)

2. are you using MyISAM? (i'm pretty sure you are). CiviCRM uses transactions and rollbacks to avoid getting into a bad state. This is NOT supported by MyISAM, and hence will cause you issues down the road. You should definitely move the db's to InnoDB

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

Neil Adair

  • I post occasionally
  • **
  • Posts: 78
  • Karma: 4
  • CiviCRM version: 4.5.8
  • CMS version: Drupal 7
  • MySQL version: MariaDB 10
  • PHP version: 5.5 FPM
Re: CiviCRM database error after 1.7 > 1.8 upgrade
August 22, 2007, 02:36:17 pm
This is the sql for the civicrm_domain table, it looks like it's InnoDB

--
-- Table structure for table `civicrm_domain`
--

DROP TABLE IF EXISTS `civicrm_domain`;
CREATE TABLE `civicrm_domain` (
  `id` int(10) unsigned NOT NULL auto_increment COMMENT 'Domain ID',
  `name` varchar(64) collate utf8_unicode_ci default NULL COMMENT 'Name of Domain / Organization',
  `description` varchar(255) collate utf8_unicode_ci default NULL COMMENT 'Description of Domain.',
  `contact_name` varchar(64) collate utf8_unicode_ci default NULL COMMENT 'Name of the person responsible for this domain',
  `email_domain` varchar(64) collate utf8_unicode_ci default NULL COMMENT 'The domain from which outgoing email for this domain will appear to originate',
  `email_return_path` varchar(64) collate utf8_unicode_ci default NULL COMMENT 'The domain from which outgoing email for this domain will appear to originate',
  `config_backend` text collate utf8_unicode_ci COMMENT 'Backend configuration.',
  `config_frontend` text collate utf8_unicode_ci COMMENT 'Frontend configuration.',
  PRIMARY KEY  (`id`),
  UNIQUE KEY `UI_name` (`name`)
) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci;


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: CiviCRM database error after 1.7 > 1.8 upgrade
August 22, 2007, 02:49:01 pm

in your mysql database, can u run this command:

mysql> show create table civicrm_domain \G;

There is a difference between what is present in the sql file and what mysql interprets it as :)

The main reason i think u r with MyISAM is because of the civicrm_domain.frm file, which i think is a MyISAM based file

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

Neil Adair

  • I post occasionally
  • **
  • Posts: 78
  • Karma: 4
  • CiviCRM version: 4.5.8
  • CMS version: Drupal 7
  • MySQL version: MariaDB 10
  • PHP version: 5.5 FPM
Re: CiviCRM database error after 1.7 > 1.8 upgrade
August 22, 2007, 03:11:25 pm
mysql> show create table civicrm_domain \G;
ERROR 1033 (HY000): Incorrect information in file: './testv4mmp_crm/civicrm_domain.frm'
ERROR:
No query specified

Neil Adair

  • I post occasionally
  • **
  • Posts: 78
  • Karma: 4
  • CiviCRM version: 4.5.8
  • CMS version: Drupal 7
  • MySQL version: MariaDB 10
  • PHP version: 5.5 FPM
Re: CiviCRM database error after 1.7 > 1.8 upgrade
August 23, 2007, 04:23:39 pm
Things started to work better when a second instance of MySQL was killed!

Now I get the following which confirms that these are MyISAM tables.

mysql> show create table civicrm_domain \G;
*************************** 1. row ***************************
       Table: civicrm_domain
Create Table: CREATE TABLE `civicrm_domain` (
  `id` int(10) unsigned NOT NULL auto_increment COMMENT 'Domain ID',
  `name` varchar(64) collate utf8_unicode_ci default NULL COMMENT 'Name of Domain / Organization',
  `description` varchar(255) collate utf8_unicode_ci default NULL COMMENT 'Description of Domain.',
  `contact_name` varchar(64) collate utf8_unicode_ci default NULL COMMENT 'Name of the person responsible for this domain',
  `email_domain` varchar(64) collate utf8_unicode_ci default NULL COMMENT 'The domain from which outgoing email for this domain will appear to originate',
  `email_return_path` varchar(64) collate utf8_unicode_ci default NULL COMMENT 'The domain from which outgoing email for this domain will appear to originate',
  `config_backend` text collate utf8_unicode_ci COMMENT 'Backend configuration.',
  `config_frontend` text collate utf8_unicode_ci COMMENT 'Frontend configuration.',
  PRIMARY KEY  (`id`),
  UNIQUE KEY `UI_name` (`name`)
) ENGINE=MyISAM AUTO_INCREMENT=2 DEFAULT CHARSET=utf8 COLLATE=utf8_unicode_ci

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: CiviCRM database error after 1.7 > 1.8 upgrade
August 23, 2007, 04:37:40 pm

You will need to work with Bryght tech support to figure out how to fix the MyISAM/InnoDB issue and get those tables in an InnoDB format

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

Neil Adair

  • I post occasionally
  • **
  • Posts: 78
  • Karma: 4
  • CiviCRM version: 4.5.8
  • CMS version: Drupal 7
  • MySQL version: MariaDB 10
  • PHP version: 5.5 FPM
Re: CiviCRM database error after 1.7 > 1.8 upgrade
August 23, 2007, 05:02:54 pm
Bryght suggested this command
mysql_convert_table_format --user='username' --password='password' --type=innodb databasename

Which does what it says. I'll try it later tonight.

Neil Adair

  • I post occasionally
  • **
  • Posts: 78
  • Karma: 4
  • CiviCRM version: 4.5.8
  • CMS version: Drupal 7
  • MySQL version: MariaDB 10
  • PHP version: 5.5 FPM
Re: CiviCRM database error after 1.7 > 1.8 upgrade
August 24, 2007, 12:20:19 am
I cloned our main site to a test site and converted the civicrm db to InnoDB tables with no problems.

When I try to repeat the procedure on the civicrm db for the main site I get the following error

$ mysql_convert_table_format --user='user' --password='password' --type=innodb v4mmp_crm
Can't convert civicrm_acl: Error Error on rename of './v4mmp_crm/#sql-7f59_3675' to './v4mmp_crm/civicrm_acl' (errno: 121)

When I try to restore the database from a backup of test I get the same error

$ gzip -d < /home/admin/backups/2007-08-23a-testv4mmp-crm-backup.sql.gz | mysql -uuser -ppassword v4mmp_crm

ERROR 1005 (HY000) at line 23: Can't create table './v4mmp_crm/civicrm_acl.frm' (errno: 121)

Any idea what may be causing this? The table checks out OK with mysqlcheck.

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: CiviCRM database error after 1.7 > 1.8 upgrade
August 24, 2007, 12:21:35 pm

Neil:

another alternative of doing the conversion is:

1. Do a mysql dump of the data only
2. create a new database
3. load the right civicrm_41.mysql
4. load the data file created in step 1

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

Pages: [1] 2
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • CiviCRM database error after 1.7 > 1.8 upgrade

This forum was archived on 2017-11-26.