Connect Liquibase to Oracle Database using Oracle Internet Directory

If you are connecting using an inline LDAP URL (for example, jdbc:oracle:thin:@ldap://your_oid_host:port/...), skip to Step 4: Configure Liquibase. Steps 1–3 are only required if you are connecting using a TNS alias.

All JARs are available from the Oracle JDBC Downloads page and Maven Central. Replace 21.13.0.0 with the latest 21.x release.

To connect using a TNS alias (Option A), you must also install Oracle Instant Client 23c. It provides the OCI native libraries (for example, ocijdbc23.dll on Windows) that the jdbc:oracle:oci driver requires. Earlier versions such as 19c will not work. The inline LDAP URL options (B and C) use the thin driver and do not need Instant Client.

Create an Oracle Net administration directory (for example, ~/tns-admin) and add ldap.ora to point to your OID server.

Be sure to:

• Replace your_admin_context with your LDAP admin context. For example, dc=company,dc=com, dc=myorg,dc=local

• Replace your_oid_host with your OID server hostname. For example, oid.company.com, ldap.myorg.local

• Replace your_ldap_port with your LDAP port. Usually, 389

• Replace your_ldap_ssl_port with your LDAP SSL port. Usually, 636

Create sqlnet.ora in the same directory to set LDAP as the primary name resolution method.

Create ojdbc.properties in the same directory as ojdbc11.jar (for example, lib/). The Oracle JDBC driver picks it up automatically from that location. This file tells the driver where to find ldap.ora and sqlnet.ora.

Be sure to:

• Replace your_tns_admin_dir with the absolute path to your TNS admin directory. For example, /home/user/tns-admin, /Users/name/tns-admin, C:/Users/name/tns-admin (Windows — use forward slashes)

Create liquibase.properties in your working directory. Option A is the standard enterprise setup. Liquibase resolves the TNS alias through OID at connect time using the Oracle OCI driver (which requires Oracle Instant Client 23c), so you never hard-code OID server details in your properties file. Options B and C use the thin driver, embed the OID server address directly in the URL, and do not require ldap.ora or sqlnet.ora. To use Oracle Wallet for credentials, see Using Oracle Wallet with Liquibase.

Be sure to:

• Replace your_tns_alias with the service name registered in OID. For example, MYSERVICE, ORCL

• Replace your_username with your database username

• Replace your_password with your database password

• Replace your_oid_host with your OID server hostname (Options B and C only). For example, oid.company.com

• Replace your_ldap_port with your LDAP port (Option B only). Usually, 389

• Replace your_ldap_ssl_port with your LDAPS port (Option C only). Usually, 636

• Replace dc=your_domain,dc=com with your LDAP admin context (Options B and C only). For example, dc=company,dc=com

If you are using Option A (TNS alias), set TNS_ADMIN to the directory containing your ldap.ora and sqlnet.ora files. Options B and C (inline LDAP URL) do not require this variable.

Your DBA or directory admin must create an LDAP entry in OID for each Oracle service that Liquibase should connect to. Create a file named service.ldif with the following content.

Be sure to:

• Replace MYSERVICE with your Oracle service name

• Replace dc=company,dc=com with your LDAP admin context

• Replace db.company.com with your Oracle DB hostname

For SSL (TCPS), replace the orclNetDescString with:

Load the LDIF file with ldapadd.

Be sure to:

• Replace oid.company.com with your OID server hostname

• Replace cn=orcladmin,dc=company,dc=com with your LDAP admin DN

• Replace your_admin_password with your LDAP admin password

Run Liquibase against your OID-configured database. The inline option at the end lets you run without a liquibase.properties file.

Be sure to:

• Replace your_oid_host with your OID server hostname (inline option only)

• Replace your_ldap_port with your LDAP port (inline option only). Usually, 389

• Replace your_tns_alias with your service name (inline option only)

• Replace your_admin_context with your LDAP admin context (inline option only). For example, dc=company,dc=com

• Replace your_username and your_password with your database credentials (inline option only)