Submit a ticketCall us

Get a crash course on Network Monitoring delivered right to your inbox
This free 7-day email course provides a primer to the philosophy, theory, and fundamental concepts involved in IT monitoring. Lessons will explain not only how to perform various monitoring tasks, but why and when you should use them. Sign up now.

Home > Success Center > Storage Manager (STM) > Manually run a myisamchk in STM - Windows

Manually run a myisamchk in STM - Windows

Table of contents

Overview

MyISAM is the default storage engine for MySQL databases. However, MyISAM tables get corrupted very easily because of any of the following reasons:

  • common wear and tear
  • AV software is trying to read/write the DB at the same time
  • another software is actively scanning the same subdirectory as <install path>\mariadb\data\storage\ subdir

Environment

STM v5, v5.6.2 and v5.7.2

Steps

To avoid and/or resolve this issue, manually run a myISAMCHK in Windows STM by doing the following steps:

Windows STM:

  1. Stop the Mariadb service. 

    Note: All other SW services are dependent upon the Mariadb service being run so they will stop automatically; this behavior is expected.

  2. Open Windows Explorer and copy the entire path: C:\Program Files\SolarWinds\Storage Manager Server\mariadb\data\storage

  3. Open CMD as an Administrator.
  4. Paste the copied path in Step 2 and change the directory to: C:\Program Files\SolarWinds\Storage Manager Server\mariadb\data\storage
  5. Run the following: for %i in (*.MYI) do ..\..\bin\myisamchk --defaults-extra-file=..\..\my.cnf --check --analyze -r -v %i

Please refer to How to Run a myisamchk to Resolve Crashed MariaDB Tables as an additional reference for this article.

Last modified
08:05, 7 Jan 2017

Tags

Classifications

Public