Installation Troubleshooting

If you cannot run the liquibase --version command successfully, perform the following steps:

Verification #1: Check your PATH to Liquibase

To verify that you have correctly added the Liquibase folder to your PATH after the upgrade, type env in your Linux Terminal or Windows Command Prompt to display all available PATHs.

Verification #2: Check for Java installation

For Liquibase to run correctly, Java must be installed on your Linux, Unix, or macOS operating system. To verify that Java is installed on your computer:

  1. Open your Linux Terminal or Windows Command Prompt.
  2. In the command line window, type java -version.
  3. If you see the error message: "-bash: java: command not found", "'java' is not recognized as an internal or external command, operable program or batch file", or "java : The term 'java' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again", then you need to install Java or add the location of the Java executable to your PATH.

    To install Java on your computer:

    • Go to the Adoptium download site and install the needed version of Java.
    • Add the location of the Java executable to your PATH environment variable. You can find more information about adding Java to the PATH for Windows, Linux, Unix, or macOS on the Installing Liquibase page under the Manual installation section.

Verification #3: Run the Liquibase validate command

To verify that your existing project changelogs are compatible with your current projects, you can run the Liquibase validate command.

  1. Open your Linux Terminal or Windows Command Prompt.
  2. Run the following:
  3. liquibase validate

Troubleshooting

  • If the validate command produces an error on a specific changeset, examine your changelog carefully. There may be situations where you have fixed a bug, and now you need to check syntax issues.
  • If you are testing a new feature within an XML changelog, ensure that the header next to the XSD field has the current version of Liquibase. For example, if the upgrade is for Liquibase 4.3.1:
  • <databaseChangeLog
    	xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
    	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    	xmlns:ext="http://www.liquibase.org/xml/ns/dbchangelog-ext"
    	xmlns:pro="http://www.liquibase.org/xml/ns/pro"
    	xsi:schemaLocation="http://www.liquibase.org/xml/ns/dbchangelog
    		http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-latest.xsd
    		http://www.liquibase.org/xml/ns/dbchangelog-ext http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-ext.xsd
    		http://www.liquibase.org/xml/ns/pro http://www.liquibase.org/xml/ns/pro/liquibase-pro-latest.xsd">
    </databaseChangeLog>