SpirirHost Support Centre: MySQL Reference Manual p.500

<< previous page -- table of contents -- next page >>

Chapter_1

Chapter_2

Chapter_3

Chapter_4

Chapter_5

Return to Table of Contents

Table of Contents
1. General Information
2. MySQL Installation
3. Tutorial Introduction
4. Database Administration
5. MySQL Optimisation
6. MySQL Language Reference
7. MySQL Table Types
8. MySQL APIs
9. Extending MySQL

500 MySQL Technical Reference for Version 4.0.3 7.1.3 MyISAM Table Problems The le format that MySQL uses to store data has been extensively tested, but there are always circumstances that may cause database tables to become corrupted. 7.1.3.1 Corrupted MyISAM Tables Even if the MyISAM table format is very reliable (all changes to a table is written before the SQL statements returns) , you can still get corrupted tables if some of the following things happens: The mysqld process being killed in the middle of a write. Unexpected shutdown of the computer (for example, if the computer is turned o). A hardware error. You are using an external program (like myisamchk) on a live table. A software bug in the MySQL or MyISAM code. Typial typical symptoms for a corrupt table is: You get the error Incorrect key file for table: '...'. Try to repair it while se- lecting data from the table. Queries doesn't nd rows in the table or returns incomplete data. You can check if a table is ok with the command CHECK TABLE. See Section 4.4.4 [CHECK TABLE], page 229. You can repair a corrupted table with REPAIR TABLE. See Section 4.4.5 [REPAIR TABLE], page 230. You can also repair a table, when mysqld is not running with the myisamchk command. myisamchk syntax. If your tables get corrupted a lot you should try to nd the reason for this! See Section A.4.1 [Crashing], page 640. In this case the most important thing to know is if the table got corrupted if the mysqld died (one can easily verify this by checking if there is a recent row restarted mysqld in the mysqld error le). If this isn't the case, then you should try to make a test case of this. See Section E.1.6 [Reproduceable test case], page 763. 7.1.3.2 Clients is using or hasn't closed the table properly Each MyISAM `.MYI' le has in the header a counter that can be used to check if a table has been closed properly. If you get the following warning from CHECK TABLE or myisamchk: # clients is using or hasn't closed the table properly this means that this counter has come out of sync. This doesn't mean that the table is corrupted, but means that you should at least do a check on the table to verify that it's okay. The counter works as follows:

MySQL Reference Manual

Home
Hosting Plans \| Domain Registration \| About Us \| Contact Us \| Site Map Terms of Use \| Privacy Policy \| Guarantees Merchant Accounts

SpiritHost - web hosting for spiritual and education sites SpiritHit.com - Religious and Spiritual Portal Copyright © 2002 Dyntex Group, Inc. All Rights Reserved

Return to Table of Contents	Back to top

Web Hosting: Manuals & FAQ's

1. Unix-Based Web Hosting
2. Unix Dedicated Servers
3. Windows Dedicated Servers
4. CuteFTP User’s Guide
5. CuteHTML User’s Guide
6. WS_FTP Pro User's Guide
7. Miva Order User's Guide
8. Miva Merchant User's Guide