mysql-server reinstall - configuration.frm error

[crchi]

I had to reinstall mysql-server. Everything else is working fine but when I try to open the store I get this error:

 

1033 - Incorrect information in file: './catalog/configuration.frm'

 

select configuration_key as cfgKey, configuration_value as cfgValue from configuration

 

[TEP STOP]

 

 

Can anyone help? The mysql user and password is correct, and I can see the database for the store in phpmyadmin.

 

Thanks

Susan

[kgt]

In phpMyAdmin, you need to select the table configuration, then at the bottom, there's a dropdown list with the text "With Selected:" You need to choose "Repair table."

[crchi]

In phpMyAdmin, you need to select the table configuration, then at the bottom, there's a dropdown list with the text "With Selected:" You need to choose "Repair table."

 

I don't have that option in the With Selected dropdown menu. Not sure why. Using phpmyadmin 2.2.7.

 

Isn't there something I can do at the command line? I've been looking everywhere for this info.

[kgt]

From the mysql command line:

 

repair table configuration;

[crchi]

From the mysql command line:

 

repair table configuration;

 

I'm worried I'm running out of options here. This is what happened when I tried the above:

 

catalog.configuration | repair | error | Can't find file: './catalog/configuration.frm' (errno: 13) |

[kgt]

I'm worried I'm running out of options here. This is what happened when I tried the above:

 

catalog.configuration | repair | error | Can't find file: './catalog/configuration.frm' (errno: 13) |

 

Error 13 is 'permission denied'. Make sure the mysql server has permissions on all the database files.

[crchi]

Error 13 is 'permission denied'. Make sure the mysql server has permissions on all the database files.

 

Another error when I try the repair (since it's still not working properly - although I changed all the permissions).

 

| catalog.configuration | repair | error | Incorrect information in file: './catalog/configuration.frm' |

 

And when I go into to mysql and specify the database to use it tells me it can't find fields in any of the tables.

[kgt]

You're going to have to do some repairing. Read the MySQL manual:

 

http://dev.mysql.com/doc/mysql/en/repair.html

 

You're going to need to shutdown the mysqld server and run myisamchk. The link above has more information.

 

Alternatively, you can delete the database, and recreate it from a backup (a sql dump file).

[crchi]

You're going to have to do some repairing. Read the MySQL manual:

 

http://dev.mysql.com/doc/mysql/en/repair.html

 

You're going to need to shutdown the mysqld server and run myisamchk. The link above has more information.

 

Alternatively, you can delete the database, and recreate it from a backup (a sql dump file).

 

Unfortunately, the people that set up the server and said they were backing up from our main office, did not in fact back up. I am stuck with no backup.

 

Before I removed and reinstalled using yum, I copied the database over to my Windows machine using SSH. After re-installing mysql I then copied it over to the mysql directory. I can see now that it does have records in it, but I still get the same error for every table:

 

error : Incorrect information in file: './catalog/zones.frm'

catalog.zones_to_geo_zones

 

This is from running mysqlcheck. I tried all the repairs. I don't know where I went wrong or if there is any way to recover. Rebuilding this is going to be a real drag.

 

Do I have any options left?

[kgt]

Are you 100% absolutely super-duper sure you reinstalled the same version of MySQL?

 

 

Make sure you do this part:

 

Stage 4: Very difficult repair

 

You should reach this stage only if the .frm description file has also crashed. That should never happen, because the description file isn't changed after the table is created:

 

1. Restore the description file from a backup and go back to Stage 3. You can also restore the index file and go back to Stage 2. In the latter case, you should start with myisamchk -r.

2. If you don't have a backup but know exactly how the table was created, create a copy of the table in another database. Remove the new data file, then move the .frm description and .MYI index files from the other database to your crashed database. This gives you new description and index files, but leaves the .MYD data file alone. Go back to Stage 2 and attempt to reconstruct the index file.

 

I doubt step 1 will help you, but step 2 might. You should be able to recover the table structure. You need to get the .sql files for your version of OSC and build empty tables. Then you need to get the .sql files for all the contributions you have installed and make sure your database tables are the same structure as they should be. Create this in a new database, then move those files to the corrupted OSC data directory. You will be overwriting the existing files. Then use

 

myisamchk -r

or

myisamchk --safe-recover

[crchi]

It worked it worked it worked!! Oh man, what a weight off my shoulders. I was thinking I'd never get this fixed. I had made a backup of the database once I had successfully created the store, but I didn't have the data in it yet. So, I was able to re-create the structure, copy the good .frm and .MYI files over to the crashed db, then use myisamchk -r to repair it. Voila!

 

Thank you SO much for your help!!

[kgt]

Wonderful! I'm glad you didn't have to rebuild. I've been stuck in situations like those before.