Legacy Knowledge Base
Published Jul. 2, 2025

Warnings "Attempting to upgrade X table by recreating table"

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

  • During an upgrade to newer versions of the portal, warnings like "Attempting to upgrade some table by recreating table due to some reason" may be found in the logs. They can cause confusion and makes one wonder if they will have impact later or can be ignored.
  • For example:
2021-03-04 08:40:09.561 WARN  [main][UpgradeProcess:400]  Attempting to upgrade table DDLRecord by recreating the table due to:  Key column 'classPK' doesn't exist in table

Environment

  • Any upgrade from one version to a newer one.

Resolution

  • Liferay has a fallback mechanism that is executed when a modification in a database table is needed and cannot be performed by some reason. This mechanism:
    1. Dumps the table information into the disk.
    2. Recreates the table with the new defined structure.
    3. Dumps information of 2. into the database table.
  • If it successes, the next message is logged:
2021-03-04 08:40:09.702 WARN [main][UpgradeProcess:419] Successfully recreated and upgraded table DDLRecord

So the warnings can safely be ignored.

 

Did this article resolve your issue ?

Legacy Knowledge Base