Using Liquibase with Informix

IBM Informix is an embeddable relational database management system that specializes in online transaction processing and data warehouse workflows. For more information, see IBM Informix Servers Documentation.

Supported versions

  • 12.10.X


Install drivers

To use Liquibase and Informix, you need the JDBC driver JAR file (Maven download).

Place your JAR file(s) in the liquibase/lib directory. Read more: Adding and Updating Liquibase Drivers.

If you use Maven, you must include the driver JAR as a dependency in your pom.xml file. Read more: Configuring Liquibase Attributes in your Maven POM File.


Test your connection

  1. Ensure your Informix database is configured. Create an Informix database in the ANSI mode to enable implicit transactions by using the following statement:

    For more information, see Informix Installation and CREATE DATABASE statement: Logging Options.

  3. Specify the database URL in the Liquibase properties file. Liquibase does not parse the URL. You can either specify the full database connection string or specify the URL using your database's standard JDBC format:
  4. url: jdbc:informix-sqli://localhost:9088/dbname:INFORMIXSERVER=dbserver

    Tip: To apply a Liquibase Pro key to your project, add the following property to the Liquibase properties file: licenseKey: <paste code here>

  1. Create a text file called changelog (.xml, .sql, .json, or .yaml) in your project directory and add a changeset.
  2. Navigate to your project folder in the CLI and run the Liquibase status command to see whether the connection is successful:
  3. liquibase status --username=test --password=test --changelog-file=<changelog.xml>

    Note: You can pass arguments in the CLI or keep them in the Liquibase properties file.

  4. Inspect the SQL with the update-sql command. Then make changes to your database with the update command.
  5. liquibase update-sql --changelog-file=<changelog.xml>
    liquibase update --changelog-file=<changelog.xml>
  6. From a database UI tool, ensure that your database contains the test_table you added along with the DATABASECHANGELOG table and DATABASECHANGELOGLOCK table.

If you add a changeset with the procedure but receive an error message during the runtime, add the splitStatements attribute set to false to your changeset as follows:

--changeset bob:5 splitStatements:false
CREATE PROCEDURE raise_prices ( per_cent INT)
        UPDATE stock SET unit_price = unit_price + (unit_price * (per_cent/100) );