unexpectedChangeSets command

The unexpectedChangeSets command produces a list of changesets that were run in the database but do not exist in the current changelog.

Uses

The unexpectedChangeSets command is typically used to detect and compare the changes between the DATABASECHANGELOG table and the current changelog. If any of the changesets in the DATABASECHANGELOG table do not exist in the current changelog, the unexpectedChangeSets command detects those changesets and produces them in your output.

The unexpectedChangeSets command also produces all the deleted changesets that were previously deployed from the current changelog.

The image below shows the changelog that is already applied to the database — changelog_release1. If you want to apply a new changelog_release2 and it requires information about the previous changesets applied against the database, the unexpectedChangeSets command will list those changesets from changelog_release1 and changelog_release2.

By running the unexpectedChangeSets command, you can review any changesets in the DATABASECHANGELOG table applied from any other changelogs outside the scope of your current changelog.

Running the unexpectedChangeSets command

To run the unexpectedChangeSets command, you need to specify your driver, class path, URL, and user authentication information 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 unexpectedChangeSets command:

liquibase unexpectedChangeSets

To see the list of all changes applied, add the --verbose flag while running the command:

liquibase unexpectedChangeSets --verbose

unexpectedChangeSets global attributes

Attribute Definition Requirement

--changeLogFile

The root changelog

Required

--url

The JDBC database connection URL

Required

--username

The database username

Required

--password

The database password

Required

When running the unexpectedChangeSets command with the --verbose flag, the output can be as follows:

Liquibase Pro 3.9.0 by Datical licensed to Liquibase Pro Customer until Tue Sep 22 19:00:00 CDT 2020
20 unexpected changes were found in HR_DEV@jdbc:oracle:thin:@support.datical.net:1521:ORCL
../changelog.oracle.sql::1585673761195-1::support.liquibase.net
../changelog.oracle.sql::1585673761195-2::support.liquibase.net
../changelog.oracle.sql::1585673761195-3::support.liquibase.net
../changelog.oracle.sql::1585673761195-4::support.liquibase.net
../changelog.oracle.sql::1585673761195-5::support.liquibase.net
../changelog.oracle.sql::1585673761195-6::support.liquibase.net
../changelog.oracle.sql::1585673761195-8::support.liquibase.net
../changelog.oracle.sql::1585673761195-9::support.liquibase.net
changelog.oracle.sql::158768::SteveZ
changelog.oracle.sql::1587uye::SteveZ
changelog.xml::63f54::SteveZ
changelog.xml::63f434::SteveZ
changelog.xml::63634::SteveZ
changelog.oracle.sql::createTable113::Jack
changelog.oracle.sql::createProc_add_job_history112::Joe
changelog.oracle.sql::createView_EMP_DETAILS_VIEW112::John
changeLogWithRunAlways.xml::159120::SteveZ
samplefile.sql::raw::includeAll
samplefile.sql::1588246573379-865::rajeshmishra
samplefile.sql::1::your.name
Liquibase command 'unexpectedChangeSets' was executed successfully.

When running the unexpectedChangeSets command without indicating the --verbose flag, you receive the following output:

Liquibase Pro 3.9.0 by Datical licensed to Liquibase Pro Customer until Tue Sep 22 19:00:00 CDT 2020
20 unexpected changes were found in HR_DEV@jdbc:oracle:thin:@support.datical.net:1521:ORCL
Liquibase command 'unexpectedChangeSets' was executed successfully.