Description:
I have a small sessions table with two fields, BIGINT and VARCHAR(30) to keep track of web sessions. I insert a record when a user's session starts and delete the record on session end. The table crashes about twice a week making it impossible for users to use the web site. myisamchk -r usually does not correct the problem. The result of myisamchk -s gives messages like:
MyISAM file session.MYI
Warning: Table is marked as crashed
Warning: Size of datafile is: 372 Should be: 72
Error: Reord-count is not ok: is 11 Should be 12
'session.MYI' is corrupted
I sometimes get a message like:
Error: Wrong bytesec: 255-255-255 at linkstart: 40
(not sure about word linkstart)
I am accessing the table from an ASP page using VBScript, ADO and MyODBC version 3.51.06. I am using a DSN ODBC data connection. I have two other tables that only get updates and inserts. These do not seem to crash. I am closing the reset set and db connection in each ASP page.
I did not specify the table type when the tables were created assuming they would be myisam tables. When I "SHOW TABLE STATUS", all table types are shown as myisam tables. When I examine the log, I see the message "InnoDB Started". I do not understand why InnoDB is involved. I have a very minimal my.ini file (no InnoDB files specified). I am also using mysqld-max-nt server. I have not applied any patches.
How to repeat:
I do not know how to repeat.
