Showing results for 
Show  only  | Search instead for 
Did you mean: 
Not a customer? Start a free trial

Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.

AppDynamics customers and established members should click the sign in button to authenticate.

Knowledge Base

How do I fix a Liquibase validation error during a EUM Schema update?

Resolving an intermittent Liquibase error when upgrading to EUM Server v4.5 from a version lower than 4.4



As of the 4.5 EUM Server in production, the EUM MySQL database has been moved from the Controller host machine to the EUM Server host machine. 


As a result, when upgrading to EUM Server version 4.5 from a version lower than 4.4, t you may see this intermittent error after the database has been imported and during the schema update:



cd <eum_server_home>/eum-processor/bin/

bash ./eum-schema update

Loading class `com.mysql.jdbc.Driver'. This is deprecated. The new driver class is `com.mysql.cj.jdbc.Driver'. The driver is automatically registered via the SPI and manual loading of the driver class is generally unnecessary.

Unexpected error running Liquibase: Validation Failed:

1 change sets check sum

liquibaseChangelog.xml::21::AppDynamics is now: 7:834d03b3da7773ee8b2d5c0b9dd3aa96





To resolve this error, log in to the EUM database and run this SQL query:


update DATABASECHANGELOG set MD5SUM='7:834d03b3da7773ee8b2d5c0b9dd3aa96' where id=21;



Then, run the eum-schema command again, using the root user:


./eum-schema --username=root --password=XXXX update



For alternate solution, execute these commands:


bash ./eum-schema clearCheckSums
bash ./eum_schema update


Version history
Last update:
‎06-05-2020 01:13 PM
Updated by:
Labels (1)
By replying you agree to the Terms and Conditions of the AppDynamics Community.

Sometimes the below SQL query fails with ERROR 1292 (22007): Truncated incorrect DOUBLE value: 'synthetic-tag'


update DATABASECHANGELOG set MD5SUM='7:834d03b3da7773ee8b2d5c0b9dd3aa96' where id=21;

In that case, try addressing the checksum issue using below command

bash ./eum-schema clearCheckSums