Using Liquibase with Oracle ATP & ADW

Oracle Autonomous Database is an Oracle Cloud product with a set of services that deliver automated patching, upgrades, and tuning. It includes:

  • Autonomous Transaction Processing (ATP) – an Autonomous Database service that can instantly scale to meet demands of mission critical transaction processing and mixed workload applications.
  • Autonomous Data Warehouse (ADW) – a fully autonomous data warehousing environment that scales elastically, delivers fast query performance, and requires no database administration.

For more information, see the Oracle Cloud documentation page.

Supported versions

  • 19c – officially supported

Prerequisites

Install drivers

To use Liquibase and Oracle ATP or Oracle ADW, you need the JDBC driver JAR file:

Ensure you downloaded the Oracle JDBC driver JAR file (Maven download) to connect to the Oracle database. You can download ojdbc8.jar or ojdbc10.jar. The ojdbc10.jar file is certified with JDK10 and JDK11, and the ojdbc8.jar file is certified with JDK8, JDK9, and JDK11.

Note: It is best practice to use the Oracle Database 18c (or higher) drivers. Also, the following additional .jar files are required: oraclepki.jar, osdt_cert.jar, and osdt_core.jar. For more information, see Using Oracle Autonomous Database on Shared Exadata Infrastructure.

Place your JAR file(s) in the liquibase/lib directory. For more information, see Adding and Updating Liquibase Drivers.

If you use Maven, you also need to download the driver JAR file and configure your Maven pom.xml file to use the local copy of the driver. For example:

<dependency>
    <groupId>com.oracle.database.jdbc</groupId>
    <artifactId>ojdbc8</artifactId>
    <version>21.5.0.0</version>
</dependency>

Test your connection

Ensure that you have created:

Ensure that your Oracle ATP or ADW database is configured:

  1. Download the Wallet to connect to the database:
    1. Log into your Oracle Cloud account.
    2. Navigate to Autonomous Database and select DB Connection > Wallet Type > Download.
    3. Enter a secure password for the Wallet and download the ZIP file to save the client security credentials.
    4. Unzip the Wallet and place it somewhere safe in your file system to prevent unauthorized database access.
    5. Navigate to the Wallet folder and update the ojdbc.properties file with the following:
      • Comment out the oracle.net.wallet_location line.
      • Set javax.net.ssl.trustStorePassword to the Wallet password that you entered to download the Wallet.
      • Set javax.net.ssl.keyStorePassword to the Wallet password that you entered to download the Wallet.
      #oracle.net.wallet_location=(SOURCE=(METHOD=FILE)(METHOD_DATA=(DIRECTORY=${TNS_ADMIN})))
      javax.net.ssl.trustStore=${TNS_ADMIN}/truststore.jks
      javax.net.ssl.trustStorePassword=my_wallet_password
      javax.net.ssl.keyStore=${TNS_ADMIN}/keystore.jks
      javax.net.ssl.keyStorePassword=my_wallet_password
    6. In the Wallet folder, open the sqlnet.ora and ensure that SSL_SERVER_DN_MATCH=yes.
  2. Note: For alternative secure connection methods, see Connecting to Autonomous Database.

  3. Specify the database URL in the Liquibase properties file:
  4. url: jdbc:oracle:thin:@<database_name>_high?TNS_ADMIN=/path/to/Wallet_<database_name>

    Note: If you use Windows, ensure the TNS_ADMIN path to your wallet folder includes double slashes in the URL property.

    Example: url: jdbc:oracle:thin:@databaseName_high?TNS_ADMIN=path//to//Wallet_databaseName

    Tip: To apply a Liquibase Pro key to your project, add the following property to the Liquibase properties file: liquibaseProLicenseKey: <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 --username=test --password=test --changelog-file=<changelog.xml> status

    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 --changelog-file=<changelog.xml> update-sql
    liquibase --changelog-file=<changelog.xml> update
  6. From a database UI tool, ensure that your database contains the test_table you added along with the DATABASECHANGELOG table and DATABASECHANGELOGLOCK table.

Related links