Liquibase DATABASECHANGELOG checksum mismatch blocks update after editing an executed changeset

Answer

Clear the stored checksum for only the edited changeset if the edit was intentional and does not alter already-applied schema logic, then re-run update. Revert the changelog file if the edit was accidental. Do not disable checksum validation globally, and do not leave the mismatch unresolved.

Likely explanation

Liquibase computes a checksum for each changeset when it runs and stores it in DATABASECHANGELOG.MD5SUM. Before update, default validation recomputes the checksum and compares it with the stored value. Editing an executed changeset—including whitespace, formatting, or attribute changes—changes the computed checksum, so validation reports a mismatch and blocks the command.

Confirmed facts

• Default pre-update validation is enabled unless explicitly disabled.
• A mismatch applies to the specific changeset row, although some clear-checksum commands affect every row in DATABASECHANGELOG.
• Editing an executed changeset is only safe when the database is reset or the checksum is explicitly cleared; otherwise, prefer adding a new changeset.
• runOnChange=true does not repair an existing mismatch; it only governs future re-execution.

Steps for this case

1. Compare the changelog file against version control to confirm the edit was intentional, and note the changeset id, author, and file path.
2. If intentional and schema-safe, clear the stored checksum for that specific changeset using your installed Liquibase version's targeted clear-checksum command.
3. Re-run update. Liquibase recomputes and stores the new checksum.
4. If accidental, revert the file to the previously deployed content instead of modifying DATABASECHANGELOG.

Version-specific behavior to confirm

Checksum-clearing command names and validation properties differ between Liquibase major versions. Confirm the installed major version before running any command, because syntax that works in one release may not exist in another.

Missing diagnostic detail: What is your installed Liquibase major version? This determines the exact clear-checksum command and whether a targeted row-level clear is available.

Verification

1. Run update again and confirm it completes without a validation error.
2. Inspect the DATABASECHANGELOG row for the edited changeset and confirm MD5SUM is repopulated after success.
3. Back up DATABASECHANGELOG before any manual table edits.

Assumptions and uncertainty

This assumes a standard DATABASECHANGELOG table, default validation enabled, and no custom checksum handling. No specific error text or exit code is assumed. Version-specific command syntax is not verified against your installed release; treat it as requiring review.