MYSQL Error Can't Access Sitemap

Permalink
Client tried to link to internal page and got a WPOD.

Here's the full error report:
An unexpected error occurred.
mysql error: [145: Table './seattler_src/PageSearchIndex' is marked as crashed and should be repaired] in EXECUTE("select p1.cID, pt.ctHandle from Pages p1 left join Pages p2 on (p1.cPointerID = p2.cID) left join PageTypes pt on (pt.ctID = (if (p2.cID is null, p1.ctID, p2.ctID))) left join PagePaths on (PagePaths.cID = p1.cID and PagePaths.ppIsCanonical = 1) left join PageSearchIndex psi on (psi.cID = if(p2.cID is null, p1.cID, p2.cID)) inner join CollectionVersions cv on (cv.cID = if(p2.cID is null, p1.cID, p2.cID) and cvID = (select max(cvID) from CollectionVersions where cID = cv.cID)) inner join Collections c on (c.cID = if(p2.cID is null, p1.cID, p2.cID)) left join CollectionSearchIndexAttributes on (CollectionSearchIndexAttributes.cID = if (p2.cID is null, p1.cID, p2.cID)) where 1=1 and p1.cParentID = '0' and (p1.cIsTemplate = 0 or p2.cIsTemplate = 0) and (p1.cID not in (5,6,7,8,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,43,44,45,46,47,48,49,50,51,52,53,54,55,85,86,87,88,89,90,91,92,180) or p2.cID not in (5,6,7,8,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,43,44,45,46,47,48,49,50,51,52,53,54,55,85,86,87,88,89,90,91,92,180)) ")

Has anyone ever seen this? What should I do?

Also, I'm a complete virgin when it comes to direct editing of MYSQL, should I be nervous?

Thanks!

Veronikan
 
mdzoidberg replied on at Permalink Best Answer Reply
mdzoidberg
You just need to repair the table, check out this link with step by step instructions with images on how to repair tables via phpMyAdmin.

http://paulstamatiou.com/how-to-quickie-repair-mysql-tables-in-phpm...


Cheers.
Veronikan replied on at Permalink Reply
Veronikan
Thank you!
mdzoidberg replied on at Permalink Reply
mdzoidberg
Great, if that work can you mark my answer? regards.
Veronikan replied on at Permalink Reply
Veronikan
It did indeed work and quickly.
Veronikan replied on at Permalink Reply
Veronikan
Almost. The host upgraded MYSQL last night, table was damaged, they will repair.