On Apr 6, 2005, at 4:47 PM, Frank Bax wrote:
It seems the "bad file number" error was caused by MySQL trying to
have more than 128 files open at one time. This was "fixed" by
changing MySQL startup, but the "fix" would not have been needed if
MySQL were to close open files after some period of
Hello.
See:
http://dev.mysql.com/doc/mysql/en/table-cache.html
Frank Bax <[EMAIL PROTECTED]> wrote:
> It seems the "bad file number" error was caused by MySQL trying to have
> more than 128 files open at one time. This was "fixed" by changing MySQL
> startup, but the "fix" would not
It seems the "bad file number" error was caused by MySQL trying to have
more than 128 files open at one time. This was "fixed" by changing MySQL
startup, but the "fix" would not have been needed if MySQL were to close
open files are some period of "no activity to a table" - does MySQL ever
clo
According to perror:
perror 9
Error code 9: Bad file number
This is an operating system error code:
http://dev.mysql.com/doc/mysql/en/operating-system-error-codes.html
Out of curiosity, have you tried running myisamchk or some CHECK TABLE
commands yet?
http://dev.mysql.com/doc/mysql/en/table-ma
At 10:07 AM 4/5/05, Frank Bax wrote:
At 04:27 PM 4/4/05, Frank Bax wrote:
Cannot execute query.
Can't find file: './donor/list_lst.frm' (errno: 9)
- -
I got the same error last week on a different table. Today I notice that
there is a table in another database on same system producin
At 04:27 PM 4/4/05, Frank Bax wrote:
Cannot execute query.
Can't find file: './donor/list_lst.frm' (errno: 9)
- -
I got the same error last week on a different table. Today I notice that
there is a table in another database on same system producing the same
error. I attempted to ac
Hello.
I can't find a similar bug in the bug database (if you could search
more, please do it). As far as I know the OpenBSD-current has MySQL 4.0.24
in it's ports tree. Upgrading most probably will solve the problems.
Frank Bax <[EMAIL PROTECTED]> wrote:
> Cannot execute query.
>
