The history command lists all deployed changesets and their deploymentIds. The history command does not modify the database.


The history command is typically used when you want to inspect a particular group of changes to ensure that they have been applied to the database.

Running the history command

To run the history command, you can specify the driver, classpath, and URL in your liquibase.properties file. For more information, see Creating and configuring a liquibase.properties file. You can also specify these properties in your command line.

Then run the history command:

liquibase --outputFile=history.txt history

history global attributes

Attribute Definition Requirement
--url The JDBC database connection URL Required
--username The database username Required
--password The database password Required
--outputFile Specifies that the output should go to a file rather than to STDOUT Optional

Note: The username and password attributes are not required for connections and systems which use alternate means of authentication.


When successful, the history command produces the following output:

C:\dev\DaticalDB-testing\liquibase-pro-cli-project\oracle_lbpro_master>..\liquibase history
Liquibase Pro 3.8.7 by Datical licensed to Liquibase Pro Customer until Tue Nov 03 19:00:00 CST 2020
Liquibase History for jdbc:oracle:thin:@ - Database updated at 2/17/20 10:54 AM. Applied 3 changeSet(s) in 0.485s, DeploymentId: 1958497040
oracle_lbpro_master_changelog.xml::1::createTableforSynonym-PROSCHEMA::Liquibase Pro User
oracle_lbpro_master_changelog.xml::2::createTableForView-PROSCHEMA::Liquibase Pro User
oracle_lbpro_master_changelog.xml::3::createTableForCC-PROSCHEMA::Liquibase Pro User
Liquibase command 'history' was executed successfully.