Post-Upgrade Database Verification Reference
Liferay DXP 2026.Q4+
This reference describes the messages the post-upgrade database verification logs, how each message names what it affects, and where the verification records them. To act on a finding, see Acting on the Findings.
Log Messages
This table lists each message with its level and the kind of finding it reports. A message’s level doesn’t stop or fail the upgrade.
| Message | Level | Finding |
|---|---|---|
Missing tables were detected | ERROR | Missing |
Missing views were detected | ERROR | Missing |
Missing columns were detected for <TABLE> table | ERROR | Missing |
Missing indexes were detected for <TABLE> table | ERROR | Missing |
Missing primary key was detected for <TABLE> table: [<COLUMNS>] | ERROR | Missing |
Index <INDEX> is not defined as [<COLUMNS>] for <TABLE> table | ERROR | Mismatched |
Index <INDEX> must be defined as unique for <TABLE> table | ERROR | Mismatched |
Index <INDEX> must not be defined as unique for <TABLE> table | ERROR | Mismatched |
Primary key [<ACTUAL_COLUMNS>] is not defined as [<DECLARED_COLUMNS>] for <TABLE> table | ERROR | Mismatched |
Column <COLUMN> is not defined as <DEFINITION> for <TABLE> table | WARN | Mismatched |
Stale unique indexes were detected for <TABLE> table | ERROR | Stale |
Stale tables were detected | WARN | Stale |
Stale views were detected | WARN | Stale |
Stale columns were detected for <TABLE> table | WARN | Stale |
Stale indexes were detected for <TABLE> table | WARN | Stale |
Custom or untracked tables were detected | INFO | Custom or untracked |
Custom or untracked views were detected | INFO | Custom or untracked |
Module <MODULE> has release state <STATE>, schema version <VERSION> | ERROR | Module release state |
Unable to get table names for company <COMPANY_ID> | ERROR | Verification error |
Unable to get the declared indexes | ERROR | Verification error |
A verification error means part of the check couldn’t run. After Unable to get the declared indexes, the verification skips the index checks.
Message Format
A message about a Liferay module’s table names the module with in module <MODULE>. A message about a core table uses in module portal. Messages about custom or untracked tables and views, and about object tables, name no module.
When database.partition.enabled=true, the missing, stale, mismatched, and custom or untracked messages also name the virtual instance with for company <COMPANY_ID>, before in module.
Missing, stale, and custom or untracked messages end with the affected names in brackets, such as Missing columns were detected for Address table in module portal: [city]. The missing primary key message instead puts the declared key columns in brackets before in module.
In the Column <COLUMN> is not defined as message, <DEFINITION> is the column’s whole declared definition, such as VARCHAR(75) null.
The module release state message appears only for a module that also has another finding. Its <STATE> reads upgrade failure or verify failure.
Console and Upgrade Report
The verification logs its findings to the console. When you run the Database Upgrade Tool, its -l option sets the log file name.
After the automatic verification, errors and warnings are also recorded in the errors and warnings sections of the upgrade report’s upgrade_report_diagnostics.txt file. That file exists only when the upgrade report is written, which requires all of these conditions:
upgrade.report.enabledistrue, its default value.- The database is not new.
- The upgrade ran at least one upgrade process.
Custom or untracked findings appear only in the console. A manual run is never recorded in an upgrade report.