MySQL Forums
Forum List  »  InnoDB

ERROR 1033 (HY000): Incorrect information in file: .\db\table.frm'
Posted by: Amin Taheri
Date: November 05, 2007 04:24PM

Hello,

We are having this problem:

mysql> use database
select * from database.table1
ERROR 1033 (HY000): Incorrect information in file: '.\database\table1.frm'

I installed a new copy of 5.0.22-community-nt-log and restored a backup of the data directory and the my.ini file

Service starts fine, but I cant read any of the innodb tables.

I then run the following:
C:\Program Files\MySQL\MySQL Server 5.0\bin>mysqlbinlog.exe --database=database ..\data\Binary_log.000021 | mysql -umy_user_name -p -b
enter password: **********************

I get this once
ERROR 1017 (HY000) at line 14: Can't find file: 'hits' (errno: 2)

Then this line appears a bunch of times
mysqlbinlog.exe: Error writing file 'UNOPENED' (Errcode: 22)



I have also tried
C:\Program Files\MySQL\MySQL Server 5.0\bin>mysqlbinlog.exe -t ..\data\Binary_log.000021 | mysql -umy_user_name -p -b


and got the same results

if I do not do the pipe I get back a lot of data printed to the screen. A bout 750MB worth in this one log file alone.


So I tried it again with -f, but this time I dropped the database first.

drop database db

C:\Program Files\MySQL\MySQL Server 5.0\bin>mysqlbinlog.exe -f --database=db ..\data\Binary_log.000021 | mysql -umy_user_name -p -b


now I get this:
ERROR 1289 (HY000) at line 1861500: The 'InnoDB' feature is disabled; you
ySQL built with 'InnoDB' to have it working
mysqlbinlog.exe: Error writing file 'UNOPENED' (Errcode: 0)
mysqlbinlog.exe: Error writing file 'UNOPENED' (Errcode: 22) <- this line is repeated about 20 times

I have innoDB enabled in mysql - both mysql admin GUI and my.inf have it enabled.

I do a "show variables like 'innodb%';" in mysql and I get this:

+---------------------------------+------------------------+
| Variable_name | Value |
+---------------------------------+------------------------+
| innodb_additional_mem_pool_size | 2097152 |
| innodb_autoextend_increment | 8 |
| innodb_buffer_pool_awe_mem_mb | 0 |
| innodb_buffer_pool_size | 8388608 |
| innodb_checksums | ON |
| innodb_commit_concurrency | 0 |
| innodb_concurrency_tickets | 500 |
| innodb_data_file_path | ibdata1:10M:autoextend |
| innodb_data_home_dir | |
| innodb_doublewrite | ON |
| innodb_fast_shutdown | 1 |
| innodb_file_io_threads | 4 |
| innodb_file_per_table | OFF |
| innodb_flush_log_at_trx_commit | 1 |
| innodb_flush_method | |
| innodb_force_recovery | 0 |
| innodb_lock_wait_timeout | 50 |
| innodb_locks_unsafe_for_binlog | OFF |
| innodb_log_arch_dir | |
| innodb_log_archive | OFF |
| innodb_log_buffer_size | 1048576 |
| innodb_log_file_size | 10485760 |
| innodb_log_files_in_group | 2 |
| innodb_log_group_home_dir | .\ |
| innodb_max_dirty_pages_pct | 90 |
| innodb_max_purge_lag | 0 |
| innodb_mirrored_log_groups | 1 |
| innodb_open_files | 300 |
| innodb_support_xa | ON |
| innodb_sync_spin_loops | 20 |
| innodb_table_locks | ON |
| innodb_thread_concurrency | 10 |
| innodb_thread_sleep_delay | 10000 |
+---------------------------------+------------------------+
33 rows in set (0.20 sec)




What can I do to be able to use my database again?



Edited 1 time(s). Last edit at 11/05/2007 04:50PM by Amin Taheri.

Options: ReplyQuote


Subject
Views
Written By
Posted
ERROR 1033 (HY000): Incorrect information in file: .\db\table.frm'
15006
November 05, 2007 04:24PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.