Liquibase rollback fails with missing rollback definition after addColumn changeset

Question

Rollback aborts after a deployed schema change

I have a changelog where one changeset adds a column with a default value to an existing table, and a later changeset builds on that column. When I run a rollback command targeting the earlier changeset, Liquibase aborts and reports that no rollback was defined for the changeset, leaving the schema untouched.

My understanding is that Liquibase only reverses a changeset if it contains an explicit <rollback> block, and that some change types can be auto-reversed while others cannot. I am unsure which category addColumn with a default value falls into, and whether the failure I am seeing is purely the missing block or something about how the changeset was written.

A second concern: even once a rollback block exists, dropping the column would also destroy the data it holds, and I have not found a documented built-in mechanism for preserving that data during reversal.

Questions

Which change types does Liquibase auto-reverse, and does addColumn with a default value require an explicit <rollback> block?
Is there a documented pattern for archiving column data inside a rollback block before the column is dropped?
If a rollback fails partway through, what state does Liquibase leave the database in, and how is that recorded in the DATABASECHANGELOG table?

Tasadduq Burney · Answer

Answer to the exact question

Liquibase can automatically reverse a changeset only when it uses one of the built‑in change types that are marked as reversible. The <addColumn> change type is one of those; Liquibase will generate a DROP COLUMN statement for you. However, the “missing rollback definition” error appears when Liquibase cannot infer a reverse operation. This usually happens when the column was added with a raw <sql> tag or a <customChange> instead of the structured <addColumn> element. In that case, Liquibase requires an explicit <rollback> block.

Which change types are auto‑reversible?

addColumn, dropColumn, addPrimaryKey, dropPrimaryKey
addForeignKeyConstraint, dropForeignKeyConstraint
createTable, dropTable
insert, delete, update (if rollback is provided)
other change types that have a documented reverse operation in Liquibase docs.

Any change that does not have a reverse, or that is expressed via raw SQL, must be wrapped in a <rollback> block.

Archiving column data in a rollback block

Liquibase does not move data for you when a column is dropped. The usual pattern is to copy the column’s contents to an archive table before dropping it. Example:

<changeSet id="2026-10-15-add-new-col" author="me">
  <addColumn tableName="orders">
    <column name="promo_code" type="varchar(20)" defaultValue="N/A"></column>
  </addColumn>
  <rollback>
    <sql>
      CREATE TABLE IF NOT EXISTS orders_promo_code_backup AS
      SELECT id, promo_code FROM orders;
    </sql>
    <dropColumn tableName="orders" columnName="promo_code"/>
  </rollback>
</changeSet>

In this block Liquibase first creates a backup table (id + old column value) and then drops the column. Because the <dropColumn> is a reversible change, Liquibase will record the rollback as successful only after the backup table is created.

State after a partial rollback failure

If Liquibase aborts while executing a rollback, the database remains in the state after the last successful SQL statement. Liquibase updates the DATABASECHANGELOG table only when the entire rollback completes. Therefore:

Rows for the changeset that failed remain in DATABASECHANGELOG with EXECUTED status.
Subsequent rollback attempts will skip that changeset unless you force it with --force or manually delete the row.
Any data that was already moved (e.g., to an archive table) stays, but the column may still exist if the drop failed.

What to check next

The error message you see is most common when the column was added with a raw <sql> statement. If that is the case, add an explicit <rollback> block as shown above. If you used <addColumn> correctly, ensure that no later changeset depends on the column you are trying to roll back; Liquibase will refuse to roll back an earlier changeset if a later one references it. In that scenario, roll back the later changeset first.

Diagnostic question for you: Did you add the column using a <sql> tag instead of the structured <addColumn> element? This detail determines whether Liquibase can auto‑reverse the change or requires an explicit rollback block.