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


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

Driver Information

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

  1. 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.
  2. 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.

  3. 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 file: classpath:../path_to_drivers/ojdbc<version>.jar. For more information, see Creating and configuring a 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:


Testing Your Connection

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

  1. Ensure that you created:
  1. 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 file with the following:
      • Comment out the line.
      • Set to the Wallet password that you entered to download the Wallet.
      • Set to the Wallet password that you entered to download the Wallet.${TNS_ADMIN})))${TNS_ADMIN}/truststore.jks${TNS_ADMIN}/keystore.jks
    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.

  1. Specify the database URL in your file:
  2. 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

  1. Create a text file called Working with Changelogs (.xml, .sql, .json, or .yaml) in your project directory and add a Changelog Formats .

  1. 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 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.
  2. liquibase --username=test --password=test --changeLogFile=changelog.xml status

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

  1. 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.
  2. liquibase --changeLogFile=changelog.xml updateSQL
    liquibase --changeLogFile=changelog.xml update

After your first update, your database will contain the table you added along with the DATABASECHANGELOG and DATABASECHANGELOGLOCK tables:

  • 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

Change Type Supported Command Supported
addAutoIncrement Not Supported calculateCheckSum Supported
addCheckConstraint Supported changelogSync Supported
addColumn Supported changelogSyncSQL Supported
addDefaultValue Supported changelogSyncToTag Supported
addForeignKeyConstraint Supported changelogSyncToTagSQL Supported
addLookupTable Supported clearCheckSums Supported
addNotNullConstraint Supported dbDoc Supported
addPrimaryKey Supported deactivateChangeLog Supported
addUniqueConstraint Supported diff Supported
alterSequence Supported diff JSON Supported
createFunction Supported diffChangeLog Supported
createIndex Supported dropAll Supported
createPackage Supported futureRollbackCountSQL Supported
createPackageBody Supported future-rollback-from-tag-sql Supported
createProcedure Supported futureRollbackSQL Supported
createSequence Supported generateChangeLog Supported
createSynonym Supported help Supported
createTable Supported history Supported
createTrigger Supported listLocks Supported
createView Supported markNextChangeSetRan Supported
customChange Supported markNextChangeSetRanSQL Supported
delete Supported registerChangeLog Supported
disableCheckConstraint Supported releaseLocks Supported
disableTrigger Supported rollback Supported
dropAllForeignKeyConstraints Supported rollbackCount Supported
dropCheckConstraint Supported rollbackCountSQL Supported
dropColumn Supported rollbackOneChangeSet Supported
dropDefaultValue Supported rollbackOneChangeSetSQL Supported
dropForeignKeyConstraint Supported rollbackOneUpdate Supported
dropFunction Supported rollbackOneUpdateSQL Supported
dropIndex Supported rollbackSQL Supported
dropNotNullConstraint Supported rollbackToDate Supported
dropPackage Supported rollbackToDateSQL Supported
dropPackageBody Supported snapshot Supported
dropPrimaryKey Supported snapshotReference Supported
dropProcedure Supported status --verbose Supported
dropSequence Supported syncHub Supported
dropSynonym Supported tag command Supported
dropTable Supported tagExists Supported
dropTrigger Supported unexpectedChangeSets Supported
dropUniqueConstraint Supported update Supported
dropView Supported updateSQL Supported
empty Supported updateCount Supported
enableCheckConstraint Supported updateCountSQL Supported
enableTrigger Supported updateTestingRollback Supported
executeCommand Supported updateToTag Supported
insert Supported updateToTagSQL Supported
loadData Supported validate Supported
loadUpdateData Supported    
markUnused Supported    
mergeColumns Supported    
modifyDataType Supported    
output Supported    
renameColumn Supported    
renameSequence Supported    
renameTable Supported    
renameTrigger Supported    
renameView Supported    
setColumnRemarks Supported    
setTableRemarks Supported    
sql Supported    
sqlFile Supported    
stop Supported    
tagDatabase Supported    
update Supported    

Related Links