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
--
http://stut.net
On Wed, Jun 4, 2008 at 6:44 PM, Stut <[EMAIL PROTECTED]> wrote:
On 4 Jun 2008, at 23:10, Stut wrote:
HELP!!
Our database just died. SHOW TABLE STATUS shows the message in the
status line for every table except the one that's MyISAM - the rest
are InnoDB.
Is there any way to rebuild the .frm files for the InnoDB tables?
Can anyone help? I know I haven't waited very long for an answer but
this is (obviously) a massive problem for us. Do I need to resort to
restoring the last full backup or is there a way to rebuild the .frm
files? I've googled my butt off but can't find anything related to
this.
Thanks.
-Stut
--
http://stut.net/
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
--
Help build our city at http://free-dc.myminicity.com !
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
