Hello all, I'm running into an error which seems to be fairly uncommon. Hopefully somebody can give me some insight!
In the monthly run for my accounting software, I am doing a fairly heavy query with a few joins, some date arithmetic, a 'having' condition and finally an 'order by'. When mysqld has been running for some time (a day or so), this query produces the following error: ERROR 1030 (HY000): Got error 12 from storage engine Strangely, this problem does not appear when mysqld is restarted and I retry the query. When I wait a day, the error starts to appear again. I've already found that by removing the final "order by" from the query, the error does not occur. The result is 1107 rows by 24 columns (a few varchars and the rest is all integer). The whole result fits in the querycache, it's not unusually large. The server is running 4.1.10a on FreeBSD 5.4-RELEASE-p6. It has 2GB physical RAM of which 1.2GB is available (free + buffers) to mysqld at almost all times. mysqld's size is 516MB. There's 1GB free on the drive used for filesorts. I've guessed setting max_heap_table_size=256M but this did not help. Because I can only test one variable change per day, I will be quickly running out of options before january 1st :) Any ideas would be appreciated! Kind regards, Walter Hop Transip BV -- Transip BV | http://www.transip.nl/ Hoogwaardige Innovatie | Aangename Zekerheid -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
