`update-count`

The update-count command sequentially updates a specified number of changesets on your database.

Uses

The update-count command is mainly used when you want to apply changes and update changesets sequentially, starting with the changesets from the top of the changelog file until the number specified is reached.

The image below shows four changesets: changeset a, changeset b, changeset c, and changeset d. As you can see, changeset a is already deployed on the database. So, running the command update-count --count=2 deploys changeset b and c without applying changeset d.

Additionally, the best practice is to run the update-count-sql helper command because it allows you to inspect the update-count SQL, so you can correct any issues that may arise before running the command.

In Liquibase Pro 4.25.1 and later, you can automatically generate a database Update Report summarizing this command.

Syntax

To run the update-count command, specify the driver, classpath, and URL in the Liquibase properties file. For more information, see Create and Configure a liquibase.properties File. You can also specify them from the command line.

Then run the update-count command:

liquibase update-count --count=2 --changelog-file=example-changelog.xml

Note: The --count=myCount syntax was added in Liquibase 4.4. If you use an older version, specify your count as a positional argument: <command> myCount.

Command parameters

Attribute	Definition	Requirement
`--changelog-file=<string>`	The root changelog	Required
`--count=<int>`	Integer specifying how many changes Liquibase applies the command to. Specify as `--count=myCount`. Positional format `<command> <count>` deprecated in 4.4+.	Required
`--url=<string>`	The JDBC database connection URL. See Using JDBC URL in Liquibase.	Required
`--change-exec-listener-class=<string>`	Fully-qualified class which specifies a `ChangeExecListener`. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`--change-exec-listener-properties-file=<string>`	Path to a properties file for the `ChangeExecListener` class. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`--context-filter=<string>`	Specifies the changeset contexts to match. Contexts are tags you can add to changesets to control which changesets are executed in any particular migration run. Note: If you use Liquibase 4.23.0 or earlier, use the syntax `--contexts` instead of `--context-filter`.	Optional
`--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
`--driver=<string>`	The JDBC driver class	Optional
`--driver-properties-file=<string>`	The JDBC driver properties file	Optional
`--force-on-partial-changes=<true\|false>`	Liquibase Pro only. Use this argument only if you are specifying `--rollback-on-error=true` to automatically roll back `update` operations containing errors. `--force-on-partial-changes=true` specifies whether Liquibase rolls back partially invalid changesets, such as a changeset containing two changes: one with an error and one without an error. This ensures that you can successfully roll back all changes if a deployment has an error, even if the changeset contains multiple changes. Available in Liquibase 4.25.0+. Default: `false`. See also: `failOnError`.	Optional
`--label-filter=<string>`	Specifies the changeset labels to match. Labels are tags you can add to changesets to control which changesets will be executed in any migration run.	Optional
`--password=<string>`	Password to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional
`--report-enabled=<true\|false>`	Enables a report at the command level. Overrides the global parameter `--reports-enabled`. Default: `true`.	Optional
`--report-name=<string>`	Specifies the name of the report file at the command level. Overrides the global parameter `--reports-name`. By default, Liquibase generates a new report file labeled with a timestamp (user's local time). If you set a custom name, Liquibase overwrites the existing file every time you generate a new report. Default: `report-<DD-Mon-YYYY-HHmmss>.html`.	Optional
`--report-path=<string>`	Specifies the file path to the report file at the command level. Overrides the global parameter `--reports-path`. Default: `./`.	Optional
`--report-suppress-exception=<true\|false>`	Liquibase 4.31.0+. Specifies whether to hide exceptions (which may contain SQL) from the operation report at the command level. Overrides the global parameter `--reports-suppress-exception`. Default: `false`. However: If `--report-suppress-exception` is not set and `--report-suppress-sql=true`, Liquibase suppresses all SQL, including exception SQL. If `--report-suppress-exception=false` and `--report-suppress-sql=true`, Liquibase suppresses most SQL but shows exception SQL.	Optional
`--report-suppress-sql=<true\|false>`	Liquibase 4.31.0+. Specifies whether to hide changeset SQL in operation reports at the command level. Overridden by the global parameter `--reports-suppress-sql`. Default: `false`.	Optional
`--rollback-on-error=<true\|false>`	Liquibase Pro only. If any changeset in a deployment fails, `--rollback-on-error` stops the `update` operation and rolls back all changesets you just deployed. Available in Liquibase 4.18.0+. Default: `false`. Note: A changeset marked `failOnError=false` does not trigger as an error, so `rollback-on-error` will not occur. Additionally, if a changeset is not auto-rollback compliant or does not have a rollback script, then `rollback-on-error` does not occur for any changeset. Read more: `failOnError`.	Optional
`--show-summary=<string>`	Liquibase 4.24.0+. Produces a summary list of any changesets skipped and why they were skipped. Valid values are `OFF`, `SUMMARY`, and `VERBOSE`. In Liquibase Pro, `SUMMARY` and `VERBOSE` provide additional information about failed deployments. Default: `SUMMARY`. Note: Liquibase may display one or multiple reasons for halting deployment of a changeset. If Liquibase cannot resolve a halting reason, it does not evaluate the changeset for other possible halting reasons.	Optional
`--show-summary-output=<string>`	Liquibase 4.24.0+. Summary output to report update summary results. Valid values are `LOG`, `CONSOLE`, and `ALL`. If set to `LOG`, the `--show-summary` output is sent to the file specified in `--log-file`. If set to `CONSOLE`, the `--show-summary` output is sent to `STDOUT`. If set to `ALL`, the `--show-summary` output is sent to both locations. Default: ALL.	Optional
`--username=<string>`	Username to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional

Attribute	Definition	Requirement
`cmdArgs: { changelog-file: "<string>" }`	The root changelog	Required
`cmdArgs: { count: "<int>" }`	Integer specifying how many changes Liquibase applies the command to. Specify as `--count=myCount`. Positional format `<command> <count>` deprecated in 4.4+.	Required
`cmdArgs: { url: "<string>" }`	The JDBC database connection URL. See Using JDBC URL in Liquibase.	Required
`cmdArgs: { change-exec-listener-class: "<string>" }`	Fully-qualified class which specifies a `ChangeExecListener`. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`cmdArgs: { change-exec-listener-properties-file: "<string>" }`	Path to a properties file for the `ChangeExecListener` class. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`cmdArgs: { context-filter: "<string>" }`	Specifies the changeset contexts to match. Contexts are tags you can add to changesets to control which changesets are executed in any particular migration run. Note: If you use Liquibase 4.23.0 or earlier, use the syntax `--contexts` instead of `--context-filter`.	Optional
`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: { driver: "<string>" }`	The JDBC driver class	Optional
`cmdArgs: { driver-properties-file: "<string>" }`	The JDBC driver properties file	Optional
`cmdArgs: { force-on-partial-changes: "<true\|false>" }`	Liquibase Pro only. Use this argument only if you are specifying `--rollback-on-error=true` to automatically roll back `update` operations containing errors. `--force-on-partial-changes=true` specifies whether Liquibase rolls back partially invalid changesets, such as a changeset containing two changes: one with an error and one without an error. This ensures that you can successfully roll back all changes if a deployment has an error, even if the changeset contains multiple changes. Available in Liquibase 4.25.0+. Default: `false`. See also: `failOnError`.	Optional
`cmdArgs: { label-filter: "<string>" }`	Specifies the changeset labels to match. Labels are tags you can add to changesets to control which changesets will be executed in any migration run.	Optional
`cmdArgs: { password: "<string>" }`	Password to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional
`cmdArgs: { report-enabled: "<true\|false>" }`	Enables a report at the command level. Overrides the global parameter `--reports-enabled`. Default: `true`.	Optional
`cmdArgs: { report-name: "<string>" }`	Specifies the name of the report file at the command level. Overrides the global parameter `--reports-name`. By default, Liquibase generates a new report file labeled with a timestamp (user's local time). If you set a custom name, Liquibase overwrites the existing file every time you generate a new report. Default: `report-<DD-Mon-YYYY-HHmmss>.html`.	Optional
`cmdArgs: { report-path: "<string>" }`	Specifies the file path to the report file at the command level. Overrides the global parameter `--reports-path`. Default: `./`.	Optional
`cmdArgs: { report-suppress-exception: "<true\|false>" }`	Liquibase 4.31.0+. Specifies whether to hide exceptions (which may contain SQL) from the operation report at the command level. Overrides the global parameter `--reports-suppress-exception`. Default: `false`. However: If `--report-suppress-exception` is not set and `--report-suppress-sql=true`, Liquibase suppresses all SQL, including exception SQL. If `--report-suppress-exception=false` and `--report-suppress-sql=true`, Liquibase suppresses most SQL but shows exception SQL.	Optional
`cmdArgs: { report-suppress-sql: "<true\|false>" }`	Liquibase 4.31.0+. Specifies whether to hide changeset SQL in operation reports at the command level. Overridden by the global parameter `--reports-suppress-sql`. Default: `false`.	Optional
`cmdArgs: { rollback-on-error: "<true\|false>" }`	Liquibase Pro only. If any changeset in a deployment fails, `--rollback-on-error` stops the `update` operation and rolls back all changesets you just deployed. Available in Liquibase 4.18.0+. Default: `false`. Note: A changeset marked `failOnError=false` does not trigger as an error, so `rollback-on-error` will not occur. Additionally, if a changeset is not auto-rollback compliant or does not have a rollback script, then `rollback-on-error` does not occur for any changeset. Read more: `failOnError`.	Optional
`cmdArgs: { show-summary: "<string>" }`	Liquibase 4.24.0+. Produces a summary list of any changesets skipped and why they were skipped. Valid values are `OFF`, `SUMMARY`, and `VERBOSE`. In Liquibase Pro, `SUMMARY` and `VERBOSE` provide additional information about failed deployments. Default: `SUMMARY`. Note: Liquibase may display one or multiple reasons for halting deployment of a changeset. If Liquibase cannot resolve a halting reason, it does not evaluate the changeset for other possible halting reasons.	Optional
`cmdArgs: { show-summary-output: "<string>" }`	Liquibase 4.24.0+. Summary output to report update summary results. Valid values are `LOG`, `CONSOLE`, and `ALL`. If set to `LOG`, the `--show-summary` output is sent to the file specified in `--log-file`. If set to `CONSOLE`, the `--show-summary` output is sent to `STDOUT`. If set to `ALL`, the `--show-summary` output is sent to both locations. Default: ALL.	Optional
`cmdArgs: { username: "<string>" }`	Username to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional

Attribute	Definition	Requirement
`liquibase.command.changelogFile: <string>` `liquibase.command.updateCount.changelogFile: <string>`	The root changelog	Required
`liquibase.command.count: <int>` `liquibase.command.updateCount.count: <int>`	Integer specifying how many changes Liquibase applies the command to. Specify as `--count=myCount`. Positional format `<command> <count>` deprecated in 4.4+.	Required
`liquibase.command.url: <string>` `liquibase.command.updateCount.url: <string>`	The JDBC database connection URL. See Using JDBC URL in Liquibase.	Required
`liquibase.command.changeExecListenerClass: <string>` `liquibase.command.updateCount.changeExecListenerClass: <string>`	Fully-qualified class which specifies a `ChangeExecListener`. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`liquibase.command.changeExecListenerPropertiesFile: <string>` `liquibase.command.updateCount.changeExecListenerPropertiesFile: <string>`	Path to a properties file for the `ChangeExecListener` class. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`liquibase.command.contextFilter: <string>` `liquibase.command.updateCount.contextFilter: <string>`	Specifies the changeset contexts to match. Contexts are tags you can add to changesets to control which changesets are executed in any particular migration run. Note: If you use Liquibase 4.23.0 or earlier, use the syntax `--contexts` instead of `--context-filter`.	Optional
`liquibase.command.defaultCatalogName: <string>` `liquibase.command.updateCount.defaultCatalogName: <string>`	Name of the default catalog to use for the database connection	Optional
`liquibase.command.defaultSchemaName: <string>` `liquibase.command.updateCount.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.driver: <string>` `liquibase.command.updateCount.driver: <string>`	The JDBC driver class	Optional
`liquibase.command.driverPropertiesFile: <string>` `liquibase.command.updateCount.driverPropertiesFile: <string>`	The JDBC driver properties file	Optional
`liquibase.command.forceOnPartialChanges: <true\|false>` `liquibase.command.updateCount.forceOnPartialChanges: <true\|false>`	Liquibase Pro only. Use this argument only if you are specifying `--rollback-on-error=true` to automatically roll back `update` operations containing errors. `--force-on-partial-changes=true` specifies whether Liquibase rolls back partially invalid changesets, such as a changeset containing two changes: one with an error and one without an error. This ensures that you can successfully roll back all changes if a deployment has an error, even if the changeset contains multiple changes. Available in Liquibase 4.25.0+. Default: `false`. See also: `failOnError`.	Optional
`liquibase.command.labelFilter: <string>` `liquibase.command.updateCount.labelFilter: <string>`	Specifies the changeset labels to match. Labels are tags you can add to changesets to control which changesets will be executed in any migration run.	Optional
`liquibase.command.password: <string>` `liquibase.command.updateCount.password: <string>`	Password to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional
`liquibase.command.reportEnabled: <true\|false>` `liquibase.command.updateCount.reportEnabled: <true\|false>`	Enables a report at the command level. Overrides the global parameter `--reports-enabled`. Default: `true`.	Optional
`liquibase.command.reportName: <string>` `liquibase.command.updateCount.reportName: <string>`	Specifies the name of the report file at the command level. Overrides the global parameter `--reports-name`. By default, Liquibase generates a new report file labeled with a timestamp (user's local time). If you set a custom name, Liquibase overwrites the existing file every time you generate a new report. Default: `report-<DD-Mon-YYYY-HHmmss>.html`.	Optional
`liquibase.command.reportPath: <string>` `liquibase.command.updateCount.reportPath: <string>`	Specifies the file path to the report file at the command level. Overrides the global parameter `--reports-path`. Default: `./`.	Optional
`liquibase.command.reportSuppressException: <true\|false>` `liquibase.command.updateCount.reportSuppressException: <true\|false>`	Liquibase 4.31.0+. Specifies whether to hide exceptions (which may contain SQL) from the operation report at the command level. Overrides the global parameter `--reports-suppress-exception`. Default: `false`. However: If `--report-suppress-exception` is not set and `--report-suppress-sql=true`, Liquibase suppresses all SQL, including exception SQL. If `--report-suppress-exception=false` and `--report-suppress-sql=true`, Liquibase suppresses most SQL but shows exception SQL.	Optional
`liquibase.command.reportSuppressSql: <true\|false>` `liquibase.command.updateCount.reportSuppressSql: <true\|false>`	Liquibase 4.31.0+. Specifies whether to hide changeset SQL in operation reports at the command level. Overridden by the global parameter `--reports-suppress-sql`. Default: `false`.	Optional
`liquibase.command.rollbackOnError: <true\|false>` `liquibase.command.updateCount.rollbackOnError: <true\|false>`	Liquibase Pro only. If any changeset in a deployment fails, `--rollback-on-error` stops the `update` operation and rolls back all changesets you just deployed. Available in Liquibase 4.18.0+. Default: `false`. Note: A changeset marked `failOnError=false` does not trigger as an error, so `rollback-on-error` will not occur. Additionally, if a changeset is not auto-rollback compliant or does not have a rollback script, then `rollback-on-error` does not occur for any changeset. Read more: `failOnError`.	Optional
`liquibase.command.showSummary: <string>` `liquibase.command.updateCount.showSummary: <string>`	Liquibase 4.24.0+. Produces a summary list of any changesets skipped and why they were skipped. Valid values are `OFF`, `SUMMARY`, and `VERBOSE`. In Liquibase Pro, `SUMMARY` and `VERBOSE` provide additional information about failed deployments. Default: `SUMMARY`. Note: Liquibase may display one or multiple reasons for halting deployment of a changeset. If Liquibase cannot resolve a halting reason, it does not evaluate the changeset for other possible halting reasons.	Optional
`liquibase.command.showSummaryOutput: <string>` `liquibase.command.updateCount.showSummaryOutput: <string>`	Liquibase 4.24.0+. Summary output to report update summary results. Valid values are `LOG`, `CONSOLE`, and `ALL`. If set to `LOG`, the `--show-summary` output is sent to the file specified in `--log-file`. If set to `CONSOLE`, the `--show-summary` output is sent to `STDOUT`. If set to `ALL`, the `--show-summary` output is sent to both locations. Default: ALL.	Optional
`liquibase.command.username: <string>` `liquibase.command.updateCount.username: <string>`	Username to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional

Attribute	Definition	Requirement
`JAVA_OPTS=-Dliquibase.command.changelogFile=<string>` `JAVA_OPTS=-Dliquibase.command.updateCount.changelogFile=<string>`	The root changelog	Required
`JAVA_OPTS=-Dliquibase.command.count=<int>` `JAVA_OPTS=-Dliquibase.command.updateCount.count=<int>`	Integer specifying how many changes Liquibase applies the command to. Specify as `--count=myCount`. Positional format `<command> <count>` deprecated in 4.4+.	Required
`JAVA_OPTS=-Dliquibase.command.url=<string>` `JAVA_OPTS=-Dliquibase.command.updateCount.url=<string>`	The JDBC database connection URL. See Using JDBC URL in Liquibase.	Required
`JAVA_OPTS=-Dliquibase.command.changeExecListenerClass=<string>` `JAVA_OPTS=-Dliquibase.command.updateCount.changeExecListenerClass=<string>`	Fully-qualified class which specifies a `ChangeExecListener`. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`JAVA_OPTS=-Dliquibase.command.changeExecListenerPropertiesFile=<string>` `JAVA_OPTS=-Dliquibase.command.updateCount.changeExecListenerPropertiesFile=<string>`	Path to a properties file for the `ChangeExecListener` class. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`JAVA_OPTS=-Dliquibase.command.contextFilter=<string>` `JAVA_OPTS=-Dliquibase.command.updateCount.contextFilter=<string>`	Specifies the changeset contexts to match. Contexts are tags you can add to changesets to control which changesets are executed in any particular migration run. Note: If you use Liquibase 4.23.0 or earlier, use the syntax `--contexts` instead of `--context-filter`.	Optional
`JAVA_OPTS=-Dliquibase.command.defaultCatalogName=<string>` `JAVA_OPTS=-Dliquibase.command.updateCount.defaultCatalogName=<string>`	Name of the default catalog to use for the database connection	Optional
`JAVA_OPTS=-Dliquibase.command.defaultSchemaName=<string>` `JAVA_OPTS=-Dliquibase.command.updateCount.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.driver=<string>` `JAVA_OPTS=-Dliquibase.command.updateCount.driver=<string>`	The JDBC driver class	Optional
`JAVA_OPTS=-Dliquibase.command.driverPropertiesFile=<string>` `JAVA_OPTS=-Dliquibase.command.updateCount.driverPropertiesFile=<string>`	The JDBC driver properties file	Optional
`JAVA_OPTS=-Dliquibase.command.forceOnPartialChanges=<true\|false>` `JAVA_OPTS=-Dliquibase.command.updateCount.forceOnPartialChanges=<true\|false>`	Liquibase Pro only. Use this argument only if you are specifying `--rollback-on-error=true` to automatically roll back `update` operations containing errors. `--force-on-partial-changes=true` specifies whether Liquibase rolls back partially invalid changesets, such as a changeset containing two changes: one with an error and one without an error. This ensures that you can successfully roll back all changes if a deployment has an error, even if the changeset contains multiple changes. Available in Liquibase 4.25.0+. Default: `false`. See also: `failOnError`.	Optional
`JAVA_OPTS=-Dliquibase.command.labelFilter=<string>` `JAVA_OPTS=-Dliquibase.command.updateCount.labelFilter=<string>`	Specifies the changeset labels to match. Labels are tags you can add to changesets to control which changesets will be executed in any migration run.	Optional
`JAVA_OPTS=-Dliquibase.command.password=<string>` `JAVA_OPTS=-Dliquibase.command.updateCount.password=<string>`	Password to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional
`JAVA_OPTS=-Dliquibase.command.reportEnabled=<true\|false>` `JAVA_OPTS=-Dliquibase.command.updateCount.reportEnabled=<true\|false>`	Enables a report at the command level. Overrides the global parameter `--reports-enabled`. Default: `true`.	Optional
`JAVA_OPTS=-Dliquibase.command.reportName=<string>` `JAVA_OPTS=-Dliquibase.command.updateCount.reportName=<string>`	Specifies the name of the report file at the command level. Overrides the global parameter `--reports-name`. By default, Liquibase generates a new report file labeled with a timestamp (user's local time). If you set a custom name, Liquibase overwrites the existing file every time you generate a new report. Default: `report-<DD-Mon-YYYY-HHmmss>.html`.	Optional
`JAVA_OPTS=-Dliquibase.command.reportPath=<string>` `JAVA_OPTS=-Dliquibase.command.updateCount.reportPath=<string>`	Specifies the file path to the report file at the command level. Overrides the global parameter `--reports-path`. Default: `./`.	Optional
`JAVA_OPTS=-Dliquibase.command.reportSuppressException=<true\|false>` `JAVA_OPTS=-Dliquibase.command.updateCount.reportSuppressException=<true\|false>`	Liquibase 4.31.0+. Specifies whether to hide exceptions (which may contain SQL) from the operation report at the command level. Overrides the global parameter `--reports-suppress-exception`. Default: `false`. However: If `--report-suppress-exception` is not set and `--report-suppress-sql=true`, Liquibase suppresses all SQL, including exception SQL. If `--report-suppress-exception=false` and `--report-suppress-sql=true`, Liquibase suppresses most SQL but shows exception SQL.	Optional
`JAVA_OPTS=-Dliquibase.command.reportSuppressSql=<true\|false>` `JAVA_OPTS=-Dliquibase.command.updateCount.reportSuppressSql=<true\|false>`	Liquibase 4.31.0+. Specifies whether to hide changeset SQL in operation reports at the command level. Overridden by the global parameter `--reports-suppress-sql`. Default: `false`.	Optional
`JAVA_OPTS=-Dliquibase.command.rollbackOnError=<true\|false>` `JAVA_OPTS=-Dliquibase.command.updateCount.rollbackOnError=<true\|false>`	Liquibase Pro only. If any changeset in a deployment fails, `--rollback-on-error` stops the `update` operation and rolls back all changesets you just deployed. Available in Liquibase 4.18.0+. Default: `false`. Note: A changeset marked `failOnError=false` does not trigger as an error, so `rollback-on-error` will not occur. Additionally, if a changeset is not auto-rollback compliant or does not have a rollback script, then `rollback-on-error` does not occur for any changeset. Read more: `failOnError`.	Optional
`JAVA_OPTS=-Dliquibase.command.showSummary=<string>` `JAVA_OPTS=-Dliquibase.command.updateCount.showSummary=<string>`	Liquibase 4.24.0+. Produces a summary list of any changesets skipped and why they were skipped. Valid values are `OFF`, `SUMMARY`, and `VERBOSE`. In Liquibase Pro, `SUMMARY` and `VERBOSE` provide additional information about failed deployments. Default: `SUMMARY`. Note: Liquibase may display one or multiple reasons for halting deployment of a changeset. If Liquibase cannot resolve a halting reason, it does not evaluate the changeset for other possible halting reasons.	Optional
`JAVA_OPTS=-Dliquibase.command.showSummaryOutput=<string>` `JAVA_OPTS=-Dliquibase.command.updateCount.showSummaryOutput=<string>`	Liquibase 4.24.0+. Summary output to report update summary results. Valid values are `LOG`, `CONSOLE`, and `ALL`. If set to `LOG`, the `--show-summary` output is sent to the file specified in `--log-file`. If set to `CONSOLE`, the `--show-summary` output is sent to `STDOUT`. If set to `ALL`, the `--show-summary` output is sent to both locations. Default: ALL.	Optional
`JAVA_OPTS=-Dliquibase.command.username=<string>` `JAVA_OPTS=-Dliquibase.command.updateCount.username=<string>`	Username to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional

Attribute	Definition	Requirement
`LIQUIBASE_COMMAND_CHANGELOG_FILE=<string>` `LIQUIBASE_COMMAND_UPDATE_COUNT_CHANGELOG_FILE=<string>`	The root changelog	Required
`LIQUIBASE_COMMAND_COUNT=<int>` `LIQUIBASE_COMMAND_UPDATE_COUNT_COUNT=<int>`	Integer specifying how many changes Liquibase applies the command to. Specify as `--count=myCount`. Positional format `<command> <count>` deprecated in 4.4+.	Required
`LIQUIBASE_COMMAND_URL=<string>` `LIQUIBASE_COMMAND_UPDATE_COUNT_URL=<string>`	The JDBC database connection URL. See Using JDBC URL in Liquibase.	Required
`LIQUIBASE_COMMAND_CHANGE_EXEC_LISTENER_CLASS=<string>` `LIQUIBASE_COMMAND_UPDATE_COUNT_CHANGE_EXEC_LISTENER_CLASS=<string>`	Fully-qualified class which specifies a `ChangeExecListener`. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`LIQUIBASE_COMMAND_CHANGE_EXEC_LISTENER_PROPERTIES_FILE=<string>` `LIQUIBASE_COMMAND_UPDATE_COUNT_CHANGE_EXEC_LISTENER_PROPERTIES_FILE=<string>`	Path to a properties file for the `ChangeExecListener` class. For more information, see Implementing a Custom ChangeExecListener Class with Liquibase and ChangeExecListenerCommandStep.	Optional
`LIQUIBASE_COMMAND_CONTEXT_FILTER=<string>` `LIQUIBASE_COMMAND_UPDATE_COUNT_CONTEXT_FILTER=<string>`	Specifies the changeset contexts to match. Contexts are tags you can add to changesets to control which changesets are executed in any particular migration run. Note: If you use Liquibase 4.23.0 or earlier, use the syntax `--contexts` instead of `--context-filter`.	Optional
`LIQUIBASE_COMMAND_DEFAULT_CATALOG_NAME=<string>` `LIQUIBASE_COMMAND_UPDATE_COUNT_DEFAULT_CATALOG_NAME=<string>`	Name of the default catalog to use for the database connection	Optional
`LIQUIBASE_COMMAND_DEFAULT_SCHEMA_NAME=<string>` `LIQUIBASE_COMMAND_UPDATE_COUNT_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_DRIVER=<string>` `LIQUIBASE_COMMAND_UPDATE_COUNT_DRIVER=<string>`	The JDBC driver class	Optional
`LIQUIBASE_COMMAND_DRIVER_PROPERTIES_FILE=<string>` `LIQUIBASE_COMMAND_UPDATE_COUNT_DRIVER_PROPERTIES_FILE=<string>`	The JDBC driver properties file	Optional
`LIQUIBASE_COMMAND_FORCE_ON_PARTIAL_CHANGES=<true\|false>` `LIQUIBASE_COMMAND_UPDATE_COUNT_FORCE_ON_PARTIAL_CHANGES=<true\|false>`	Liquibase Pro only. Use this argument only if you are specifying `--rollback-on-error=true` to automatically roll back `update` operations containing errors. `--force-on-partial-changes=true` specifies whether Liquibase rolls back partially invalid changesets, such as a changeset containing two changes: one with an error and one without an error. This ensures that you can successfully roll back all changes if a deployment has an error, even if the changeset contains multiple changes. Available in Liquibase 4.25.0+. Default: `false`. See also: `failOnError`.	Optional
`LIQUIBASE_COMMAND_LABEL_FILTER=<string>` `LIQUIBASE_COMMAND_UPDATE_COUNT_LABEL_FILTER=<string>`	Specifies the changeset labels to match. Labels are tags you can add to changesets to control which changesets will be executed in any migration run.	Optional
`LIQUIBASE_COMMAND_PASSWORD=<string>` `LIQUIBASE_COMMAND_UPDATE_COUNT_PASSWORD=<string>`	Password to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional
`LIQUIBASE_COMMAND_REPORT_ENABLED=<true\|false>` `LIQUIBASE_COMMAND_UPDATE_COUNT_REPORT_ENABLED=<true\|false>`	Enables a report at the command level. Overrides the global parameter `--reports-enabled`. Default: `true`.	Optional
`LIQUIBASE_COMMAND_REPORT_NAME=<string>` `LIQUIBASE_COMMAND_UPDATE_COUNT_REPORT_NAME=<string>`	Specifies the name of the report file at the command level. Overrides the global parameter `--reports-name`. By default, Liquibase generates a new report file labeled with a timestamp (user's local time). If you set a custom name, Liquibase overwrites the existing file every time you generate a new report. Default: `report-<DD-Mon-YYYY-HHmmss>.html`.	Optional
`LIQUIBASE_COMMAND_REPORT_PATH=<string>` `LIQUIBASE_COMMAND_UPDATE_COUNT_REPORT_PATH=<string>`	Specifies the file path to the report file at the command level. Overrides the global parameter `--reports-path`. Default: `./`.	Optional
`LIQUIBASE_COMMAND_REPORT_SUPPRESS_EXCEPTION=<true\|false>` `LIQUIBASE_COMMAND_UPDATE_COUNT_REPORT_SUPPRESS_EXCEPTION=<true\|false>`	Liquibase 4.31.0+. Specifies whether to hide exceptions (which may contain SQL) from the operation report at the command level. Overrides the global parameter `--reports-suppress-exception`. Default: `false`. However: If `--report-suppress-exception` is not set and `--report-suppress-sql=true`, Liquibase suppresses all SQL, including exception SQL. If `--report-suppress-exception=false` and `--report-suppress-sql=true`, Liquibase suppresses most SQL but shows exception SQL.	Optional
`LIQUIBASE_COMMAND_REPORT_SUPPRESS_SQL=<true\|false>` `LIQUIBASE_COMMAND_UPDATE_COUNT_REPORT_SUPPRESS_SQL=<true\|false>`	Liquibase 4.31.0+. Specifies whether to hide changeset SQL in operation reports at the command level. Overridden by the global parameter `--reports-suppress-sql`. Default: `false`.	Optional
`LIQUIBASE_COMMAND_ROLLBACK_ON_ERROR=<true\|false>` `LIQUIBASE_COMMAND_UPDATE_COUNT_ROLLBACK_ON_ERROR=<true\|false>`	Liquibase Pro only. If any changeset in a deployment fails, `--rollback-on-error` stops the `update` operation and rolls back all changesets you just deployed. Available in Liquibase 4.18.0+. Default: `false`. Note: A changeset marked `failOnError=false` does not trigger as an error, so `rollback-on-error` will not occur. Additionally, if a changeset is not auto-rollback compliant or does not have a rollback script, then `rollback-on-error` does not occur for any changeset. Read more: `failOnError`.	Optional
`LIQUIBASE_COMMAND_SHOW_SUMMARY=<string>` `LIQUIBASE_COMMAND_UPDATE_COUNT_SHOW_SUMMARY=<string>`	Liquibase 4.24.0+. Produces a summary list of any changesets skipped and why they were skipped. Valid values are `OFF`, `SUMMARY`, and `VERBOSE`. In Liquibase Pro, `SUMMARY` and `VERBOSE` provide additional information about failed deployments. Default: `SUMMARY`. Note: Liquibase may display one or multiple reasons for halting deployment of a changeset. If Liquibase cannot resolve a halting reason, it does not evaluate the changeset for other possible halting reasons.	Optional
`LIQUIBASE_COMMAND_SHOW_SUMMARY_OUTPUT=<string>` `LIQUIBASE_COMMAND_UPDATE_COUNT_SHOW_SUMMARY_OUTPUT=<string>`	Liquibase 4.24.0+. Summary output to report update summary results. Valid values are `LOG`, `CONSOLE`, and `ALL`. If set to `LOG`, the `--show-summary` output is sent to the file specified in `--log-file`. If set to `CONSOLE`, the `--show-summary` output is sent to `STDOUT`. If set to `ALL`, the `--show-summary` output is sent to both locations. Default: ALL.	Optional
`LIQUIBASE_COMMAND_USERNAME=<string>` `LIQUIBASE_COMMAND_UPDATE_COUNT_USERNAME=<string>`	Username to connect to the target database. Tip: It is a best practice to store sensitive data in a Secrets Management tool with Liquibase Pro.	Optional

* Liquibase will check nested changelogs for definitions of the changesets to update.

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.

Output

Liquibase Version: 4.9.1
Liquibase Community 4.9.1 by Liquibase

Liquibase command 'update-count' was executed successfully.