- Concept
- Version ยท 5.2.2
- Integration guide
Maven rollbackOneChangeSetSQL
Last updated: October 7, 2026
The Maven rollbackOneChangeSetSQL goal is a helper goal that allows you to inspect the SQL Liquibase will run to revert the changeset specified when using the Maven rollbackOneChangeSet goal.
Uses
The Maven rollbackOneChangeSetSQL goal is typically used when you want to inspect the raw SQL that Liquibase uses to revert your changeset when you run the rollbackOneChangeSet goal so that you don't unintentionally make a mistake.
Maven configuration
You can configure Liquibase Maven in multiple ways. You can pass arguments like <changeLogFile> in Maven directly in your pom.xml file, in a liquibase.properties file referenced in your POM, as environment variables, or as JVM system properties. To learn about each file's syntax, see Maven Properties.
For more information about the Maven configuration, see Configuring Maven.
Ensure you add <ProLicenseKey>specify your Liquibase Secure license key here</ProLicenseKey> to pom.xml or specify it in another valid way.
Running the rollbackOneChangeSetSQL Maven goal
Before running the rollbackOneChangeSetSQL goal, gather the following information from your DATABASECHANGELOG table:
The
authorof the changeset you want to revert.The
idof the changeset you want to revert.The
filename(changeset path) of the changeset you want to revert.
Note: The liquibase.rollbackScript script is only needed if the rollback is not yet defined in the changelog, and if it is not a rollback that is automatically provided by Liquibase.
Also, you can run the Maven history goal to see the history of all deployments against the configured database:
mvn liquibase:history
Next, run the rollbackOneChangeSetSQL goal, with your information:
Note: Running the rollbackOneChangeSetSQL goal requires a Maven project to be implemented.
mvn liquibase:rollbackOneChangeSetSQL
-Dliquibase.changeSetAuthor="LiquibaseProUser"
-Dliquibase.changeSetId="createProSchema"
-Dliquibase.changeSetPath="changelog.xml" -Dliquibase.force
Note: Enter the name of the changeset author, id, and the path with the changelog filename that you want to use in place of LiquibaseProUser, createProSchema, and changelog.xml. For more information, run mvn liquibase:help -Ddetail=true -Dgoal=rollbackOneChangeSetSQL.
Definition | |
|---|---|
| Specifies the |
| Specifies the changeset |
| Specifies the path to the changelog, which contains the changeset you want to roll back. |
| Specifies a required flag that indicates you intend to run this command. |
| Specifies your Liquibase Secure license key. |
Attribute | Definition |
|---|---|
| Specifies the path to the directory where Liquibase can find your changelog file. |
| The changelog file for Liquibase to use. |
| Specifies the catalog Liquibase will use to create your changelog tables. |
| Specifies the schema Liquibase will use to create your changelog tables. |
| Boolean. Forces checksums to be cleared from the DATABASECHANGELOG table. Default value is: false. |
| Specifies which contexts Liquibase will execute, which can be separated by a comma if multiple contexts are required. If a context is not specified, then all contexts will be executed. |
| Specifies the table name to use for the DATABASECHANGELOG table. |
| Specifies the table name to use for the DATABASECHANGELOG table. |
| Specifies the database object class. |
| Specifies the default catalog name to use for the database connection. |
| Specifies the default schema name to use for the database connection. |
| Specifies the driver class name to use for the database connection. |
| Specifies the location of a JDBC connection properties file which contains properties the driver will use. |
| Deprecated. Boolean. Use an empty or null value for the password instead. Default value is: false. |
| Specifies a map-based collection of changelog properties to apply. |
| Specifies a property-based collection of changelog properties to apply. |
| Boolean. Includes a Maven project artifact in the class loader, which obtains the Liquibase properties file and changelog files. Default value is |
| Boolean. Includes the Maven test output directory in the class loader which obtains the Liquibase properties file and changelog files. Default value is |
| Specifies which labels Liquibase runs, and which can be separated by a comma if multiple labels are required or you need to designate a more complex expression. If no label is specified, then all labels are run. |
| Specifies your Liquibase Secure license key. |
| Boolean. Specifies whether to ignore the catalog or database name. Default value is: false. |
| Boolean. Specifies whether to ignore the schema name. Default value is: false. |
| Specifies the file to output the rollback/ |
| Indicates that you want to set the character encoding of the output file during the |
| Specifies the database password for the database connection. |
| Deprecated. Boolean. Controls whether users are prompted before executing changesets to a non-local database. Default value is: true. |
| Specifies the Liquibase properties file to use for configuration, like |
| Boolean. Indicates that you want the |
| Specifies the property provider, which must be a |
| Specifies the path to a rollback script. |
| When set to TRUE, suppress DBCL and DBCLH sql in the console and log. Default value is: false |
| Specifies the server ID in the Maven |
| Boolean. Specifies whether to skip running Liquibase. The use of this attribute is not recommended but can be used when needed. Default value is: false. |
| Specifies a list of system properties you want to pass to the database. |
| Specifies the database URL you want to use to execute Liquibase. |
| Specifies the database username for the database connection. |
| Boolean. Controls the amount of output detail when you call the plugin. Default value is: false. |
Maven rollbackOneChangeSetSQL output
Starting Liquibase at 10:24:59 (version 4.1.1 #10 built at 2020-10-12 19:24+0000)
[INFO] Parsing Liquibase Properties File local.liquibase.properties for changeLog parameters
[INFO] Executing on Database: jdbc:oracle:thin:@localhost:1521/ORCL
[INFO] Successfully installed license from Base64 string starting with 'ABwwGgQUvH' (property liquibaseProLicenseKey).
[INFO] Liquibase Secure 4.1.1 by Liquibase licensed to support until Wed Sep 22 23:59:59 CDT 2021
[INFO] Liquibase Secure 4.1.1 by Liquibase licensed to support until Wed Sep 22 23:59:59 CDT 2021
[INFO] Successfully acquired change log lock
[INFO] Reading from DATABASECHANGELOG
[INFO] Successfully released change log lock
-- Lock Database
UPDATE DATABASECHANGELOGLOCK SET LOCKED = 1, LOCKEDBY = 'WIN-20E107KB4TN (172.30.3.88)', LOCKGRANTED = TO_TIMESTAMP('2020-11-27 10:25:01.185', 'YYYY-MM-DD HH24:MI:SS.FF') WHERE ID = 1 AND LOCKED = 0;
-- *********************************************************************
--rollback changeset 'dbchangelog.xml::createProSchema::LiquibaseProUser'
-- *********************************************************************
-- Change Log: dbchangelog.xml
-- Ran at: 11/27/20 10:25 AM
-- Against: MVN_UAT@jdbc:oracle:thin:@localhost:1521/ORCL
-- Liquibase version: 4.1.1
-- *********************************************************************
-- Rolling Back ChangeSet: dbchangelog.xml::createProSchema:: LiquibaseProUser
DROP TABLE 2;
DELETE FROM DATABASECHANGELOG WHERE ID = 'createProSchema' AND AUTHOR = 'LiquibaseProUser' AND FILENAME = 'dbchangelog.xml';
-- Release Database Lock
UPDATE DATABASECHANGELOGLOCK SET LOCKED = 0, LOCKEDBY = NULL, LOCKGRANTED = NULL WHERE ID = 1;
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 4.917 s
[INFO] Finished at: 2020-11-27T10:25:01-06:00
[INFO] ------------------------------------------------------------------------