Issues with Solutions Specific to Storage Engines
Actually, any problem this book discusses could have specific nuances based on the storage engine you use. We will touch upon these aspects throughout the book. In this section, I want to show a few features of storage engines that are independent of other problems. We’ll cover a few basic problems that use tools specific to MyISAM or InnoDB because these are the most popular and frequently used storage engines. If you use a third-party storage engine, consult its user manual for useful tools.
Errors related to a storage engine are either reported back to the client or recorded in the error logfile. Usually the name of the storage engine appears in the error message. In rare cases, you will get an error number not known by the perror utility. This is usually a symptom of an issue with a storage engine.
One common storage engine issue is corruption. This is not
always the fault of the storage engine, but can have an external cause
such as disk damage, a system crash, or a MySQL server crash. For example,
if somebody runs kill -9 on the server’s process, she
is almost asking for data corruption. We will discuss here what to do in
case of MyISAM and InnoDB corruption. We will not discuss how to fix
corruption of a third-party storage engine; consult its documentation for
guidance. As a general recommendation, you can try CHECK TABLE, which many storage engines support.
(CHECK TABLE for the MyISAM storage
engine is explained in Repairing ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access