Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

"Error on rename of" tables during upgrade when using Windows 10 and MySQL

Written By

Cristina Rodriguez

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

  • When performing a Liferay upgrade, the process stops and you find the following error in the log:
2021-05-06 08:49:36.319 INFO [main][UpgradeProcess:115] Failed upgrade process com.liferay.portal.upgrade.UpgradeProcess_7_0_0 in 33771 ms
com.liferay.portal.kernel.upgrade.UpgradeException: com.liferay.portal.kernel.upgrade.UpgradeException: java.sql.SQLException: Error on rename of '.\lportal_ee620\#sql-15cc_1e3' to '.\lportal_ee620\layout' (errno: 168 - Unknown (generic) error from engine)
  • It usually happens (randomly, not always on the same table) when the upgrade tries to update the type of data of a column:
[main][UpgradeMySQL:140] Updating columns for table layout to datetime(6)


Environment

  • Upgrade from Liferay 6.2 to Liferay DXP (7.0, 7.1, 7.2, 7.3).
  • MySQL (any supported version).
  • Windows 10.
  • Windows Security: Real Time protection active.

Resolution

  • Although Windows 10 is not listed in Liferay's compatibility matrix among the supported OS, it is a common scenario to locally test an upgrade. 
  • To workaround this issue, Windows virus and thread Real Time Protection shoud be deactivated before running the upgrade. You can do this through Windows Security -> Virus and thread protection settings -> Manage settings -> Switch off Real Time protection
  • When the process finishes, please switch on this setting again.

Additional Information

  • Similar error due to specific problem with McAfee antivirus explained here. 
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?