zen_db_cache' is marked as crashed and should be repaired

Hi,

I am seeing this error in one of my clients' sites. I have tried doing a repair on the table (many times) but it hasn't fixed the problem.

What I would like to know is - could I simply delete it and recreate it? Is that going to cause any other problems?

TIA

If you have good full regular backups, and you are confident in managing database tables and content, you could try that. It would be prudent to contact the hosting company if you are uncertain.

DrByte:

If you have good full regular backups, and you are confident in managing database tables and content, you could try that. It would be prudent to contact the hosting company if you are uncertain.Message to DrByte ... even though you have dodgy, irregular backups, it would be prudent to make contact with your bed after spending a day in uncertain company!

DrByte:

If you have good full regular backups, and you are confident in managing database tables and content, you could try that. It would be prudent to contact the hosting company if you are uncertain.

Yes, I am confident working with MySQL databases, I have designed many sites that use them.

I posed the question because I am unsure of the purpose of this particular table. It appears to be just a temporary storage of visitor data (perhaps?) so losing the content wont affect anything else - do you know if this is correct?

kuroi:

Message to DrByte ... even though you have dodgy, irregular backups, it would be prudent to make contact with your bed after spending a day in uncertain company!

Message to uncertain company ... sleep is well advised to all parties involved regardless of backup status :smartalec:

upollo:

Yes, I am confident working with MySQL databases, I have designed many sites that use them.

I posed the question because I am unsure of the purpose of this particular table. It appears to be just a temporary storage of visitor data (perhaps?) so losing the content wont affect anything else - do you know if this is correct?

The db_cache table is used to store cached query results if your store's setup is configured to cache to the database (see configure.php). You can safely delete and recreate the table if you know what you're doing with managing databases (many readers of this forum dabble where they ought not to). Naturally I suggest doing so during a less-busy time to minimize disruption to your users.

upollo:

Hi,

I am seeing this error in one of my clients' sites. I have tried doing a repair on the table (many times) but it hasn't fixed the problem.

What I would like to know is - could I simply delete it and recreate it? Is that going to cause any other problems?

TIA
Tia, what's the actual error?

Note to DrByte: sleepy people will often miss omissions like this...

BlindSide:

Note to DrByte: sleepy people will often miss omissions like this...

Amazing how easily one can be made sleepy whilst techies talk code for hours on end.

upollo:

What I would like to know is - could I simply delete it and recreate it? Is that going to cause any other problems?

TIA

BlindSide:

Tia, what's the actual error?BTW, I think you must need some sleep yourself. I suspect "TIA" means "Thanks in Advance", and does not necessarily denote the first name of the poster :smartalec:

Even sleepy doctors catch that :eek:

Excellent, thanks DrByte. That has fixed the problem :smile:

DrByte:

I suspect "TIA" means "Thanks in Advance", and does not necessarily denote the first name of the poster

Correct :smile:

So glad that the good doctor was able to help you and all thoughts of malpractice suits can now be put to bed. :sleep1:

:sleep1:

just received this same error, deleted the table and rebuilt the table in sql and all is better again

however why/how did it crash, we have the latest security patches installed but still it has happened

Security and a crashed database table are two different things ...

Sometimes, there can be an issue with the database causing issues like this.

You might check with your hosting provider to see if they have any ideas of what might have happened.

Fortunately, this particular table crash has a quick and easy solution to fixing the table ... :lamo: