Internal documentation only

This page has been marked as draft.

Fixing corrupted tables in MySQL/MariaDB

Though rare, a table may get corrupted in MySQL/MariaDB, causing you to not be able to use some features of OP5 or cause instability in the system.

An example would be trying to go to the Availability Reporting section, and it you receive an error like so:

You will need to run the repair for MySQL to fix the crashed table. You may need to stop the Monitor services to proceed:

## mon stop
## mysqlcheck merlin --auto-repair
## mon start

Do note that, depending on the size of the database and/or table, this may take some time.

Additional details for mysqlcheck here:

Usage: mysqlcheck [OPTIONS] database [tables]
OR     mysqlcheck [OPTIONS] --databases DB1 [DB2 DB3...]
OR     mysqlcheck [OPTIONS] --all-databases

The option -c will be used by default, if none was specified. You
can change the default behavior by making a symbolic link, or
copying this file somewhere with another name, the alternatives are:
mysqlrepair:   The default option will be -r
mysqlanalyze:  The default option will be -a
mysqloptimize: The default option will be -o

To run specifically for merlin:

## mysqlcheck merlin --auto-repair

or

## mysqlcheck -r merlin

Afterwards, restart monitor to start back up the service:

## mon start