'Got error 134 from storage engine' Error Due to MySQL Table Corruption
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
The following appears in the atlassian-confluence.log:
uncategorized SQLException for SQL []; SQL state [HY000]; error code [1030]; Got error 134 from storage engine; nested exception is java.sql.SQLException: Got error 134 from storage engine
Cause
MySQL (with MyISAM as the storage engine) has experienced table corruption.
MyISAM is not recommended as the storage engine. Please see Database Troubleshooting for MySQL.
Resolution
- Refer to MySQL's site, 13.1.4.1. Corrupted MyISAM Tables.
- After repairing the corruption, convert from MyISAM to InnoDB tables. See Database errors when using MySQL and MyISAM tables.