jtablesession:tore Failed DB function failed with error number 145

"jtablesession:tore Failed
DB function failed with error number 145
Table '.\saharareports\jos_session' is marked as crashed and should be repaired SQL=INSERT INTO `jos_session` ( `session_id`,`time`,`username`,`gid`,`guest`,`client_id` ) VALUES ( '3fbrbb5n2nrrl26imoaih872a0','1240991425','','0','1','0' )"

Well, this is the session problem. I think that Joomla have unnecessary indexes on jos_session table. This table is very often overhead, and thus giving you a problem.
Possible causes:

1. Flooding. (Check your http access logs for access IP's, and your PHP error logs). Solution: Try dropping the time out down temporally to a lower value, to see if the sessions clear or not.

2. SEF . If your site has a lot of visitors table jos_session can accumulate substantial overhead. And if you use default SEF, some 404 pages can make some bots to enter into loop, and those bots gives you a huge session overhead.

Solutions:

If you want to make your Joomla site runs faster, then you might think about these following options:

1. Don't use site statistics from within Joomla. (Enabling statistics through your site configuration just adds extra MySQL queries and increases server loads. If you need stats, see if your host will provide them for you (Awstats, Webalizer, etc) or use Google statistics.

2. Don't use SEF URL's unless you really need to. (Search engines don't care if your URL's are the standard Joomla URL's or SEF URL's)

3. If you don't need to use an editor, remove it. (Many people use external editors and cut n paste their content. If you are using Joomla in this way, remove the editor and set your configuration to NO WYSIWYG Editor - this improves the performance and speed of the administrator backend.)

4. Do try using gzip and caching (if your server allows gzip compression, and most do) you can turn these on through your administrator configuration options.

5. Use phpMyAdmin or other MySQL management tool to periodically optimize your MySql database tables. When records are deleted, MySql does not reclaim unused space until the tables are optimized.

 

ghogilee