From: Ben Clewett Date: June 5 2008 8:04am Subject: Re: Incorrect information in file: './maindb/users.frm' List-Archive: http://lists.mysql.com/mysql/213212 Message-Id: <48479DF4.2030702@clewett.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit It could be the size of your InnoDB log files. Or something else which stops InnoDB running. I once changed server and by mistake changed the size of the innodb_log_file_size. The result was that InnoDB could not start and instead dissabled its self. Therefore every table I created became MyISAM. Check the error.log. If this is the case it will say.... Also do a SHOW ENGINS, may show something... Ben Stut wrote: > On 5 Jun 2008, at 00:41, Phil wrote: >> Just a very quick guess but is innobd engine running ? >> >> SHOW STATUS like '%inno%' > > Output shown below. I've just finished importing the backup file again > (into a different DB) and it's ignored the engine=innodb on each create > table and has used MyISAM instead. Trying to alter a table yields the > following... > > mysql> alter table users engine=InnoDB; > Query OK, 853097 rows affected, 1 warning (1 min 35.71 sec) > Records: 853097 Duplicates: 0 Warnings: 0 > > mysql> show warnings; > +---------+------+-----------------------------------------------+ > | Level | Code | Message | > +---------+------+-----------------------------------------------+ > | Warning | 1266 | Using storage engine MyISAM for table 'users' | > +---------+------+-----------------------------------------------+ > 1 row in set (0.00 sec) > > Show status output... > > mysql> SHOW STATUS like '%inno%'; > +-----------------------------------+--------+ > | Variable_name | Value | > +-----------------------------------+--------+ > | Com_show_innodb_status | 0 | > | Innodb_buffer_pool_pages_data | 0 | > | Innodb_buffer_pool_pages_dirty | 0 | > | Innodb_buffer_pool_pages_flushed | 0 | > | Innodb_buffer_pool_pages_free | 196608 | > | Innodb_buffer_pool_pages_latched | 0 | > | Innodb_buffer_pool_pages_misc | 0 | > | Innodb_buffer_pool_pages_total | 196608 | > | Innodb_buffer_pool_read_ahead_rnd | 0 | > | Innodb_buffer_pool_read_ahead_seq | 0 | > | Innodb_buffer_pool_read_requests | 0 | > | Innodb_buffer_pool_reads | 0 | > | Innodb_buffer_pool_wait_free | 0 | > | Innodb_buffer_pool_write_requests | 0 | > | Innodb_data_fsyncs | 0 | > | Innodb_data_pending_fsyncs | 0 | > | Innodb_data_pending_reads | 0 | > | Innodb_data_pending_writes | 0 | > | Innodb_data_read | 0 | > | Innodb_data_reads | 1 | > | Innodb_data_writes | 0 | > | Innodb_data_written | 0 | > | Innodb_dblwr_pages_written | 0 | > | Innodb_dblwr_writes | 0 | > | Innodb_log_waits | 0 | > | Innodb_log_write_requests | 0 | > | Innodb_log_writes | 0 | > | Innodb_os_log_fsyncs | 0 | > | Innodb_os_log_pending_fsyncs | 0 | > | Innodb_os_log_pending_writes | 0 | > | Innodb_os_log_written | 0 | > | Innodb_page_size | 16384 | > | Innodb_pages_created | 0 | > | Innodb_pages_read | 0 | > | Innodb_pages_written | 0 | > | Innodb_row_lock_current_waits | 0 | > | Innodb_row_lock_time | 0 | > | Innodb_row_lock_time_avg | 0 | > | Innodb_row_lock_time_max | 0 | > | Innodb_row_lock_waits | 0 | > | Innodb_rows_deleted | 0 | > | Innodb_rows_inserted | 0 | > | Innodb_rows_read | 0 | > | Innodb_rows_updated | 0 | > +-----------------------------------+--------+ > 44 rows in set (0.00 sec) > > Anyone have any ideas? > > Thanks. > > -Stut >