MySQL Data Access Exception - Errcode - 17 occurs with JIRA
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
Summary
Symptoms
JIRA was not able to come up after restart, and the following appears in the atlassian-jira.log:
1
2
3
4
5
6
7
8
com.atlassian.jira.exception.DataAccessException: java.sql.SQLException: Can't create/write to file 'C:\temp2#sql_eb4_0.MYI' (Errcode: 17)
at com.atlassian.jira.upgrade.util.UpgradeUtils.getExactColumnName(UpgradeUtils.java:222)
at com.atlassian.jira.appconsistency.db.Build178SchemaCheck.isColumnInTable(Build178SchemaCheck.java:81)
at com.atlassian.jira.appconsistency.db.Build178SchemaCheck.check(Build178SchemaCheck.java:71)
at com.atlassian.jira.appconsistency.db.Build178SchemaCheck.isOk(Build178SchemaCheck.java:38)
at com.atlassian.jira.appconsistency.db.DatabaseChecker.checkDatabase(DatabaseChecker.java:108)
at com.atlassian.jira.appconsistency.db.DatabaseCompatibilityEnforcer.contextInitialized(DatabaseCompatibilityEnforcer.java:32)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3692)
Diagnosis
error code means:
1
2
C:\>perror 17
OS error code 17: File existsCause
This error was caused by a MySQL Bug which is described in detail on the following link MySQL Bug Forum.
Solution
Workaround
Disable anti-virus from checking JIRA folders. "On-access" checking on JIRA servers should not be enabled.
Was this helpful?