Error: The database contains changes from a previous upgrade attempt that failed

Document ID : KB000004217
Last Modified Date : 14/02/2018
Show Technical Document Details
Issue:
The wasp probe continuously restarts and shows the following error in the portal.log:

ERROR [MainServlet:217] java.lang.IllegalStateException: The database contains changes from a previous upgrade attempt that failed. Please restore the old database and file system and retry the upgrade. A patch may be required if the upgrade failed due to a bug or an unforeseen data permutation that resulted from a corrupt database.
java.lang.IllegalStateException: The database contains changes from a previous upgrade attempt that failed. Please restore the old database and file system and retry the upgrade. A patch may be required if the upgrade failed due to a bug or an unforeseen data permutation that resulted from a corrupt database.
at com.liferay.portal.tools.DBUpgrader._checkReleaseState(DBUpgrader.java:300)

This is an issue where Liferay believes that it is in a failed upgrade state.  
 

********Warning********

This article should only be followed when NO previous upgrade attempts have been performed.

Environment:
UIM /UMP 7.5
Resolution:

The first step is to determine which version of UMP the customer is running. The version of UMP will then correspond with a Liferay build number.
UMP v7.5 = 6130
UMP 7.1 = 6005

Run the following query to determine the current values:

SELECT releaseId, buildNumber, state_
FROM Release_;

If the buildNumber does not match the current version of UMP then it needs to be corrected.


First stop all wasp processes.  Ensure there are no wasp processes running elsewhere in a multi-UMP environment.

Execute the following query, replacing <Build> with the correct value from above:

UPDATE Release_
SET buildNumber = <Build>, state_ = 1
WHERE releaseId = 1;