Legacy Knowledge Base
Published Sep. 10, 2025

java.sql.SQLException: Error on rename of mysql.frm due to permission denied

Written By

Sivakumar Perumal

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • After deploying the jar, it gets deployed and started successfully with the following error on Liferay logs. Also, the table gets created but there is no entry in Release_ and ServiceComponent table.
    ERROR [fileinstall-E:/Prod_server/server/osgi/modules][com_liferay_portal_upgrade_impl:97] Invocation to listener threw exception 
    java.lang.RuntimeException: com.liferay.portal.kernel.upgrade.UpgradeException: Bundle UserInformation.service_1.0.0 [714] has invalid content in indexes.sql:_create index IX_EFCA58E8 on AtosSyntelUserInfo (City[$COLUMN_LENGTH:75$]);_create index IX_724EB8AB on AtosSyntelUserInfo (uuid_[$COLUMN_LENGTH:75$]); [Sanitized]
    .
    .
    Caused by: java.sql.SQLException: Error on rename of '.\mydb\#sql-670_19b0.frm' to '.\mydb\atossynteluserinfo.frm' (Errcode: 13 - Permission denied)
    at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:963)
    at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3966)
    ... 49 more

Environment

  • Liferay DXP 7.0
  • MySQL
  • McAfee antivirus
  • Windows environment

Resolution

  • This seems to be a frequent issue when MySQL and antivirus are installed on the windows system.
  • Since McAfee antivirus installed on the same system where DB is running, due to some restrictions in permissions or interactions, MySQL is unable to create an index with the above error.
  • Redeploying the jar once again by disabling the antivirus might help. Please look into this unofficial article as per your discretion.
    http://osskb.blogspot.com/2016/09/how-to-fix-error-on-rename-of-mysql-frm.html

Additional Information

  • Since the root cause is due to the antivirus, connecting with the respective team would help to move forward.
Did this article resolve your issue ?

Legacy Knowledge Base