phpmyadmin problems

Worker Joined: Mar 31, 2004 Posts: 111

When I log into myphpadmin and look at the tables i spot somethin very unusual on table nuke_bbserch_wordmach

look at this picture

does anybody know what the problem is?

by the way my forum is not working I assume it is because of that

Code:

Could not insert new word matches





DEBUG MODE





SQL Error : 1016 Can't open file: 'nuke_bbsearch_wordmatch.MYI'. (errno: 145)





INSERT INTO nuke_bbsearch_wordmatch (post_id, word_id, title_match) SELECT 3402, word_id, 0 FROM nuke_bbsearch_wordlist WHERE word_text IN ('azsxsazsxa')





Line : 252


File : /home/bosankan/public_html/kemo/includes/functions_search.php

that is the error help please

Site Admin/Owner Joined: Aug 27, 2002 Posts: 17088

Run a REPAIR on that table and then on your database.

Posted: Sun Oct 23, 2005 11:36 pm

you mean to repair the table fiirst and than the database?

if that is it i did that and the forum would work for about 15 posts and it wold give me the same error again and i wopuld do the same thing repair the table and than the database and after 10 - 15 posts an error would come up

Posted: Sun Oct 23, 2005 11:38 pm

could it be that i have a problem with my server? becuse it is shared?

Posted: Sun Oct 23, 2005 11:40 pm

Yes. Have you repaired the entire database? if so and the error keeps returning, then your disk space may be full or close to it.

Posted: Sun Oct 23, 2005 11:43 pm

ok yes i did repair the whole database and like I said after 10-15 posts on the forum it closes on me one time i got the messege it looked like thhis

DEBUG MODE

SQL Error : 1016 not enough memory: 'nuke_bbsearch_wordmatch.MYI'. (memory needed 1989899)

somethinng like that

Posted: Sun Oct 23, 2005 11:46 pm

This is an issue for your host. It would seem that they may be out of disk space and the swap isn't able to handle the memory overflow. Contact them.

Posted: Sun Oct 23, 2005 11:47 pm

thank you very much raven Smile

registered · Posted: Mon Oct 24, 2005 3:08 am

I've had problems like that before, and it turned out to be cross-linked and/or corrupt tables. Repairing the tables fixed the problem[s] most of the time, but sometimes I had to delete the tables and restore them from a backup.

Anyway, like Raven said, I'd contact your host. If I remember correctly, my problems were due to a botched MySQL upgrade, and something like that may be in play here...