By Reflexe on

Hello,

Recently my host changed settings on the server (I run Drupal and CiviCRM on a shared solution) and my DB got broken.

The issue seems related to InnoDB.

Result = my site is broken

The host does not give me a solution so I am looking for someone who can help me with this.

The error in the DB tables is:

#1033 - Incorrect information in file: './*_civicrm/system.frm'

In several (almost all tables)

I am not a DB expert... but I would like to repair the DB and have the site running again.

Thank you

⋅ Categories: Drupal 5.x

Comments

criznach’s picture

criznach commented

Do you have access to your mysql configuration? If not, do you have database backups?

http://www.trailheadinteractive.com

Reflexe’s picture

Reflexe commented

I do have access to phpMyAdmin,

But the host just flushed the tables and made a folder backup... i just hope I will be able to recover the information.

Thank you

WebbyWorker’s picture

WebbyWorker commented

HI Reflexe,

I would be willing to take a crack at it, all for FREE to evaluate what the issue is possible solutions.

I have dealt with similar issue before with Drupal and CiviCRM on other clients sites.

-Thanks

Reflexe’s picture

Reflexe commented

Hello WebbyWorker,

Here is the state of things:

The host flushed the DB (without prior notification) and made a backup of the folders...

I am worried now about recovering the contents (pages, stories, blog posts and so).

So, yes if you could help me I would be very grateful

Thank you

LiquidWeb’s picture

LiquidWeb commented

You are lucky in some way if the problem is only with frm file because frm file stores structure information about that table. Try to replace that file with a clean one from a clean install (You need root access to do that)

martinhansell’s picture

martinhansell commented

Hi,

I have the same problem as our friend... and I really don't want to loose everything if avoidable.

I edited my my.cnf file while installing the Perseus Java application which wanted me to add in this line...

innodb_data_file_path=ibdata1:500M

I also amended the GLOBAL VARIABLE wait_timeout to a larger number, but this shouldn't affect my other tables?

I have many databases/CRMs that I am testing under MySQL. Why is it that only the Drupal tables were affected, not the Joomla, CiviCRM, Wordpress etc...? I am not looking to compare, only that might lead me to understand where the fix lies?

Looking in further it seems that only the core Drupal tables were affected, not the additional modules. Does that tell us anything?

So how to I go about obtaining a .frm files? Create a new site that looks like the old one?

And once I have them, do I just copy them from the new database into the old one?

Many thanks
Martin

Reflexe’s picture

Reflexe commented

I am really upset, files could not be recovered and so content. I have to start over.

Thanks for all who replied

yasheshb’s picture

yasheshb commented

I had a similar problem earlier.

http://www.mysqlperformanceblog.com/2006/09/29/what-to-tune-in-mysql-ser...
http://forums.mysql.com/read.php?34,177212,234851#msg-234851
http://forums.mysql.com/read.php?22,32004,32014
http://dschneller.blogspot.com/2007/09/error-1033-hy000-on-innodb.html

hth

yashesh bhatia

Yashesh Bhatia

martinhansell’s picture

martinhansell commented

Thanks yasheshb!!! I think that might just crack it... It seemed "logical" that it couldn't have been a total "crash" crash, and that it must have been "something I did" - GIGO !! But this has pointed me to the likely cause for my own case with...

http://dschneller.blogspot.com/2007/09/error-1033-hy000-on-innodb.html

...and I will amend this post soon enough to let you know the final outcome.