can't explain mysql crash

[J-F Portala]

Hi listers,
I am completly lost with a crash problem.
I have these messages in the mysql.log file.

121206 17:43:27 [ERROR] wampmysqld: Incorrect key file for table
'.\ducret_bdd\production.MYI'; try to repair it
121206 17:43:54 [ERROR] Error writing file '(null)' (errno: 9)
121206 17:43:54 [Note] Failed to delete file '.\mysql-bin.000001'
121206 17:43:54 [Note] Failed to delete file '.\mysql-bin.000002'
121206 17:43:54 [Note] Failed to delete file '.\mysql-bin.000003'
121206 17:43:54 [Note] Failed to delete file '.\mysql-bin.index'
121206 17:43:54 [ERROR] Could not use mysql-bin for logging (error 22).
Turning logging off for the whole duration of the MySQL server process. To
turn it on again: fix the cause, shutdown the MySQL server and restart it.
121206 17:44:00 [ERROR] wampmysqld: Table '.\ducret_bdd\noyaumes' is marked
as crashed and should be repaired

The database is 72Mb weight. There is more than 100Gb free disk space.
I have recorded in text file all queries involving update , delete or
insert. All the queries are reliable.
I dont' know what to do to find the error. I have put database on another
disk partition.
I am working with wamp.

errno: 9 is bad number file

My application is based on 2 pcs. One is the server and both have C++
applications which are making queries through ODBC to mysql server.
The 2 PCs are working with XP sp3.

Repair operation is generally working but I have lost 3 times all the data
of several tables during repairing.

Any help will be greatly appreciated.

Thank you
Jeff

[Brian Cryer]

"J-F Portala" <jf.po...@free.fr> wrote in message
news:50c1b7c3$0$1385$ba4a...@reader.news.orange.fr...

I can't help with your specific error sorry, but, a few things to check just
incase:

1. Do you have any errors in the Windows System event log? Given your
comments, I wonder whether this is not the first time you've had issues (in
general you shouldn't ever need to repair a database), and I'm wondering
whether there might be an underlying hardware issue. If there is a hardware
issue then it should be recorded in the Windows System event log.

2. Try it with anti-virus turned off. I had an issue once with a MySQL
database which used to crash occasionally and it turned out to be the
anti-virus. Don't leave your anti-virus off, just turn it off when you next
try a repair to eliminate it from the equation. In my case I just had to
tell my anti-virus to ignore the folders being used by MySQL.

Hope you get it resolved.
--
Brian Cryer
www.cryer.co.uk/brian

[J-F Portala]

I thank you for this idea.
But unfortunately, there are no interesting information in the differet evt
logs.
I retrieve mysql.log error messages.

I will look at the antivirus parameters but I doubt I can exclude folders.

Thank you for your help

Jeff


"Brian Cryer" <not....@localhost.invalid> a �crit dans le message de news:
k9sds9$9j0$1...@dont-email.me...