MySQL error for mdl_cache_text

MySQL error for mdl_cache_text

by David Day -
Number of replies: 2

Hi All MySQL experts!

I have a problem with my Moodle 1.4.3 box running on Win 2k3 server under IIS6 with MySQL 4.1 and PHP v4... I am getting thousands of log errors with event no. 100 claiming;

C:\Program Files\MySQL\MySQL Server 4.1\bin\mysqld-nt: Can't open file: 'mdl_cache_text.MYI' (errno: 145)

For more information, see Help and Support Center at http://www.mysql.com.

When I go into MySQL Administrator I note that the table is missing from the Moodle database. I've tried both the REPAIR TABLE and myisamchk --safe-recover commands but to no avial as both claim there is no such table!

The funny thing is that the Moodle environment does not seem to be effected at all. Any ideas on how to fix these errors? Any info what has caused this disaster? I have had a few unexpected power outages in the last 3 weeks or so _ I'm guessing this table disappeared during one of these and never came back :->

Any help would be much appreciated!

Regards

David Day :->

Average of ratings: -
In reply to David Day

Re: MySQL error for mdl_cache_text

by Martin Dougiamas -
Picture of Core developers Picture of Documentation writers Picture of Moodle HQ Picture of Particularly helpful Moodlers Picture of Plugin developers Picture of Testers
I'm sure it was the blackouts. REPAIR TABLE should have fixed it, (were you looking at the wrong database?)

Anyhow, don't worry, it's not a crucial table, so you can delete it entirely.

To recreate it, issue this SQL using the mysql client or phpmyadmin:

CREATE TABLE `mdl_cache_text` (
`id` int(10) unsigned NOT NULL auto_increment,
`md5key` varchar(32) NOT NULL default '',
`formattedtext` longtext NOT NULL,
`timemodified` int(10) unsigned NOT NULL default '0',
PRIMARY KEY (`id`),
KEY `md5key` (`md5key`)
) TYPE=MyISAM COMMENT='For storing temporary copies of processed texts';


Average of ratings:Useful (1)
In reply to Martin Dougiamas

Re: MySQL error for mdl_cache_text

by David Day -

Hi Martin

Thanks for the lead... yes I had set the right database ..but ... please don't laugh too loud .. I hadn't spelt the work 'cache' properly... yes there is an 'e' on the end!

Now everything back to purring along normally!

Thanks,  David.