Sorry, should've sent an update last night. That was indeed the
problem. It's fixed now.
Thanks to everyone who helped.
-Stut
--
http://stut.net/
On 5 Jun 2008, at 09:04, Ben Clewett wrote:
It could be the size of your InnoDB log files. Or something else
which stops InnoDB running.
I o
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 M
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 ins
Just a very quick guess but is innobd engine running ?
SHOW STATUS like '%inno%'
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 ta
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
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?
-Stut
--
http://stut.net/
--
MySQL General Mailing List
For list arc
