Hi,

I’m using MYSQL version 3.22.24 trial on WinNT 4.0. And I started mysqld with
the following options:

Mysqld-nt --big-tables --standalone --datadir=.\Database --skip-new
--skip-grant-tables -O max_connections=300 -O max_allowed_packet=30M

and I usually ran into these problems :

a.. When I use more than 50 JDBC connections to insert records
simultaneously into a DB & one connection to query (not a complex query with
limit records) the DB, sometimes the query connection runs OK. But sometimes, it
appears to hang while consuming 100% CPU until I decided to terminate mySQL by
using Windows NT Task Manager. While mySQL was hung up, I used MySQLWinAdmin to
list pending SQL processes, I observed a list of queries in locked state. Using
EXPLAIN to verify the SQL syntax, I found no problems with my SQL statements. a.. After mySQL was terminated by force as mentioned above, the database was
in error (or damaged). I had to use isamchk –s & isamchk –o to repair the DB so
it can be useful again. After the repair, the number of records in the DB was
increased to almost twicwe as many (from 109000 records to 197000). The
additional records (resulting trom the repair) contains unrecognizable (dirty)
data. a.. Finally, I tried to restart my MYSQL servers (two servers, both can read
& update a DB on a shared drive on one of them) to run all the same data with
above options (disable –skip-locking one). All seems OK, then the server
(sharing the drive containing the DB) ran into this problem :

( enclosed file attached )

I would appreciate if anybody can help me with the following questions:

- Are there anything wrong with my start options ?

a.. How to recover the DB after it crashed (so that we can eliminate extra
records with dirty data as described above) ? b.. And what happened with the sharing server when the above error messages
popped up ? Once again, thank you for your time, and help.