2 Database Client Configuration Files

Learn about database client configuration files for on-premises database and Oracle Autonomous Database (ADB).

In order to use Oracle Client for Microsoft Tools, an on-premises Oracle Database or ADB must already be provisioned. Connecting to Oracle databases on-premises and through ADB are similar, but there are some variations in the steps needed.

2.1 Setting Up On-Premises Databases

Locate the client configuration files and place them into a specified location on your machine.

To connect to an on-premises database:

  1. Locate the configuration files required for your database server setup.
    • Typically, ODP.NET requires tnsnames.ora and sqlnet.ora to be accessible to connect to the database server. These files can be copied from another Oracle database client that connects to the target database server.
    • Alternatively, an Easy Connect or Easy Connect Plus string can be used in lieu of credential files for on-premises databases. If you use Easy Connect (Plus), you can skip the credential file downloading and setup steps.
    For example, the Power BI Desktop Server configuration setting accepts an Easy Connect string with the following format:
    <DB hostname>:<Port>/<Service Name>
  2. Place the client configuration files on your Windows machine into a directory, and note the directory location.
    If your on-premises database requires a wallet or additional configuration, be sure to update your tnsnames.ora, sqlnet.ora, or other configuration files accordingly.
The credentials are now available, and you can continue with the configuration of your specific Microsoft tool.

2.2 Setting Up Oracle Autonomous Database

Download your database credentials and unzip the content onto your client machine.

In order to use Oracle Client for Microsoft Tools (OCMT), Autonomous Database (ADB) must already be provisioned.
You need access to the Oracle Cloud Console that has access to your ADB instance.
  1. Go to the cloud console screen for the ADB instance you connect to.
  2. Start your ADB instance.
  3. Click Database Connection.
  4. Click Download Wallet.
  5. Supply the wallet password. Confirm the password, and click Download.
  6. Download the ADB credentials zip file to the machine that has your Microsoft tool installed.
    OCMT uses these credential files (cwallet.sso, tnsnames.ora, and sqlnet.ora) to connect your Microsoft tool to ADB.

  7. Unzip the credentials, and place them on your Windows machine into a directory. Note the directory location.
  8. If you are connecting to one ADB instance:
    1. From the credentials directory, open sqlnet.ora in a text editor.
    2. Locate the following line: WALLET_LOCATION = (SOURCE = (METHOD = file) (METHOD_DATA = (DIRECTORY=?/network/admin)))
    3. Set the DIRECTORY value to the ADB wallet directory.
    For example,
    WALLET_LOCATION = (SOURCE = (METHOD = file) (METHOD_DATA = (DIRECTORY=C:\DATA\WALLET)))
  9. If you are connecting to multiple ADB instances:
    1. Ensure that each ADB instance is set up with a different wallet.
    2. In each wallet location, add the parameter WALLET_LOCATION to each connect descriptor in tnsnames.ora.
    3. After making your changes, save the file.
    For example:
    adwptr_high = 
    (description=(retry_count=20)(retry_delay=3)(address=(protocol=tcps)(port=1522)(host=host name))
    (connect_data=(service_name=service name))
    (security=(ssl_server_dn_match=yes)(WALLET_LOCATION=C:\DATA\WALLET\ADWPTR)))
    adwbi_high = 
    (description=(retry_count=20)(retry_delay=3)(address=(protocol=tcps)(port=1522)(host=host name))
    (connect_data=(service_name=service name))
    (security=(ssl_server_dn_match=yes)(WALLET_LOCATION=C:\DATA\WALLET\ADWBI)))
  10. Continue with the configuration of your specific Microsoft tool.

Note:

See Connecting with Microsoft Tools for more detailed information.