mysql cpsession & session
 

Hi.
Please tell me it's okay or not this Two files sql database or is there any possibility to repair these. I have VB 4.2.2 & php 5.2.17

cpsession] note: The storage engine for the table doesn't support repair

.session] note: The storage engine for the table doesn't support repair and

thanks

You can't repair them. You also should ever run the repair command unless a table is actually crashed. It'll do more harm than good.

thanks .. then what else should I do to repair sql database ?

Why do you think that those tables need to be repaired?

If you have a crashed table, then repair that one crashed table.

Why do you think those two tables need repair?

because think my sql database is corrupt these cause any problem or not ?

Why do you think it is?

I think because I tested my sql backup is corrupt cannot import or restore all sql ,for this reason I say this,

And what lead you to believe it is those tables, did it error out on them?
Perhaps the backup it's self is bad, how did you do the backup?
What is the size of the database?
How big is your forum, posts members etc?

Is new forum 1300 members. size database is 137MB


https://vborg.vbsupport.ru/external/2014/02/9.jpg

That is not a issue with the tables, it is a server side issue.

MySQL server gone away error explained
Reasons outlined at http://vbtechsupport.com/433/


++++++++++++++++++++++++++++++++

http://dev.mysql.com/doc/refman/5.1/en/gone-away.html
http://dev.mysql.com/doc/refman/5.1/...on-errors.html
http://dev.mysql.com/doc/refman/5.1/...arameters.html
http://dev.mysql.com/doc/refman/5.1/...ion-files.html
http://dev.mysql.com/doc/refman/5.1/...variables.html
[Updated 04/14/09.]

The most common reason for the MySQL server has gone away error

1. Is that the server timed out and closed the connection. By default, the server closes the connection after 8 hours or 28800 seconds if nothing has happened. You can change the time limit by setting the wait_timeout variable when you start mysqld via your server's /etc/my.cnf as well.

2. Another common reason to receive the MySQL server has gone away error is because you have issued a ``close'' on your MySQL connection and then tried to run a query on the closed connection. You can check that the MySQL hasn't died by executing mysqladmin version and examining the uptime.

i.e. to check mysql uptime, in shell as root user type:

mysqladmin -u root -p version

3. You can also get these errors if you send a query to the server that is incorrect or too large. If mysqld gets a packet that is too large or out of order, it assumes that something has gone wrong with the client and closes the connection. If you need big queries (for example, if you are working with big BLOB columns), you can increase the query limit by starting mysqld with the -O max_allowed_packet=# option (default 1M) or via max_allowed_packet variable in your /etc/my.cnf file and restarting mysql after you edited your /etc/my.cnf file. The extra memory is allocated on demand, so mysqld will use more memory only when you issue a big query or when mysqld must return a big result row

thank you all

Not a problem, glad to help. :)

Next time you post a issue, it would be best to provide as much information I'm your first post, so it would not take 11 posts to get to the proper solution.