rollbackOneUpdate command
The rollbackOneUpdate command reverts (rolls back) all changesets related by a specific deploymentId that was made during a previous change to your database. It is only available for Liquibase Pro users.
Uses
The rollbackOneUpdate command is typically used when you want to undo a series of changes made to your database during a specific deployment and revert those changesets to their previous state without affecting any other changes made to your database.
The rollbackOneUpdate command allows you to target a specific deploymentId without impacting other changes or deployments that came before or after it.
The image above shows deploymentIds 1 through 5, with deploymentId 2 incorporating all the changesets we want to roll back. As you can see, the rollbackOneUpdate command allows you to target deploymentId 2 and revert all changesets associated with the same deploymentId to its previous state without impacting the others.
The impacts of rollbackOneUpdate
Like any cherry-picking tool, using the rollbackOneUpdate command comes with risks which may be unintended.
Please look for potential unintended consequences before using this command.
It is a best practice to run the rollbackOneUpdateSQL command because it allows you to inspect the rollbackOneUpdate SQL and search for any potential mistakes before you execute the rollbackOneUpdate command.
Also, the use of rollbackOneUpdate comes with risk of unintended consequences, because of this, the command requires a --force flag to indicate that you intend to run the command.
Additional impacts to the DATABASECHANGELOG table
Running the rollbackOneUpdate command will remove the deployment record from the DATABASECHANGELOG table. As a user, you must decide on what to do with your changesets after the rollbackOneChangeSet command has been run.
Depending on your desired outcome, consider doing one of the following:
- Modify the changeset in the changelog file and re-deploy it.
- Do nothing to the changeset in the changelog file and have it be re-deployed.
- Delete the changeset in the changelog file.
Running the rollbackOneUpdate command
Before running the rollbackOneUpdate command, you can get the optional deploymentId by running the history command:
- The
deploymentIdof the deployment you want to revert
Note: If the
deploymentIdis not supplied, Liquibase Pro will look up the most recentdeploymentIdfrom the DATABASECHANGELOG table and use it for the rollback.
Then run the rollbackOneUpdate command, with your information:
liquibase rollbackOneUpdateSQL --deploymentId=068379006For more command specific help, type liquibase rollbackOneUpdate --help into the command prompt.
rollbackOneUpdate global parameters
| Parameter | Definition | Requirement |
|---|---|---|
--changeLogFile * |
The root changelog | Required |
--url
|
The JDBC database connection URL | Required |
--username
|
The database username | Required |
--password
|
The database password | Required |
--liquibaseProLicenseKey
|
Your Liquibase Pro license key | Required |
* Liquibase will check nested changelogs for definitions of the changesets to rollback
rollbackOneUpdate command parameters
| Parameter | Definition | Requirement |
|---|---|---|
--deploymentId * |
Specifies the deploymentId of all from the DATABASECHANGELOG table related to the changesets intended for rollback. |
Optional |
--force
|
A required parameter which indicates you intend to use this feature. | Required |
* If not supplied, Liquibase Pro will lookup the most recent
deploymentIdfrom the DATABASECHANGELOG table and use it for the rollback.
Output
When successful, the rollbackOneUpdate command produces the following output:
liquibase rollbackOneUpdate --deploymentId=2126881174 --force
Liquibase Pro 3.8.7 by Datical licensed to Liquibase Pro Customer until Tue Nov 03 19:00:00 CST 2020
Rolling Back Changeset:sql.oracle.sql::3-createTableForCC::Liquibase Pro User
Rolling Back Changeset:sql.oracle.sql::2-createTableForView::Liquibase Pro User
Rolling Back Changeset:sql.oracle.sql::1-createTableForSynonym::Liquibase Pro User
Liquibase: Rollback has been successful.