Database Errors when using the Default MySQL Storage Engine
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs 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
Errors when creating table schema during database migration or an upgrade
Cause
The default storage engine for MySQL is MyISAM. It does not support referential integrity, foreign key constraints or transactions, so it may cause data corruption. See - http://dev.mysql.com/doc/refman/5.1/en/storage-engines.html
Resolution
Set the storage engine by passing the '--default-storage-engine=INNODB' option when starting the session.
Or
Alter the existing table storage engine to use INNODB type
1 2ALTER TABLE <tablename> ENGINE=INNODB;Or
Make the default MySQL Server setting by adding this option to the my.ini (or my.cnf) configuration file.
Was this helpful?