# Validation Failed without any changes

**URL:** <https://forum.liquibase.org/t/validation-failed-without-any-changes/3612>\
**Category:** General Discussion\
**Created:** [April 6, 2018, 5:37pm UTC](https://forum.liquibase.org/t/validation-failed-without-any-changes/3612 "2018-04-06T17:37:00Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![TomaszPiec](https://avatars.discourse-cdn.com/v4/letter/t/a88e57/32.png) [@TomaszPiec](https://forum.liquibase.org/u/TomaszPiec)\
**Post date:** [April 6, 2018, 5:37pm UTC](https://forum.liquibase.org/t/validation-failed-without-any-changes/3612/1 "2018-04-06T17:37:00Z")

</div>

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&nbsp;

  

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&nbsp;liquibase:clearCheckSums but I would like to know the reason before hitting PROD db).

---

<div class="post-metadata">

**Author:** ![un40715084211236659r](https://avatars.discourse-cdn.com/v4/letter/u/50afbb/32.png) [@un40715084211236659r](https://forum.liquibase.org/u/un40715084211236659r)\
**Post date:** [April 6, 2018, 5:37pm UTC](https://forum.liquibase.org/t/validation-failed-without-any-changes/3612/2 "2018-04-06T17:37:00Z")

</div>

I have found solution myself 😉

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&nbsp;

3.5.5

problem was solved.

And the most magic thing is that when we executed&nbsp;

---

<div class="post-metadata">

**Author:** ![un40715084211236659r](https://avatars.discourse-cdn.com/v4/letter/u/50afbb/32.png) [@un40715084211236659r](https://forum.liquibase.org/u/un40715084211236659r)\
**Post date:** [April 6, 2018, 5:37pm UTC](https://forum.liquibase.org/t/validation-failed-without-any-changes/3612/3 "2018-04-06T17:37:00Z")

</div>

Problem was solved.

We have separate user which has read access to:

DATABASECHANGELOG

DATABASECHANGELOGLOCK

but those tables are not in default schema.&nbsp;

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:

&nbsp; ACC

&nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp;

&nbsp; &nbsp; \<db.schema\>MY\_SCHEMA\</db.schema\>

&nbsp;

No it works fine.

Thanks for reply.

---

<div class="post-metadata">

**Author:** ![nvoxland](https://avatars.discourse-cdn.com/v4/letter/n/87869e/32.png) [@nvoxland](https://forum.liquibase.org/u/nvoxland)\
**Post date:** [April 6, 2018, 5:37pm UTC](https://forum.liquibase.org/t/validation-failed-without-any-changes/3612/4 "2018-04-06T17:37:00Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![nvoxland](https://avatars.discourse-cdn.com/v4/letter/n/87869e/32.png) [@nvoxland](https://forum.liquibase.org/u/nvoxland)\
**Post date:** [April 6, 2018, 5:37pm UTC](https://forum.liquibase.org/t/validation-failed-without-any-changes/3612/5 "2018-04-06T17:37:00Z")

</div>

Good, thanks for letting me know.

Nathan