8:abc123... ... The validCheckSum child element accepts the old checksum string and tells Liquibase that this old hash is also acceptable. This is less disruptive than clearCheckSums because it only affects the specific changeSet, not the entire migration history."> 8:abc123... ... The validCheckSum child element accepts the old checksum string and tells Liquibase that this old hash is also acceptable. This is less disruptive than clearCheckSums because it only affects the specific changeSet, not the entire migration history." />

Prev Next

Database / Liquibase interview questions

What is the Liquibase Pro checksum validity and how do clearCheckSums and validChecksums work?

Liquibase computes an MD5 checksum for each changeSet when it first runs and stores it in DATABASECHANGELOG. On every subsequent run, Liquibase recomputes the checksum from the current file and compares it against the stored value. If they differ, Liquibase throws a ValidationFailedException and refuses to proceed.

This is a deliberate safety mechanism — if someone edits an applied changeSet, you know immediately. However, there are legitimate cases where you need to update a checksum without re-running the migration:

clearCheckSums — Clears all stored checksums in DATABASECHANGELOG, setting them to NULL. On the next run, Liquibase recomputes checksums from the current files and stores them again. This is a brute-force fix but it means Liquibase loses its ability to detect modifications until the checksums are re-stored on the next run.

liquibase clearCheckSums

validCheckSums — A more targeted approach. You declare additional valid checksums for a specific changeSet in the changeLog itself, telling Liquibase to accept any of those checksum values as legitimate. This is used when a changeSet content changed due to whitespace normalisation, encoding changes, or Liquibase version upgrades that changed how checksums are computed:

<changeSet id="1" author="alice">
    <validCheckSum>8:abc123...</validCheckSum>  <!-- previous computed checksum -->
    <createTable tableName="customer">
        ...
    </createTable>
</changeSet>

The validCheckSum child element accepts the old checksum string and tells Liquibase that this old hash is also acceptable. This is less disruptive than clearCheckSums because it only affects the specific changeSet, not the entire migration history.

What is the targeted alternative to clearCheckSums when only one changeSet has a checksum issue?
When would a Liquibase version upgrade legitimately cause checksum mismatches on unchanged changeSets?

Invest now in Acorns!!! 🚀 Join Acorns and get your $5 bonus!

Invest now in Acorns!!! 🚀
Join Acorns and get your $5 bonus!

Earn passively and while sleeping

Acorns is a micro-investing app that automatically invests your "spare change" from daily purchases into diversified, expert-built portfolios of ETFs. It is designed for beginners, allowing you to start investing with as little as $5. The service automates saving and investing. Disclosure: I may receive a referral bonus.

Invest now!!! Get Free equity stock (US, UK only)!

Use Robinhood app to invest in stocks. It is safe and secure. Use the Referral link to claim your free stock when you sign up!.

The Robinhood app makes it easy to trade stocks, crypto and more.


Webull! Receive free stock by signing up using the link: Webull signup.

More Related questions...

What is Liquibase and what problem does it solve? What is a changeLog in Liquibase? What is a changeSet in Liquibase and how is it identified? What are the DATABASECHANGELOG and DATABASECHANGELOGLOCK tables? What is the difference between Liquibase and Flyway? What are contexts in Liquibase and how do you use them? What are labels in Liquibase and how do they differ from contexts? How does rollback work in Liquibase? What is a Liquibase precondition and why would you use one? How do you integrate Liquibase with Spring Boot? What are Liquibase change types and can you name common ones? What is the Liquibase diff command and when is it useful? What are Liquibase tags and how do you use rollback to a tag? What is runOnChange and runAlways in a Liquibase changeSet? What is the markNextChangeSetRan and markNextChangeSetRanSQL command used for? How do you manage Liquibase changeLog files in a multi-module Maven project? What is the Liquibase updateSQL command and when is it used? What is a Liquibase snapshot and what commands use it? What is the failOnError attribute in a changeSet and when should you set it to false? How does Liquibase handle transactions during migration? What is the Liquibase Hub and what does it provide? How do you use Liquibase with multiple databases or schemas in a single application? What is the Liquibase Pro checksum validity and how do clearCheckSums and validChecksums work? What are Liquibase custom change types and how do you create one? How do you handle large table migrations in Liquibase without causing downtime? What is the Liquibase Maven plugin and how do you run migrations with it? What is the Liquibase status command and how does it differ from validate? What are Liquibase property substitution and how does it work? How do you write Liquibase changeLogs in YAML format? What is the Liquibase formatted SQL changeLog format? What is the Liquibase updateTestingRollback command? How do you use Liquibase with Docker and Testcontainers in integration tests? What is the difference between addColumn with a default value and a nullable column in Liquibase for large tables? What is liquibase.properties and what configuration belongs in it?
Show more question and Answers...

MuleESB

Comments & Discussions