Validation Failed without any changes

General Discussion
1

Hi.

We have encountered problem with checksums. We have 3 environments: TEST, ACC and PROD.
Everything was working fine till today where we encounter such error:

… (CUT) …
Nothing has changed in code. Files are the same as weeks before. And the most important thing:
DATABASECHANGELOG table has exactly the same MD5 checksum in TEST, ACC and PROD databases and 

liquibase:updateSQL -PACC
or
liquibase:status -PACC

have problem on ACC and PROD but works fine for TEST environment.
What might cause a problem here ?
(I know I can solve this by liquibase:clearCheckSums but I would like to know the reason before hitting PROD db).

2

I have found solution myself :wink:

We had no definition of liquibase-maven-plugin so maven automatically pulled version of liquibase 3.6.0 (update in maven was done yesterday 05.04.2018)

and it looks like there was major change of checksum algorithm.

When I used 

3.5.5

problem was solved.

And the most magic thing is that when we executed 

3

Problem was solved.

We have separate user which has read access to:

DATABASECHANGELOG

DATABASECHANGELOGLOCK

but those tables are not in default schema. 

We had configuration for schema but it’s property was externalized to property file like this in pom.xml in section :

${db.schema}

And was not set correctly.

I have moved config directly to profile:

  ACC

          

    <db.schema>MY_SCHEMA</db.schema>

 

No it works fine.

Thanks for reply.

4

Yes, working on rolling out 3.6.0, thanks for the bug reports.

There was a change in the checksum algorithm that made us have to update the version from 7 to 8. The update commands will handle that upgrade for you automatically, but status can’t because it doesn’t change the database, it just reads what is there. I should look at making it less error-y, though.

UpdateSQL should only require read access. What exception/error are you getting?

Nathan

5

Good, thanks for letting me know.

Nathan