Bug #12892 Application that calls MySQL db hangs due to "mysql_store_result()" error 1030
Submitted: 30 Aug 2005 20:54 Modified: 31 Aug 2005 6:44
Reporter: Vince Gallagher Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:4.1.7 OS:HP/UX (Hp-Unix)
Assigned to: CPU Architecture:Any

[30 Aug 2005 20:54] Vince Gallagher
Description:
This is occurring in a high volume production environment.
The code that is pasted below is the log of the calling application.
This is most likely an implementation/maintenance issue. Wondering if you could tell us where to start. Current fix is to "bounce" mysql...daily.

Code:-1100|dbiget:mysql_store_result() failed:Error 1030 (Got error 12 from storage engine)                                                           
Code:-1100|dbiget:mysql_store_result() failed:Error 1030 (Got error 12 from storage engine)                                                           
Code:-1100|dbiget:mysql_store_result() failed:Error 1030 (Got error 12 from storage engine)                                                           
Code:-1100|dbiget:mysql_store_result() failed:Error 1030 (Got error 12 from storage engine)                                                           
Code:-1100|mysql_query() failed:Error 1030 (Got error 12 from storage engine) 

How to repeat:
don't bounce mysql daily in our environment...

Suggested fix:
probably flushing/cleaning up log files, general maintenance...unsure where to start
[31 Aug 2005 6:44] Valeriy Kravchuk
We're sorry, but the bug system is not the appropriate forum for 
asking help on using MySQL products. Your problem is not the result 
of a bug.

Support on using our products is available both free in our forums
at http://forums.mysql.com and for a reasonable fee direct from our
skilled support engineers at http://www.mysql.com/support/

Thank you for your interest in MySQL.

Additional info:

Please, read http://bugs.mysql.com/how-to-report.php. We really need information on what exactly you did, what you expected to get and what the results you got.

my.cnf content, show variables etc. will also help, but a repeatable sequence of actions showing a bug is a must.

You may also try to use newer version - 4.1.7 is a bit old.