rollback-one-update-sql

Last updated: January 21, 2026

Note: This is a Liquibase Secure feature, so you need a Liquibase Secure License Key to use it.

The rollback-one-update-sql command is a helper command that allows you to inspect the SQL Liquibase will run to revert all changeset associated with the deploymentID specified in the rollback-one-update command. It is only available for Liquibase Secure users.

Uses

The rollback-one-update-sql command is typically used when you want inspect the raw SQL that Liquibase uses to revert all changesets associated with a specified deploymentId when you run the rollback-one-update command, so you don't unintentionally make a mistake.

Syntax

Before running the rollback-one-update-sql command, you can get the optional deploymentId of the changeset group you want to revert by running the history command.

Then run the rollback-one-update-sql command, with your information:

liquibase rollback-one-update-sql --changelog-file=example-changelog.xml --deploymentId=2068379006

Note: Unlike the rollback-one-update command, there is no impact to the DATABASECHANGELOG table.

For more command-specific help, type liquibase rollback-one-update-sql --help into the command prompt.

* Liquibase checks the changelog and any nested changelogs for the definitions of the changeset to roll back.

Note: The username and password attributes are not required for connections and systems which use alternate means of authentication. Also, you can specify database credentials as part of the url attribute.

Parameters

Global parameters

Parameter	Definition	Requirement
`--license-key=<string>`	Your Liquibase Pro license key	Required
`--output-file=<string>`	File path to where the command output will be written. If not specified, output goes to `STDOUT`. See `--output-file`.	Optional

Command parameters

Parameter	Definition	Requirement
`--changelog-file=<string>`	The root changelog	Required
`--url=<string>`	The JDBC database connection URL.	Required
`--default-catalog-name=<string>`	Name of the default catalog to use for the database connection	Optional
`--default-schema-name=<string>`	Name of the default schema to use for the database connection. If `defaultSchemaName` is set, then objects do not have to be fully qualified. This means you can refer to just `mytable` instead of `myschema.mytable`. Note: In the properties file and `JAVA_OPTS` only: in 4.18.0 and earlier, specify this parameter using the syntax `defaultSchemaName`. In 4.19.0 and later, use the syntax `liquibase.command.defaultSchemaName`. Note: In Liquibase 4.12.0 and later, you can use mixed-case schema names if you set `--preserve-schema-case` to `true`. However, in Liquibase 4.12.0–4.22.0, the Liquibase validator still throws a `DatabaseException` error if you specify a mixed-case value of `defaultSchemaName`. In 4.23.0 and later, the Liquibase validator accepts any casing.	Optional
`--deployment-id=<string>`	Specifies the deployment ID of all rows from the DATABASECHANGELOG table related to the changesets intended for rollback. If not supplied, Liquibase Pro will look up the most recent deployment ID from the DATABASECHANGELOG table and use it for the rollback.	Optional
`--driver=<string>`	The JDBC driver class	Optional
`--driver-properties-file=<string>`	The JDBC driver properties file	Optional
`--output-default-catalog=<true\|false>`	Control whether names of objects in the default catalog are fully qualified or not. If `true`, they are. If `false`, only objects outside the default catalog are fully qualified. Default: `true`.	Optional
`--output-default-schema=<true\|false>`	Control whether names of objects in the default schema are fully qualified or not. If `true`, they are. If `false`, only objects outside the default schema are fully qualified. Default: `true`.	Optional
`--password=<string>`	Password to connect to the target database.	Optional
`--rollback-script=<string>`	The path to the script to use to perform the rollback. Only needed if the rollback is not already defined in the changelog, and if it is not a rollback statement that Liquibase automatically generates.	Optional
`--username=<string>`	Username to connect to the target database.	Optional

Global parameters

Parameter	Definition	Requirement
`globalArgs: { license-key: "<string>" }`	Your Liquibase Pro license key	Required
`globalArgs: { output-file: "<string>" }`	File path to where the command output will be written. If not specified, output goes to `STDOUT`. See `--output-file`.	Optional

Command parameters

Parameter	Definition	Requirement
`cmdArgs: { changelog-file: "<string>" }`	The root changelog	Required
`cmdArgs: { url: "<string>" }`	The JDBC database connection URL.	Required
`cmdArgs: { default-catalog-name: "<string>" }`	Name of the default catalog to use for the database connection	Optional
`cmdArgs: { default-schema-name: "<string>" }`	Name of the default schema to use for the database connection. If `defaultSchemaName` is set, then objects do not have to be fully qualified. This means you can refer to just `mytable` instead of `myschema.mytable`. Note: In the properties file and `JAVA_OPTS` only: in 4.18.0 and earlier, specify this parameter using the syntax `defaultSchemaName`. In 4.19.0 and later, use the syntax `liquibase.command.defaultSchemaName`. Note: In Liquibase 4.12.0 and later, you can use mixed-case schema names if you set `--preserve-schema-case` to `true`. However, in Liquibase 4.12.0–4.22.0, the Liquibase validator still throws a `DatabaseException` error if you specify a mixed-case value of `defaultSchemaName`. In 4.23.0 and later, the Liquibase validator accepts any casing.	Optional
`cmdArgs: { deployment-id: "<string>" }`	Specifies the deployment ID of all rows from the DATABASECHANGELOG table related to the changesets intended for rollback. If not supplied, Liquibase Pro will look up the most recent deployment ID from the DATABASECHANGELOG table and use it for the rollback.	Optional
`cmdArgs: { driver: "<string>" }`	The JDBC driver class	Optional
`cmdArgs: { driver-properties-file: "<string>" }`	The JDBC driver properties file	Optional
`cmdArgs: { output-default-catalog: "<true\|false>" }`	Control whether names of objects in the default catalog are fully qualified or not. If `true`, they are. If `false`, only objects outside the default catalog are fully qualified. Default: `true`.	Optional
`cmdArgs: { output-default-schema: "<true\|false>" }`	Control whether names of objects in the default schema are fully qualified or not. If `true`, they are. If `false`, only objects outside the default schema are fully qualified. Default: `true`.	Optional
`cmdArgs: { password: "<string>" }`	Password to connect to the target database.	Optional
`cmdArgs: { rollback-script: "<string>" }`	The path to the script to use to perform the rollback. Only needed if the rollback is not already defined in the changelog, and if it is not a rollback statement that Liquibase automatically generates.	Optional
`cmdArgs: { username: "<string>" }`	Username to connect to the target database.	Optional

Global parameters

Parameter	Definition	Requirement
`liquibase.licenseKey: <string>`	Your Liquibase Pro license key	Required
`liquibase.outputFile: <string>`	File path to where the command output will be written. If not specified, output goes to `STDOUT`. See `--output-file`.	Optional

Command parameters

Parameter	Definition	Requirement
`liquibase.command.changelogFile: <string>` `liquibase.command.rollbackOneUpdateSql.changelogFile: <string>`	The root changelog	Required
`liquibase.command.url: <string>` `liquibase.command.rollbackOneUpdateSql.url: <string>`	The JDBC database connection URL.	Required
`liquibase.command.defaultCatalogName: <string>` `liquibase.command.rollbackOneUpdateSql.defaultCatalogName: <string>`	Name of the default catalog to use for the database connection	Optional
`liquibase.command.defaultSchemaName: <string>` `liquibase.command.rollbackOneUpdateSql.defaultSchemaName: <string>`	Name of the default schema to use for the database connection. If `defaultSchemaName` is set, then objects do not have to be fully qualified. This means you can refer to just `mytable` instead of `myschema.mytable`. Note: In the properties file and `JAVA_OPTS` only: in 4.18.0 and earlier, specify this parameter using the syntax `defaultSchemaName`. In 4.19.0 and later, use the syntax `liquibase.command.defaultSchemaName`. Note: In Liquibase 4.12.0 and later, you can use mixed-case schema names if you set `--preserve-schema-case` to `true`. However, in Liquibase 4.12.0–4.22.0, the Liquibase validator still throws a `DatabaseException` error if you specify a mixed-case value of `defaultSchemaName`. In 4.23.0 and later, the Liquibase validator accepts any casing.	Optional
`liquibase.command.deploymentId: <string>` `liquibase.command.rollbackOneUpdateSql.deploymentId: <string>`	Specifies the deployment ID of all rows from the DATABASECHANGELOG table related to the changesets intended for rollback. If not supplied, Liquibase Pro will look up the most recent deployment ID from the DATABASECHANGELOG table and use it for the rollback.	Optional
`liquibase.command.driver: <string>` `liquibase.command.rollbackOneUpdateSql.driver: <string>`	The JDBC driver class	Optional
`liquibase.command.driverPropertiesFile: <string>` `liquibase.command.rollbackOneUpdateSql.driverPropertiesFile: <string>`	The JDBC driver properties file	Optional
`liquibase.command.outputDefaultCatalog: <true\|false>` `liquibase.command.rollbackOneUpdateSql.outputDefaultCatalog: <true\|false>`	Control whether names of objects in the default catalog are fully qualified or not. If `true`, they are. If `false`, only objects outside the default catalog are fully qualified. Default: `true`.	Optional
`liquibase.command.outputDefaultSchema: <true\|false>` `liquibase.command.rollbackOneUpdateSql.outputDefaultSchema: <true\|false>`	Control whether names of objects in the default schema are fully qualified or not. If `true`, they are. If `false`, only objects outside the default schema are fully qualified. Default: `true`.	Optional
`liquibase.command.password: <string>` `liquibase.command.rollbackOneUpdateSql.password: <string>`	Password to connect to the target database.	Optional
`liquibase.command.rollbackScript: <string>` `liquibase.command.rollbackOneUpdateSql.rollbackScript: <string>`	The path to the script to use to perform the rollback. Only needed if the rollback is not already defined in the changelog, and if it is not a rollback statement that Liquibase automatically generates.	Optional
`liquibase.command.username: <string>` `liquibase.command.rollbackOneUpdateSql.username: <string>`	Username to connect to the target database.	Optional

Global parameters

Parameter	Definition	Requirement
`JAVA_OPTS=-Dliquibase.licenseKey=<string>`	Your Liquibase Pro license key	Required
`JAVA_OPTS=-Dliquibase.outputFile=<string>`	File path to where the command output will be written. If not specified, output goes to `STDOUT`. See `--output-file`.	Optional

Command parameters

Parameter	Definition	Requirement
`JAVA_OPTS=-Dliquibase.command.changelogFile=<string>` `JAVA_OPTS=-Dliquibase.command.rollbackOneUpdateSql.changelogFile=<string>`	The root changelog	Required
`JAVA_OPTS=-Dliquibase.command.url=<string>` `JAVA_OPTS=-Dliquibase.command.rollbackOneUpdateSql.url=<string>`	The JDBC database connection URL.	Required
`JAVA_OPTS=-Dliquibase.command.defaultCatalogName=<string>` `JAVA_OPTS=-Dliquibase.command.rollbackOneUpdateSql.defaultCatalogName=<string>`	Name of the default catalog to use for the database connection	Optional
`JAVA_OPTS=-Dliquibase.command.defaultSchemaName=<string>` `JAVA_OPTS=-Dliquibase.command.rollbackOneUpdateSql.defaultSchemaName=<string>`	Name of the default schema to use for the database connection. If `defaultSchemaName` is set, then objects do not have to be fully qualified. This means you can refer to just `mytable` instead of `myschema.mytable`. Note: In the properties file and `JAVA_OPTS` only: in 4.18.0 and earlier, specify this parameter using the syntax `defaultSchemaName`. In 4.19.0 and later, use the syntax `liquibase.command.defaultSchemaName`. Note: In Liquibase 4.12.0 and later, you can use mixed-case schema names if you set `--preserve-schema-case` to `true`. However, in Liquibase 4.12.0–4.22.0, the Liquibase validator still throws a `DatabaseException` error if you specify a mixed-case value of `defaultSchemaName`. In 4.23.0 and later, the Liquibase validator accepts any casing.	Optional
`JAVA_OPTS=-Dliquibase.command.deploymentId=<string>` `JAVA_OPTS=-Dliquibase.command.rollbackOneUpdateSql.deploymentId=<string>`	Specifies the deployment ID of all rows from the DATABASECHANGELOG table related to the changesets intended for rollback. If not supplied, Liquibase Pro will look up the most recent deployment ID from the DATABASECHANGELOG table and use it for the rollback.	Optional
`JAVA_OPTS=-Dliquibase.command.driver=<string>` `JAVA_OPTS=-Dliquibase.command.rollbackOneUpdateSql.driver=<string>`	The JDBC driver class	Optional
`JAVA_OPTS=-Dliquibase.command.driverPropertiesFile=<string>` `JAVA_OPTS=-Dliquibase.command.rollbackOneUpdateSql.driverPropertiesFile=<string>`	The JDBC driver properties file	Optional
`JAVA_OPTS=-Dliquibase.command.outputDefaultCatalog=<true\|false>` `JAVA_OPTS=-Dliquibase.command.rollbackOneUpdateSql.outputDefaultCatalog=<true\|false>`	Control whether names of objects in the default catalog are fully qualified or not. If `true`, they are. If `false`, only objects outside the default catalog are fully qualified. Default: `true`.	Optional
`JAVA_OPTS=-Dliquibase.command.outputDefaultSchema=<true\|false>` `JAVA_OPTS=-Dliquibase.command.rollbackOneUpdateSql.outputDefaultSchema=<true\|false>`	Control whether names of objects in the default schema are fully qualified or not. If `true`, they are. If `false`, only objects outside the default schema are fully qualified. Default: `true`.	Optional
`JAVA_OPTS=-Dliquibase.command.password=<string>` `JAVA_OPTS=-Dliquibase.command.rollbackOneUpdateSql.password=<string>`	Password to connect to the target database.	Optional
`JAVA_OPTS=-Dliquibase.command.rollbackScript=<string>` `JAVA_OPTS=-Dliquibase.command.rollbackOneUpdateSql.rollbackScript=<string>`	The path to the script to use to perform the rollback. Only needed if the rollback is not already defined in the changelog, and if it is not a rollback statement that Liquibase automatically generates.	Optional
`JAVA_OPTS=-Dliquibase.command.username=<string>` `JAVA_OPTS=-Dliquibase.command.rollbackOneUpdateSql.username=<string>`	Username to connect to the target database.	Optional

Global parameters

Parameter	Definition	Requirement
`LIQUIBASE_LICENSE_KEY=<string>`	Your Liquibase Pro license key	Required
`LIQUIBASE_OUTPUT_FILE=<string>`	File path to where the command output will be written. If not specified, output goes to `STDOUT`. See `--output-file`.	Optional

Command parameters

Parameter	Definition	Requirement
`LIQUIBASE_COMMAND_CHANGELOG_FILE=<string>` `LIQUIBASE_COMMAND_ROLLBACK_ONE_UPDATE_SQL_CHANGELOG_FILE=<string>`	The root changelog	Required
`LIQUIBASE_COMMAND_URL=<string>` `LIQUIBASE_COMMAND_ROLLBACK_ONE_UPDATE_SQL_URL=<string>`	The JDBC database connection URL.	Required
`LIQUIBASE_COMMAND_DEFAULT_CATALOG_NAME=<string>` `LIQUIBASE_COMMAND_ROLLBACK_ONE_UPDATE_SQL_DEFAULT_CATALOG_NAME=<string>`	Name of the default catalog to use for the database connection	Optional
`LIQUIBASE_COMMAND_DEFAULT_SCHEMA_NAME=<string>` `LIQUIBASE_COMMAND_ROLLBACK_ONE_UPDATE_SQL_DEFAULT_SCHEMA_NAME=<string>`	Name of the default schema to use for the database connection. If `defaultSchemaName` is set, then objects do not have to be fully qualified. This means you can refer to just `mytable` instead of `myschema.mytable`. Note: In the properties file and `JAVA_OPTS` only: in 4.18.0 and earlier, specify this parameter using the syntax `defaultSchemaName`. In 4.19.0 and later, use the syntax `liquibase.command.defaultSchemaName`. Note: In Liquibase 4.12.0 and later, you can use mixed-case schema names if you set `--preserve-schema-case` to `true`. However, in Liquibase 4.12.0–4.22.0, the Liquibase validator still throws a `DatabaseException` error if you specify a mixed-case value of `defaultSchemaName`. In 4.23.0 and later, the Liquibase validator accepts any casing.	Optional
`LIQUIBASE_COMMAND_DEPLOYMENT_ID=<string>` `LIQUIBASE_COMMAND_ROLLBACK_ONE_UPDATE_SQL_DEPLOYMENT_ID=<string>`	Specifies the deployment ID of all rows from the DATABASECHANGELOG table related to the changesets intended for rollback. If not supplied, Liquibase Pro will look up the most recent deployment ID from the DATABASECHANGELOG table and use it for the rollback.	Optional
`LIQUIBASE_COMMAND_DRIVER=<string>` `LIQUIBASE_COMMAND_ROLLBACK_ONE_UPDATE_SQL_DRIVER=<string>`	The JDBC driver class	Optional
`LIQUIBASE_COMMAND_DRIVER_PROPERTIES_FILE=<string>` `LIQUIBASE_COMMAND_ROLLBACK_ONE_UPDATE_SQL_DRIVER_PROPERTIES_FILE=<string>`	The JDBC driver properties file	Optional
`LIQUIBASE_COMMAND_OUTPUT_DEFAULT_CATALOG=<true\|false>` `LIQUIBASE_COMMAND_ROLLBACK_ONE_UPDATE_SQL_OUTPUT_DEFAULT_CATALOG=<true\|false>`	Control whether names of objects in the default catalog are fully qualified or not. If `true`, they are. If `false`, only objects outside the default catalog are fully qualified. Default: `true`.	Optional
`LIQUIBASE_COMMAND_OUTPUT_DEFAULT_SCHEMA=<true\|false>` `LIQUIBASE_COMMAND_ROLLBACK_ONE_UPDATE_SQL_OUTPUT_DEFAULT_SCHEMA=<true\|false>`	Control whether names of objects in the default schema are fully qualified or not. If `true`, they are. If `false`, only objects outside the default schema are fully qualified. Default: `true`.	Optional
`LIQUIBASE_COMMAND_PASSWORD=<string>` `LIQUIBASE_COMMAND_ROLLBACK_ONE_UPDATE_SQL_PASSWORD=<string>`	Password to connect to the target database.	Optional
`LIQUIBASE_COMMAND_ROLLBACK_SCRIPT=<string>` `LIQUIBASE_COMMAND_ROLLBACK_ONE_UPDATE_SQL_ROLLBACK_SCRIPT=<string>`	The path to the script to use to perform the rollback. Only needed if the rollback is not already defined in the changelog, and if it is not a rollback statement that Liquibase automatically generates.	Optional
`LIQUIBASE_COMMAND_USERNAME=<string>` `LIQUIBASE_COMMAND_ROLLBACK_ONE_UPDATE_SQL_USERNAME=<string>`	Username to connect to the target database.	Optional

Global parameters

Parameter	Definition	Requirement
`--license-key=<string>`	Your Liquibase Pro license key	Required
`--output-file=<string>`	File path to where the command output will be written. If not specified, output goes to `STDOUT`. See `--output-file`.	Optional

Command parameters

Parameter	Definition	Requirement
`--changelog-file=<string>`	The root changelog	Required
`--url=<string>`	The JDBC database connection URL.	Required
`--default-catalog-name=<string>`	Name of the default catalog to use for the database connection	Optional
`--default-schema-name=<string>`	Name of the default schema to use for the database connection. If `defaultSchemaName` is set, then objects do not have to be fully qualified. This means you can refer to just `mytable` instead of `myschema.mytable`. Note: In the properties file and `JAVA_OPTS` only: in 4.18.0 and earlier, specify this parameter using the syntax `defaultSchemaName`. In 4.19.0 and later, use the syntax `liquibase.command.defaultSchemaName`. Note: In Liquibase 4.12.0 and later, you can use mixed-case schema names if you set `--preserve-schema-case` to `true`. However, in Liquibase 4.12.0–4.22.0, the Liquibase validator still throws a `DatabaseException` error if you specify a mixed-case value of `defaultSchemaName`. In 4.23.0 and later, the Liquibase validator accepts any casing.	Optional
`--deployment-id=<string>`	Specifies the deployment ID of all rows from the DATABASECHANGELOG table related to the changesets intended for rollback. If not supplied, Liquibase Pro will look up the most recent deployment ID from the DATABASECHANGELOG table and use it for the rollback.	Optional
`--driver=<string>`	The JDBC driver class	Optional
`--driver-properties-file=<string>`	The JDBC driver properties file	Optional
`--output-default-catalog=<true\|false>`	Control whether names of objects in the default catalog are fully qualified or not. If `true`, they are. If `false`, only objects outside the default catalog are fully qualified. Default: `true`.	Optional
`--output-default-schema=<true\|false>`	Control whether names of objects in the default schema are fully qualified or not. If `true`, they are. If `false`, only objects outside the default schema are fully qualified. Default: `true`.	Optional
`--password=<string>`	Password to connect to the target database.	Optional
`--rollback-script=<string>`	The path to the script to use to perform the rollback. Only needed if the rollback is not already defined in the changelog, and if it is not a rollback statement that Liquibase automatically generates.	Optional
`--username=<string>`	Username to connect to the target database.	Optional

Global parameters

Parameter	Definition	Requirement
`globalArgs: { license-key: "<string>" }`	Your Liquibase Pro license key	Required
`globalArgs: { output-file: "<string>" }`	File path to where the command output will be written. If not specified, output goes to `STDOUT`. See `--output-file`.	Optional

Command parameters

Parameter	Definition	Requirement
`cmdArgs: { changelog-file: "<string>" }`	The root changelog	Required
`cmdArgs: { url: "<string>" }`	The JDBC database connection URL.	Required
`cmdArgs: { default-catalog-name: "<string>" }`	Name of the default catalog to use for the database connection	Optional
`cmdArgs: { default-schema-name: "<string>" }`	Name of the default schema to use for the database connection. If `defaultSchemaName` is set, then objects do not have to be fully qualified. This means you can refer to just `mytable` instead of `myschema.mytable`. Note: In the properties file and `JAVA_OPTS` only: in 4.18.0 and earlier, specify this parameter using the syntax `defaultSchemaName`. In 4.19.0 and later, use the syntax `liquibase.command.defaultSchemaName`. Note: In Liquibase 4.12.0 and later, you can use mixed-case schema names if you set `--preserve-schema-case` to `true`. However, in Liquibase 4.12.0–4.22.0, the Liquibase validator still throws a `DatabaseException` error if you specify a mixed-case value of `defaultSchemaName`. In 4.23.0 and later, the Liquibase validator accepts any casing.	Optional
`cmdArgs: { deployment-id: "<string>" }`	Specifies the deployment ID of all rows from the DATABASECHANGELOG table related to the changesets intended for rollback. If not supplied, Liquibase Pro will look up the most recent deployment ID from the DATABASECHANGELOG table and use it for the rollback.	Optional
`cmdArgs: { driver: "<string>" }`	The JDBC driver class	Optional
`cmdArgs: { driver-properties-file: "<string>" }`	The JDBC driver properties file	Optional
`cmdArgs: { output-default-catalog: "<true\|false>" }`	Control whether names of objects in the default catalog are fully qualified or not. If `true`, they are. If `false`, only objects outside the default catalog are fully qualified. Default: `true`.	Optional
`cmdArgs: { output-default-schema: "<true\|false>" }`	Control whether names of objects in the default schema are fully qualified or not. If `true`, they are. If `false`, only objects outside the default schema are fully qualified. Default: `true`.	Optional
`cmdArgs: { password: "<string>" }`	Password to connect to the target database.	Optional
`cmdArgs: { rollback-script: "<string>" }`	The path to the script to use to perform the rollback. Only needed if the rollback is not already defined in the changelog, and if it is not a rollback statement that Liquibase automatically generates.	Optional
`cmdArgs: { username: "<string>" }`	Username to connect to the target database.	Optional

Global parameters

Parameter	Definition	Requirement
`liquibase.licenseKey: <string>`	Your Liquibase Pro license key	Required
`liquibase.outputFile: <string>`	File path to where the command output will be written. If not specified, output goes to `STDOUT`. See `--output-file`.	Optional

Command parameters

Parameter	Definition	Requirement
`liquibase.command.changelogFile: <string>` `liquibase.command.rollbackOneUpdateSql.changelogFile: <string>`	The root changelog	Required
`liquibase.command.url: <string>` `liquibase.command.rollbackOneUpdateSql.url: <string>`	The JDBC database connection URL.	Required
`liquibase.command.defaultCatalogName: <string>` `liquibase.command.rollbackOneUpdateSql.defaultCatalogName: <string>`	Name of the default catalog to use for the database connection	Optional
`liquibase.command.defaultSchemaName: <string>` `liquibase.command.rollbackOneUpdateSql.defaultSchemaName: <string>`	Name of the default schema to use for the database connection. If `defaultSchemaName` is set, then objects do not have to be fully qualified. This means you can refer to just `mytable` instead of `myschema.mytable`. Note: In the properties file and `JAVA_OPTS` only: in 4.18.0 and earlier, specify this parameter using the syntax `defaultSchemaName`. In 4.19.0 and later, use the syntax `liquibase.command.defaultSchemaName`. Note: In Liquibase 4.12.0 and later, you can use mixed-case schema names if you set `--preserve-schema-case` to `true`. However, in Liquibase 4.12.0–4.22.0, the Liquibase validator still throws a `DatabaseException` error if you specify a mixed-case value of `defaultSchemaName`. In 4.23.0 and later, the Liquibase validator accepts any casing.	Optional
`liquibase.command.deploymentId: <string>` `liquibase.command.rollbackOneUpdateSql.deploymentId: <string>`	Specifies the deployment ID of all rows from the DATABASECHANGELOG table related to the changesets intended for rollback. If not supplied, Liquibase Pro will look up the most recent deployment ID from the DATABASECHANGELOG table and use it for the rollback.	Optional
`liquibase.command.driver: <string>` `liquibase.command.rollbackOneUpdateSql.driver: <string>`	The JDBC driver class	Optional
`liquibase.command.driverPropertiesFile: <string>` `liquibase.command.rollbackOneUpdateSql.driverPropertiesFile: <string>`	The JDBC driver properties file	Optional
`liquibase.command.outputDefaultCatalog: <true\|false>` `liquibase.command.rollbackOneUpdateSql.outputDefaultCatalog: <true\|false>`	Control whether names of objects in the default catalog are fully qualified or not. If `true`, they are. If `false`, only objects outside the default catalog are fully qualified. Default: `true`.	Optional
`liquibase.command.outputDefaultSchema: <true\|false>` `liquibase.command.rollbackOneUpdateSql.outputDefaultSchema: <true\|false>`	Control whether names of objects in the default schema are fully qualified or not. If `true`, they are. If `false`, only objects outside the default schema are fully qualified. Default: `true`.	Optional
`liquibase.command.password: <string>` `liquibase.command.rollbackOneUpdateSql.password: <string>`	Password to connect to the target database.	Optional
`liquibase.command.rollbackScript: <string>` `liquibase.command.rollbackOneUpdateSql.rollbackScript: <string>`	The path to the script to use to perform the rollback. Only needed if the rollback is not already defined in the changelog, and if it is not a rollback statement that Liquibase automatically generates.	Optional
`liquibase.command.username: <string>` `liquibase.command.rollbackOneUpdateSql.username: <string>`	Username to connect to the target database.	Optional

Global parameters

Parameter	Definition	Requirement
`JAVA_OPTS=-Dliquibase.licenseKey=<string>`	Your Liquibase Pro license key	Required
`JAVA_OPTS=-Dliquibase.outputFile=<string>`	File path to where the command output will be written. If not specified, output goes to `STDOUT`. See `--output-file`.	Optional

Command parameters

Parameter	Definition	Requirement
`JAVA_OPTS=-Dliquibase.command.changelogFile=<string>` `JAVA_OPTS=-Dliquibase.command.rollbackOneUpdateSql.changelogFile=<string>`	The root changelog	Required
`JAVA_OPTS=-Dliquibase.command.url=<string>` `JAVA_OPTS=-Dliquibase.command.rollbackOneUpdateSql.url=<string>`	The JDBC database connection URL.	Required
`JAVA_OPTS=-Dliquibase.command.defaultCatalogName=<string>` `JAVA_OPTS=-Dliquibase.command.rollbackOneUpdateSql.defaultCatalogName=<string>`	Name of the default catalog to use for the database connection	Optional
`JAVA_OPTS=-Dliquibase.command.defaultSchemaName=<string>` `JAVA_OPTS=-Dliquibase.command.rollbackOneUpdateSql.defaultSchemaName=<string>`	Name of the default schema to use for the database connection. If `defaultSchemaName` is set, then objects do not have to be fully qualified. This means you can refer to just `mytable` instead of `myschema.mytable`. Note: In the properties file and `JAVA_OPTS` only: in 4.18.0 and earlier, specify this parameter using the syntax `defaultSchemaName`. In 4.19.0 and later, use the syntax `liquibase.command.defaultSchemaName`. Note: In Liquibase 4.12.0 and later, you can use mixed-case schema names if you set `--preserve-schema-case` to `true`. However, in Liquibase 4.12.0–4.22.0, the Liquibase validator still throws a `DatabaseException` error if you specify a mixed-case value of `defaultSchemaName`. In 4.23.0 and later, the Liquibase validator accepts any casing.	Optional
`JAVA_OPTS=-Dliquibase.command.deploymentId=<string>` `JAVA_OPTS=-Dliquibase.command.rollbackOneUpdateSql.deploymentId=<string>`	Specifies the deployment ID of all rows from the DATABASECHANGELOG table related to the changesets intended for rollback. If not supplied, Liquibase Pro will look up the most recent deployment ID from the DATABASECHANGELOG table and use it for the rollback.	Optional
`JAVA_OPTS=-Dliquibase.command.driver=<string>` `JAVA_OPTS=-Dliquibase.command.rollbackOneUpdateSql.driver=<string>`	The JDBC driver class	Optional
`JAVA_OPTS=-Dliquibase.command.driverPropertiesFile=<string>` `JAVA_OPTS=-Dliquibase.command.rollbackOneUpdateSql.driverPropertiesFile=<string>`	The JDBC driver properties file	Optional
`JAVA_OPTS=-Dliquibase.command.outputDefaultCatalog=<true\|false>` `JAVA_OPTS=-Dliquibase.command.rollbackOneUpdateSql.outputDefaultCatalog=<true\|false>`	Control whether names of objects in the default catalog are fully qualified or not. If `true`, they are. If `false`, only objects outside the default catalog are fully qualified. Default: `true`.	Optional
`JAVA_OPTS=-Dliquibase.command.outputDefaultSchema=<true\|false>` `JAVA_OPTS=-Dliquibase.command.rollbackOneUpdateSql.outputDefaultSchema=<true\|false>`	Control whether names of objects in the default schema are fully qualified or not. If `true`, they are. If `false`, only objects outside the default schema are fully qualified. Default: `true`.	Optional
`JAVA_OPTS=-Dliquibase.command.password=<string>` `JAVA_OPTS=-Dliquibase.command.rollbackOneUpdateSql.password=<string>`	Password to connect to the target database.	Optional
`JAVA_OPTS=-Dliquibase.command.rollbackScript=<string>` `JAVA_OPTS=-Dliquibase.command.rollbackOneUpdateSql.rollbackScript=<string>`	The path to the script to use to perform the rollback. Only needed if the rollback is not already defined in the changelog, and if it is not a rollback statement that Liquibase automatically generates.	Optional
`JAVA_OPTS=-Dliquibase.command.username=<string>` `JAVA_OPTS=-Dliquibase.command.rollbackOneUpdateSql.username=<string>`	Username to connect to the target database.	Optional

Global parameters

Parameter	Definition	Requirement
`LIQUIBASE_LICENSE_KEY=<string>`	Your Liquibase Pro license key	Required
`LIQUIBASE_OUTPUT_FILE=<string>`	File path to where the command output will be written. If not specified, output goes to `STDOUT`. See `--output-file`.	Optional

Command parameters

Parameter	Definition	Requirement
`LIQUIBASE_COMMAND_CHANGELOG_FILE=<string>` `LIQUIBASE_COMMAND_ROLLBACK_ONE_UPDATE_SQL_CHANGELOG_FILE=<string>`	The root changelog	Required
`LIQUIBASE_COMMAND_URL=<string>` `LIQUIBASE_COMMAND_ROLLBACK_ONE_UPDATE_SQL_URL=<string>`	The JDBC database connection URL.	Required
`LIQUIBASE_COMMAND_DEFAULT_CATALOG_NAME=<string>` `LIQUIBASE_COMMAND_ROLLBACK_ONE_UPDATE_SQL_DEFAULT_CATALOG_NAME=<string>`	Name of the default catalog to use for the database connection	Optional
`LIQUIBASE_COMMAND_DEFAULT_SCHEMA_NAME=<string>` `LIQUIBASE_COMMAND_ROLLBACK_ONE_UPDATE_SQL_DEFAULT_SCHEMA_NAME=<string>`	Name of the default schema to use for the database connection. If `defaultSchemaName` is set, then objects do not have to be fully qualified. This means you can refer to just `mytable` instead of `myschema.mytable`. Note: In the properties file and `JAVA_OPTS` only: in 4.18.0 and earlier, specify this parameter using the syntax `defaultSchemaName`. In 4.19.0 and later, use the syntax `liquibase.command.defaultSchemaName`. Note: In Liquibase 4.12.0 and later, you can use mixed-case schema names if you set `--preserve-schema-case` to `true`. However, in Liquibase 4.12.0–4.22.0, the Liquibase validator still throws a `DatabaseException` error if you specify a mixed-case value of `defaultSchemaName`. In 4.23.0 and later, the Liquibase validator accepts any casing.	Optional
`LIQUIBASE_COMMAND_DEPLOYMENT_ID=<string>` `LIQUIBASE_COMMAND_ROLLBACK_ONE_UPDATE_SQL_DEPLOYMENT_ID=<string>`	Specifies the deployment ID of all rows from the DATABASECHANGELOG table related to the changesets intended for rollback. If not supplied, Liquibase Pro will look up the most recent deployment ID from the DATABASECHANGELOG table and use it for the rollback.	Optional
`LIQUIBASE_COMMAND_DRIVER=<string>` `LIQUIBASE_COMMAND_ROLLBACK_ONE_UPDATE_SQL_DRIVER=<string>`	The JDBC driver class	Optional
`LIQUIBASE_COMMAND_DRIVER_PROPERTIES_FILE=<string>` `LIQUIBASE_COMMAND_ROLLBACK_ONE_UPDATE_SQL_DRIVER_PROPERTIES_FILE=<string>`	The JDBC driver properties file	Optional
`LIQUIBASE_COMMAND_OUTPUT_DEFAULT_CATALOG=<true\|false>` `LIQUIBASE_COMMAND_ROLLBACK_ONE_UPDATE_SQL_OUTPUT_DEFAULT_CATALOG=<true\|false>`	Control whether names of objects in the default catalog are fully qualified or not. If `true`, they are. If `false`, only objects outside the default catalog are fully qualified. Default: `true`.	Optional
`LIQUIBASE_COMMAND_OUTPUT_DEFAULT_SCHEMA=<true\|false>` `LIQUIBASE_COMMAND_ROLLBACK_ONE_UPDATE_SQL_OUTPUT_DEFAULT_SCHEMA=<true\|false>`	Control whether names of objects in the default schema are fully qualified or not. If `true`, they are. If `false`, only objects outside the default schema are fully qualified. Default: `true`.	Optional
`LIQUIBASE_COMMAND_PASSWORD=<string>` `LIQUIBASE_COMMAND_ROLLBACK_ONE_UPDATE_SQL_PASSWORD=<string>`	Password to connect to the target database.	Optional
`LIQUIBASE_COMMAND_ROLLBACK_SCRIPT=<string>` `LIQUIBASE_COMMAND_ROLLBACK_ONE_UPDATE_SQL_ROLLBACK_SCRIPT=<string>`	The path to the script to use to perform the rollback. Only needed if the rollback is not already defined in the changelog, and if it is not a rollback statement that Liquibase automatically generates.	Optional
`LIQUIBASE_COMMAND_USERNAME=<string>` `LIQUIBASE_COMMAND_ROLLBACK_ONE_UPDATE_SQL_USERNAME=<string>`	Username to connect to the target database.	Optional

Output

When successful, the rollback-one-update-sql command produces the following output:

Liquibase Version: 4.9.1 Liquibase Secure 4.9.1 by Liquibase licensed to Liquibase Secure Evaluation until Tue Jun 07 18:00:00 MDT 2022 WARNING! Your license will expire in 29 days! To renew Liquibase Secure please contact sales@liquibase.com or go to https://www.liquibase.org/download Defaulting to last deployment ID '2214257654' rollback-one-update executed for DBUSER@jdbc:h2:tcp://localhost:9090/mem:dev -- ********************************************************************* --rollback deployment ID '2214257654' -- ********************************************************************* -- Change Log: example-changelog.sql -- Ran at: 5/10/22, 2:26 PM -- Against: DBUSER@jdbc:h2:tcp://localhost:9090/mem:dev -- Liquibase version: 4.9.1 -- ********************************************************************* -- Lock Database UPDATE PUBLIC.DATABASECHANGELOGLOCK SET LOCKED = TRUE, LOCKEDBY = 'DESKTOP-SQVSSV2 (192.168.1.179)', LOCKGRANTED = NOW() WHERE ID = 1 AND LOCKED = FALSE; -- Rolling Back ChangeSet: example-changelog.sql::3::other.dev ALTER TABLE person DROP COLUMN country; DELETE FROM PUBLIC.DATABASECHANGELOG WHERE ID = '3' AND AUTHOR = 'other.dev' AND FILENAME = 'example-changelog.sql'; -- Rolling Back ChangeSet: example-changelog.sql::2::your.name DROP TABLE company; DELETE FROM PUBLIC.DATABASECHANGELOG WHERE ID = '2' AND AUTHOR = 'your.name' AND FILENAME = 'example-changelog.sql'; -- Rolling Back ChangeSet: example-changelog.sql::1::your.name DROP TABLE person; DELETE FROM PUBLIC.DATABASECHANGELOG WHERE ID = '1' AND AUTHOR = 'your.name' AND FILENAME = 'example-changelog.sql'; -- Release Database Lock UPDATE PUBLIC.DATABASECHANGELOGLOCK SET LOCKED = FALSE, LOCKEDBY = NULL, LOCKGRANTED = NULL WHERE ID = 1; Liquibase command 'rollback-one-update-sql' was executed successfully.