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.

Note: For more information, see the Oracle Cloud documentation page.

Supported Versions

19c – officially supported

Prerequisites

Before using Liquibase and Oracle ATP or Oracle ADW, ensure you have completed the following:

Completed Liquibase Installation.
Created a Liquibase project folder to store all Liquibase files.
Created a new liquibase.properties file or are using the existing liquibase.properties file included in the installation package. For more information, see Creating and configuring a liquibase.properties file.

Driver Information

To use Liquibase and Oracle ATP or Oracle ADW, you need to have the JDBC jar file:

Ensure you downloaded the Oracle JDBC driver jar file 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.
Place the ojdbc<version>.jar file in the liquibase/lib directory.

Note: If you put the ojdbc<version>.jar file in any other directory, specify the path to it in the liquibase.properties file: classpath:../path_to_drivers/ojdbc<version>.jar. For more information, see Creating and configuring a liquibase.properties file.

If you use Maven, you also need to download the Oracle driver jar file and put the driver in a location that your Maven build can access. Configure the Maven pom.xml file to use the local copy of the driver jar file. For example:

<dependency>
<groupId>com.oracle.ojdbc</groupId>
<artifactId>ojdbc8</artifactId>
<version>19.3.0.0</version>
</dependency>

Testing Your Connection

For Liquibase and Oracle ATP or Oracle ADW to work, you need to:

Ensure that you created:

Oracle Autonomous Database with ATP or ADW via the Oracle Cloud Infrastructure Console.
An access control list while providing your IP address.

Download the Wallet to connect to the database:
1. Log into your Oracle Cloud account.
2. Navigate to the Autonomous Database details page and select DB Connection.
3. Select Wallet Type, and then select Download.
4. Enter a secure password for the Wallet and download the .zip file to save the client security credentials.
5. Unzip the Wallet and place it somewhere safe in your file system to prevent unauthorized database access.
6. 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
```
7. In the Wallet folder, open the sqlnet.ora and ensure that SSL_SERVER_DN_MATCH=yes.

Note: You can use other methods to securely connect to Autonomous Database. For more information, see Connecting to Autonomous Database.

Specify the database URL in your liquibase.properties file:

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 dashes in the URL property.

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

Create a text file called changelog (.xml, .sql, .json, or .yaml) in your project directory and add a changeset.

XML example

<?xml version="1.0" encoding="UTF-8"?>
<databaseChangeLog
         xmlns="http://www.liquibase.org/xml/ns/dbchangelog"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
		 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-4.3.xsd
		 http://www.liquibase.org/xml/ns/pro http://www.liquibase.org/xml/ns/pro/liquibase-pro-4.3.xsd">				
         <changeSet id="1" author="Liquibase">
         <createTable tableName="test_table">
               <column name="test_id" type="int">
               <constraints primaryKey="true"/>
               </column>
               <column name="test_column" type="varchar(20)"/>
        </createTable>
      </changeSet>
</databaseChangeLog>

SQL example

--liquibase formatted sql

--changeset liquibase:1
--Database: oracle
CREATE TABLE test_table (test_id INT, test_column VARCHAR(20), PRIMARY KEY (test_id))

YAML example

databaseChangeLog:
- changeSet:
	id: 1
	author: Liquibase
	changes:
	- createTable:
		columns:
		- column:
			name: test_column
			type: INT
			constraints:  
				   primaryKey:  true  
				   nullable:  false  
				   tableName: test_table

JSON example

{ 
  "databaseChangeLog": [
  {
	"changeSet": {
	  "id": "1",
      "author": "Liquibase",
	  "changes": [
	    {
		  "createTable": {
		    "columns": [
			{
			  "column": 
		      {
				"name": "test_column",
				"type": "INT",
				"constraints": 
			  {
				"primaryKey": true,
				"nullable": false
				}
				}
			  }]
			,
			"tableName": "test_table"
		  }
		}]
	  }
	}]
  }

Run the status command to see whether the connection is successful. Specify the name of the changelog you created in place of changelog.xml. Also, to run Liquibase commands, you need to specify your username and password in the liquibase.properties file or on the command line. However, the username and password attributes are not required for connections and systems which use alternate means of authentication.

liquibase --username=test --password=test --changeLogFile=changelog.xml status

Note: Alternatively, you can add the changeLogFile attribute to your liquibase.properties file.

Run your first update with the Liquibase update command, which will make changes to your database. You can also run the updateSQL command if you want to inspect the SQL before running the update command.

liquibase --changeLogFile=changelog.xml updateSQL
liquibase --changeLogFile=changelog.xml update

After your first update, you will see a new table along with the DATABASECHANGELOG and DATABASECHANGELOGLOCK tables added to the database:

DATABASECHANGELOG table. This table keeps a record of all the changesets that were deployed. When you deploy, the changesets in the changelog are compared with the DATABASECHANGELOG tracking table, and only the new changesets that were not found in the DATABASECHANGELOG will be deployed.
DATABASECHANGELOGLOCK table. This table is used internally by Liquibase to manage access to the DATABASECHANGELOG table during deployment and ensure only one instance of Liquibase is updating the database at a time, whether that is creating, updating or deleting changes.

Supported Commands and Change Types