Have you run a check/analyze on the table in question? The table will need to be repaired before you proceed.
>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<< On 2/4/04, 11:11:12 PM, Devios McShady <[EMAIL PROTECTED]> wrote regarding index failing on large database - any ideas why?: > I have a database with one 17GB table containing about 23 million customer records. > The table has about 15 fields. I wanna index five of them to speed up searching. > My indexing operation keeps failing with error:127 (record table has crashed). > The process fails of different fields at different times; there is no consistencey in when the error occurs... I've tried this process on three seperate systems and had the same results. > The last server was a Dual 3GHz Zeon with 6GB Ram and a 15K RPM SCSI RAID array on an LSI RAID Card running RedHat. The server prior to that was a Dual AMD Opteron with 4GB Ram running Windows 200 Server. The server prior to that was a single AMD Thunderbird 1GHz with 2GB Ram running Windows 2000 Pro. All the systems are getting the same error. > Can anyone speculate as to what might be going on? Are there some things I should check, such as for certail characters that indexing can't handle within the table data? Are there some mysqld parameters I need to set when working with this much data? Are there compilation flags I should have set? > I appreciate any help anyone may be able to provide. > Thanks, > Devi0s. > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
