By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,105 Members | 2,541 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,105 IT Pros & Developers. It's quick & easy.

CONSTANT corruption on myISAM (4.0.20a w32)

P: n/a
mySQL (4.0.20a win32), dual amd2200 machine, 4 gigs of DDR ECC memory.

I have a series of 33 tables, identical in structure : (field names
shortened)

CREATE TABLE `dbtable1` (
`FS` varchar(254) NOT NULL default '',
`NAM` varchar(254) NOT NULL default '',
`H` int(11) NOT NULL default '0',
`SIZ` int(11) default NULL,
`R` char(1) default NULL,
`CI` varchar(254) default NULL,
`AV` char(1) default NULL,
`CL` int(11) default NULL,
`BW` int(11) default NULL,
`TS` timestamp(14) NOT NULL,
`CO` blob,
`AT` varchar(254) default '',
`NS` varchar(254) default '',
`NL` varchar(254) default NULL,
PRIMARY KEY (`FS`),
KEY `IDX_TS` (`TS`),
KEY `IDX_H` (`H`),
KEY `IDX_R` (`R`,`FS`)
) TYPE=MyISAM MAX_ROWS=100000000;

The tables are constantly going corrupt at random, IE : 'Can't open file
*.MYI (errno : 145)'

My understanding is that if the server is shut down incorrectly it can cause
this. The server has remained up and stable the whole time.

Also, if the table is closed incorrectly..? Is there any way to tell from
logs IF and WHEN this may be happening so I can figure out the source of
this constant corruption. When using ado/odbc do I have to tell the
connection to wait for anything??? My suspicion is it is happening on
deleting 1 record... not completely sure though...

HINT : Whenever I repair extended on a table, it nearly always says
'Duplicate key records' and it fixed the number of rows to 2 or 3 less (-)
than what it thought....

I did increase my key buffer to 1000, and sort buffer size = 2, other than
that the ONLY thing I changed was the network simultaneous connections to
200, are there other parameters I need to change to accommodate more memory
and more connections?

Could the memory be causing these errors, hardware, configuration? mySQL
bugs??
H E L P!!! ----ANY help on what to look for would be greatly appreciated.

-Craig
cs********@hotmail.com
Jul 20 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
"Craig Stadler" wrote:
mySQL (4.0.20a win32), dual amd2200 machine, 4 gigs of DDR ECC memory.
I have a series of 33 tables, identical in structure : (field names
shortened)

CREATE TABLE `dbtable1` (
`FS` varchar(254) NOT NULL default ’’,
`NAM` varchar(254) NOT NULL default ’’,
`H` int(11) NOT NULL default ’0’,
`SIZ` int(11) default NULL,
`R` char(1) default NULL,
`CI` varchar(254) default NULL,
`AV` char(1) default NULL,
`CL` int(11) default NULL,
`BW` int(11) default NULL,
`TS` timestamp(14) NOT NULL,
`CO` blob,
`AT` varchar(254) default ’’,
`NS` varchar(254) default ’’,
`NL` varchar(254) default NULL,
PRIMARY KEY (`FS`),
KEY `IDX_TS` (`TS`),
KEY `IDX_H` (`H`),
KEY `IDX_R` (`R`,`FS`)
) TYPE=MyISAM MAX_ROWS=100000000;

The tables are constantly going corrupt at random, IE :
’Can’t open file
*.MYI (errno : 145)’

My understanding is that if the server is shut down incorrectly it can cause
this. The server has remained up and stable the whole time.

Also, if the table is closed incorrectly..? Is there any way to tell from
logs IF and WHEN this may be happening so I can figure out the source of
this constant corruption. When using ado/odbc do I have to tell the
connection to wait for anything??? My suspicion is it is happening on deleting 1 record... not completely sure though...

HINT : Whenever I repair extended on a table, it nearly always says
’Duplicate key records’ and it fixed the number of rows
to 2 or 3 less (-)
than what it thought....

I did increase my key buffer to 1000, and sort buffer size = 2, other than
that the ONLY thing I changed was the network simultaneous connections to
200, are there other parameters I need to change to accommodate more memory
and more connections?

Could the memory be causing these errors, hardware, configuration?
mySQL
bugs??
H E L P!!! ----ANY help on what to look for would be greatly
appreciated.

-Craig
cs********@hotmail.com


I am having the same problems, with corruptions showing up once every
2-3 days. Appreciate feedback as well. Running on RH Linux.

--
http://www.dbForumz.com/ This article was posted by author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.dbForumz.com/mySQL-CONSTA...ict144467.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.dbForumz.com/eform.php?p=486767
Jul 20 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.