• Reference
  • Version · 6.0
  • Change Automation Reference

mark-next-changeset-ran-sql

Last updated: September 29, 2026

The mark-next-changeset-ran-sql command is a helper command that inspects the SQL Liquibase will run while using the mark-next-changeset-ran command.

Uses

The mark-next-changeset-ran-sql command is used to inspect the raw SQL before running the mark-next-changeset-ran command, so you can correct any issues that may arise before running the command. Liquibase uses the raw SQL to mark the next changeset you apply as executed in your database and to keep that changeset in the changelog as a record assuming that it has already been deployed.

Syntax

To run the mark-next-changeset-ran-sql command, specify the driver, classpath, and URL in the Liquibase properties file. You can also specify these properties in your command line.

Then run the mark-next-changeset-ran-sql command:

liquibase mark-next-changeset-ran-sql --changelog-file=example-changelog.xml

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

Attribute

Definition

Requirement

--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

Attribute

Definition

Requirement

--changelog-file=<string>

The root changelog

Required

--url=<string>

The JDBC database connection URL.

Required

--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

--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

--conditions-filter=<string>

Specifies the changeset conditions to match. conditions is a tag you can add to changesets to control which changesets will be executed in any migration run. Matching is a straight string comparison. Prefix the value with the @ operator to match strictly, so that only changesets with the exact value match. Available in Liquibase Secure 6.0 and later.

Optional

--keywords-filter=<string>

Specifies the changeset keywords to match. keywords is a tag you can add to changesets to control which changesets will be executed in any migration run. Matching is a straight string comparison. Prefix the value with the @ operator to match strictly, so that only changesets with the exact value match. Available in Liquibase Secure 6.0 and later.

Optional

--releases-filter=<string>

Specifies the changeset releases to match. releases is a tag you can add to changesets to control which changesets will be executed in any migration run. Matching is a straight string comparison. Prefix the value with the @ operator to match strictly, so that only changesets with the exact value match. Available in Liquibase Secure 6.0 and later.

Optional

--teams-filter=<string>

Specifies the changeset teams to match. teams is a tag you can add to changesets to control which changesets will be executed in any migration run. Matching is a straight string comparison. Prefix the value with the @ operator to match strictly, so that only changesets with the exact value match. Available in Liquibase Secure 6.0 and later.

Optional

--password=<string>

Password to connect to the target database.

Optional

--username=<string>

Username to connect to the target database.

Optional

Global parameters

Attribute

Definition

Requirement

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

Attribute

Definition

Requirement

cmdArgs: { changelog-file: "<string>" }

The root changelog

Required

cmdArgs: { url: "<string>" }

The JDBC database connection URL.

Required

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: { 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: { conditions-filter: "<string>" }

Specifies the changeset conditions to match. conditions is a tag you can add to changesets to control which changesets will be executed in any migration run. Matching is a straight string comparison. Prefix the value with the @ operator to match strictly, so that only changesets with the exact value match. Available in Liquibase Secure 6.0 and later.

Optional

cmdArgs: { keywords-filter: "<string>" }

Specifies the changeset keywords to match. keywords is a tag you can add to changesets to control which changesets will be executed in any migration run. Matching is a straight string comparison. Prefix the value with the @ operator to match strictly, so that only changesets with the exact value match. Available in Liquibase Secure 6.0 and later.

Optional

cmdArgs: { releases-filter: "<string>" }

Specifies the changeset releases to match. releases is a tag you can add to changesets to control which changesets will be executed in any migration run. Matching is a straight string comparison. Prefix the value with the @ operator to match strictly, so that only changesets with the exact value match. Available in Liquibase Secure 6.0 and later.

Optional

cmdArgs: { teams-filter: "<string>" }

Specifies the changeset teams to match. teams is a tag you can add to changesets to control which changesets will be executed in any migration run. Matching is a straight string comparison. Prefix the value with the @ operator to match strictly, so that only changesets with the exact value match. Available in Liquibase Secure 6.0 and later.

Optional

cmdArgs: { password: "<string>" }

Password to connect to the target database.

Optional

cmdArgs: { username: "<string>" }

Username to connect to the target database.

Optional

Global parameters

Attribute

Definition

Requirement

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

Attribute

Definition

Requirement

liquibase.command.changelogFile: <string>

liquibase.command.markNextChangesetRanSql.changelogFile: <string>

The root changelog

Required

liquibase.command.url: <string>

liquibase.command.markNextChangesetRanSql.url: <string>

The JDBC database connection URL.

Required

liquibase.command.contextFilter: <string>

liquibase.command.markNextChangesetRanSql.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.markNextChangesetRanSql.defaultCatalogName: <string>

Name of the default catalog to use for the database connection

Optional

liquibase.command.defaultSchemaName: <string>

liquibase.command.markNextChangesetRanSql.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.markNextChangesetRanSql.driver: <string>

The JDBC driver class

Optional

liquibase.command.driverPropertiesFile: <string>

liquibase.command.markNextChangesetRanSql.driverPropertiesFile: <string>

The JDBC driver properties file

Optional

liquibase.command.labelFilter: <string>

liquibase.command.markNextChangesetRanSql.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.conditionsFilter: <string>

liquibase.command.markNextChangesetRanSql.conditionsFilter: <string>

Specifies the changeset conditions to match. conditions is a tag you can add to changesets to control which changesets will be executed in any migration run. Matching is a straight string comparison. Prefix the value with the @ operator to match strictly, so that only changesets with the exact value match. Available in Liquibase Secure 6.0 and later.

Optional

liquibase.command.keywordsFilter: <string>

liquibase.command.markNextChangesetRanSql.keywordsFilter: <string>

Specifies the changeset keywords to match. keywords is a tag you can add to changesets to control which changesets will be executed in any migration run. Matching is a straight string comparison. Prefix the value with the @ operator to match strictly, so that only changesets with the exact value match. Available in Liquibase Secure 6.0 and later.

Optional

liquibase.command.releasesFilter: <string>

liquibase.command.markNextChangesetRanSql.releasesFilter: <string>

Specifies the changeset releases to match. releases is a tag you can add to changesets to control which changesets will be executed in any migration run. Matching is a straight string comparison. Prefix the value with the @ operator to match strictly, so that only changesets with the exact value match. Available in Liquibase Secure 6.0 and later.

Optional

liquibase.command.teamsFilter: <string>

liquibase.command.markNextChangesetRanSql.teamsFilter: <string>

Specifies the changeset teams to match. teams is a tag you can add to changesets to control which changesets will be executed in any migration run. Matching is a straight string comparison. Prefix the value with the @ operator to match strictly, so that only changesets with the exact value match. Available in Liquibase Secure 6.0 and later.

Optional

liquibase.command.password: <string>

liquibase.command.markNextChangesetRanSql.password: <string>

Password to connect to the target database.

Optional

liquibase.command.username: <string>

liquibase.command.markNextChangesetRanSql.username: <string>

Username to connect to the target database.

Optional

Global parameters

Attribute

Definition

Requirement

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

Attribute

Definition

Requirement

JAVA_OPTS=-Dliquibase.command.changelogFile=<string>

JAVA_OPTS=-Dliquibase.command.markNextChangesetRanSql.changelogFile=<string>

The root changelog

Required

JAVA_OPTS=-Dliquibase.command.url=<string>

JAVA_OPTS=-Dliquibase.command.markNextChangesetRanSql.url=<string>

The JDBC database connection URL.

Required

JAVA_OPTS=-Dliquibase.command.contextFilter=<string>

JAVA_OPTS=-Dliquibase.command.markNextChangesetRanSql.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.markNextChangesetRanSql.defaultCatalogName=<string>

Name of the default catalog to use for the database connection

Optional

JAVA_OPTS=-Dliquibase.command.defaultSchemaName=<string>

JAVA_OPTS=-Dliquibase.command.markNextChangesetRanSql.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.markNextChangesetRanSql.driver=<string>

The JDBC driver class

Optional

JAVA_OPTS=-Dliquibase.command.driverPropertiesFile=<string>

JAVA_OPTS=-Dliquibase.command.markNextChangesetRanSql.driverPropertiesFile=<string>

The JDBC driver properties file

Optional

JAVA_OPTS=-Dliquibase.command.labelFilter=<string>

JAVA_OPTS=-Dliquibase.command.markNextChangesetRanSql.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.conditionsFilter=<string>

JAVA_OPTS=-Dliquibase.command.markNextChangesetRanSql.conditionsFilter=<string>

Specifies the changeset conditions to match. conditions is a tag you can add to changesets to control which changesets will be executed in any migration run. Matching is a straight string comparison. Prefix the value with the @ operator to match strictly, so that only changesets with the exact value match. Available in Liquibase Secure 6.0 and later.

Optional

JAVA_OPTS=-Dliquibase.command.keywordsFilter=<string>

JAVA_OPTS=-Dliquibase.command.markNextChangesetRanSql.keywordsFilter=<string>

Specifies the changeset keywords to match. keywords is a tag you can add to changesets to control which changesets will be executed in any migration run. Matching is a straight string comparison. Prefix the value with the @ operator to match strictly, so that only changesets with the exact value match. Available in Liquibase Secure 6.0 and later.

Optional

JAVA_OPTS=-Dliquibase.command.releasesFilter=<string>

JAVA_OPTS=-Dliquibase.command.markNextChangesetRanSql.releasesFilter=<string>

Specifies the changeset releases to match. releases is a tag you can add to changesets to control which changesets will be executed in any migration run. Matching is a straight string comparison. Prefix the value with the @ operator to match strictly, so that only changesets with the exact value match. Available in Liquibase Secure 6.0 and later.

Optional

JAVA_OPTS=-Dliquibase.command.teamsFilter=<string>

JAVA_OPTS=-Dliquibase.command.markNextChangesetRanSql.teamsFilter=<string>

Specifies the changeset teams to match. teams is a tag you can add to changesets to control which changesets will be executed in any migration run. Matching is a straight string comparison. Prefix the value with the @ operator to match strictly, so that only changesets with the exact value match. Available in Liquibase Secure 6.0 and later.

Optional

JAVA_OPTS=-Dliquibase.command.password=<string>

JAVA_OPTS=-Dliquibase.command.markNextChangesetRanSql.password=<string>

Password to connect to the target database.

Optional

JAVA_OPTS=-Dliquibase.command.username=<string>

JAVA_OPTS=-Dliquibase.command.markNextChangesetRanSql.username=<string>

Username to connect to the target database.

Optional

Global parameters

Attribute

Definition

Requirement

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

Attribute

Definition

Requirement

LIQUIBASE_COMMAND_CHANGELOG_FILE=<string>

LIQUIBASE_COMMAND_MARK_NEXT_CHANGESET_RAN_SQL_CHANGELOG_FILE=<string>

The root changelog

Required

LIQUIBASE_COMMAND_URL=<string>

LIQUIBASE_COMMAND_MARK_NEXT_CHANGESET_RAN_SQL_URL=<string>

The JDBC database connection URL.

Required

LIQUIBASE_COMMAND_CONTEXT_FILTER=<string>

LIQUIBASE_COMMAND_MARK_NEXT_CHANGESET_RAN_SQL_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_MARK_NEXT_CHANGESET_RAN_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_MARK_NEXT_CHANGESET_RAN_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_DRIVER=<string>

LIQUIBASE_COMMAND_MARK_NEXT_CHANGESET_RAN_SQL_DRIVER=<string>

The JDBC driver class

Optional

LIQUIBASE_COMMAND_DRIVER_PROPERTIES_FILE=<string>

LIQUIBASE_COMMAND_MARK_NEXT_CHANGESET_RAN_SQL_DRIVER_PROPERTIES_FILE=<string>

The JDBC driver properties file

Optional

LIQUIBASE_COMMAND_LABEL_FILTER=<string>

LIQUIBASE_COMMAND_MARK_NEXT_CHANGESET_RAN_SQL_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_CONDITIONS_FILTER=<string>

LIQUIBASE_COMMAND_MARK_NEXT_CHANGESET_RAN_SQL_CONDITIONS_FILTER=<string>

Specifies the changeset conditions to match. conditions is a tag you can add to changesets to control which changesets will be executed in any migration run. Matching is a straight string comparison. Prefix the value with the @ operator to match strictly, so that only changesets with the exact value match. Available in Liquibase Secure 6.0 and later.

Optional

LIQUIBASE_COMMAND_KEYWORDS_FILTER=<string>

LIQUIBASE_COMMAND_MARK_NEXT_CHANGESET_RAN_SQL_KEYWORDS_FILTER=<string>

Specifies the changeset keywords to match. keywords is a tag you can add to changesets to control which changesets will be executed in any migration run. Matching is a straight string comparison. Prefix the value with the @ operator to match strictly, so that only changesets with the exact value match. Available in Liquibase Secure 6.0 and later.

Optional

LIQUIBASE_COMMAND_RELEASES_FILTER=<string>

LIQUIBASE_COMMAND_MARK_NEXT_CHANGESET_RAN_SQL_RELEASES_FILTER=<string>

Specifies the changeset releases to match. releases is a tag you can add to changesets to control which changesets will be executed in any migration run. Matching is a straight string comparison. Prefix the value with the @ operator to match strictly, so that only changesets with the exact value match. Available in Liquibase Secure 6.0 and later.

Optional

LIQUIBASE_COMMAND_TEAMS_FILTER=<string>

LIQUIBASE_COMMAND_MARK_NEXT_CHANGESET_RAN_SQL_TEAMS_FILTER=<string>

Specifies the changeset teams to match. teams is a tag you can add to changesets to control which changesets will be executed in any migration run. Matching is a straight string comparison. Prefix the value with the @ operator to match strictly, so that only changesets with the exact value match. Available in Liquibase Secure 6.0 and later.

Optional

LIQUIBASE_COMMAND_PASSWORD=<string>

LIQUIBASE_COMMAND_MARK_NEXT_CHANGESET_RAN_SQL_PASSWORD=<string>

Password to connect to the target database.

Optional

LIQUIBASE_COMMAND_USERNAME=<string>

LIQUIBASE_COMMAND_MARK_NEXT_CHANGESET_RAN_SQL_USERNAME=<string>

Username to connect to the target database.

Optional

Output

Liquibase Community 4.9.1 by Liquibase -- ********************************************************************* -- SQL to add all changesets to database history table -- ********************************************************************* -- Change Log: example-changelog.sql -- Ran at: 5/6/22, 9:44 AM -- 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; -- Release Database Lock UPDATE PUBLIC.DATABASECHANGELOGLOCK SET LOCKED = FALSE, LOCKEDBY = NULL, LOCKGRANTED = NULL WHERE ID = 1; Liquibase command 'mark-next-changeset-ran-sql' was executed successfully.

PreviousMark-next-changeset-ranNextSet-contexts