Autonomous Data Warehouse is preconfigured to support Oracle Net Services (a TNS listener is installed and configured to use secure TCPS and client credentials).
The client computer must be prepared to use Oracle Net Services to connect to Autonomous Data Warehouse.
About Connecting to Autonomous Data Warehouse Using a Client Application
Applications can connect to the Autonomous Data Warehouse using any of the connection types supported by Oracle Net Services.
Consult your application documentation for details about how your application connects to Oracle. The following steps describe the process of connecting to the Autonomous Data Warehouse using a client application:
Determine what connection type your application uses, (for example OCI, ODBC, JDBC Thin, and so on).
Prepare your client computer for the type of connection used by your application. See the following sections.
Within your application, set up the connection.
Autonomous Data Warehouse is preconfigured to support Oracle Net Services (a TNS listener is installed and configured to use secure TCPS and client credentials.) The client computer must be prepared to use Oracle Net Services to connect to Autonomous Data Warehouse.
The steps required to prepare the client computer depend on the type of connection used by the client application. In all cases, client credentials in the form of the wallet file must be downloaded to the client.
Prepare for Oracle Call Interface (OCI), ODBC, and JDBC OCI Connections
Preparing for any type of Oracle Call Interface(OCI) connection requires the installation of client software, downloading client credentials, and configuring certain files and environment variables.
New Oracle Client Installation
The following steps assume Oracle client software has not already been installed on the client computer. If Oracle client software has already been installed and there are working copies of
tnsnames.ora, see Updating an Existing Oracle Client Installation.
Before making an Oracle Call Interface(OCI), ODBC, or JDBC OCI connection, do the following:
Install Oracle Client software version 184.108.40.206 (or higher) on your computer. Either the full Oracle Client or the Oracle Instant Client may be used. The Instant Client contains the minimal software needed to make an Oracle Call Interface connection. The Instant Client is sufficient for most applications.
Download client credentials and store the file in a secure folder on your computer. See Download Client Credentials (Wallets).
Unzip/uncompress the credentials file into a secure folder on your computer.
sqlnet.orafile in the folder where you unzip the credentials file, replacing
“?/network/admin”with the name of the folder containing the client credentials.
For example, edit
WALLET_LOCATION = (SOURCE = (METHOD = file) (METHOD_DATA = (DIRECTORY="?/network/admin"))) SSL_SERVER_DN_MATCH=yes
WALLET_LOCATION = (SOURCE = (METHOD = file) (METHOD_DATA = (DIRECTORY="/home/adwc_credentials"))) SSL_SERVER_DN_MATCH=yes
TNS_ADMINenvironment variable and set it to the location of the credentials file.
Note:Use this environment variable to change the directory path of Oracle Net Services configuration files from the default location of
ORACLE_HOME\network\adminto the location of the secure folder containing the credentials file you saved in Step 2. Set the
TNS_ADMINenvironment variable to the directory where the unzipped credentials files are, not to the credentials file itself.
Connections with an HTTP Proxy
If the client is behind a firewall and your network configuration requires an HTTP proxy to connect to the internet, then perform the following steps to update the
Note:Connections through an HTTP proxy are only available with Oracle Client software version 220.127.116.11 or later.
Add the following line to the
sqlnet.orafile to enable connections through an HTTP proxy:
Add the HTTP proxy hostname and port to the connection definitions in
tnsnames.ora. You need to add the
https_proxy_portparameters in the address section of connection definitions. For example, the following sets the HTTP proxy to
proxyhostnameand the HTTP proxy port to
80; replace these values with your HTTP proxy information:
ADWC1_high = (description= (address= (https_proxy=proxyhostname)(https_proxy_port=80)(protocol=tcps)(port=1522)(host=adwc.example.oraclecloud.com) ) (connect_data=(service_name=adwc1_high.adwc.oraclecloud.com) ) (security=(ssl_server_cert_dn="adwc.example.oraclecloud.com,OU=Oracle BMCS US,O=Oracle Corporation,L=Redwood City,ST=California,C=US") ) )
tnsnames.orafor the HTTP proxy may not be enough depending on your organization's network configuration and security policies. For example, some networks require a
passwordfor the HTTP proxy. In such cases contact your network administrator to open outbound connections to hosts in the oraclecloud.com domain using port 1522 without going through an HTTP proxy.
For more information on
SQLNET.USE_HTTPS_PROXY, see Net Services Reference.
For information on
HTTPS_PROXY_PORT, see Net Services Reference.
Updating an Existing Oracle Client Installation
If you have an existing Oracle Client installation, you already have
tnsnames.ora files and the
TNS_ADMIN environment variable. In this case, do the following:
sqlnet.orafile by adding the following:
WALLET_LOCATION = (SOURCE = (METHOD = file) (METHOD_DATA = (DIRECTORY="/home/adwc_credentials")))
Copy the entries in the
tnsnames.orafile provided in the Autonomous Data Warehouse wallet to your existing
Prepare for JDBC Thin Connections
Applications that use JDBC Thin connections include the software necessary to make an Oracle Net Services connection. It is not necessary to download and install Oracle Client software.
The JDK uses the Java Cryptography Extension (JCE) Jurisdiction Policy files to configure cryptographic algorithm restrictions. Connections to the Autonomous Data Warehouse require that you use the unlimited cryptographic policy. Java 9 and versions of JDK version 8, 8u161 and later, provide this support by default.
Oracle recommends using the Java Development Kit (JDK) version 8, 8u161, or later (including Java 9). These JDK versions use the Java Cryptography Extension (JCE) Jurisdiction Policy files, which are required for connections to Autonomous Data Warehouse.
Some applications use the JDK installed on your computer while others use a JDK that is embedded in the application installation. If your application uses the JDK installed on your computer and that JDK is version 8, 8u161 or later, no additional preparation is required. If your computer does not have JDK version 8, 8u161 or later, already installed then install the latest JDK first. You can download JDK version 8 from https://www.java.com/.
If your application is using a JDK version 8, prior to 8u161, then the JCE Policy Files must be updated within your application.
Note:For users running 64-bit Windows, SQL Developer 17.4.1 (or later) the software offers the choice of an embedded JDK version 8 (that is, JDK version 8 is installed with SQL Developer). The Java Cryptography Extension Unlimited Strength Jurisdiction Policy files are included in the embedded JDK installation with SQL Developer 17.4.1 (or later).