Scribd
Upload
274 views7 pages

(SSIS) To Oracle Autonomous Database (ADB) : Certification Matrix 12.2 or Higher

This document provides instructions for configuring Microsoft SQL Server Integration Services (SSIS) to connect to Oracle Autonomous Database (ADB) using Oracle Data Provider for .NET (ODP.NET). It outlines downloading credentials, installing ODP.NET and SSDT, configuring ODP.NET connectivity, and testing the connection from an SSIS project in Visual Studio.

Uploaded by

Findi Latodjo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
274 views7 pages

(SSIS) To Oracle Autonomous Database (ADB) : Certification Matrix 12.2 or Higher

This document provides instructions for configuring Microsoft SQL Server Integration Services (SSIS) to connect to Oracle Autonomous Database (ADB) using Oracle Data Provider for .NET (ODP.NET). It outlines downloading credentials, installing ODP.NET and SSDT, configuring ODP.NET connectivity, and testing the connection from an SSIS project in Visual Studio.

Uploaded by

Findi Latodjo
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 7

Creating an ODP.

NET connection from Microsoft SQL Server Integration Services


(SSIS) to Oracle Autonomous Database (ADB)
Vijay Balebail, Alex Keh

Certification Matrix Version


Microsoft SSIS (32 bit) Independent of Version
Oracle Data Provider for .NET 12.2 or higher
(ODP.NET), Managed Driver or
Unmanaged Driver
Here is the overview of the installation and configuration process to connect SSIS to ADB using
ODP.NET. These instructions will work for both dedicated and serverless ADB.

Note: ODP.NET, Managed Driver supports Bulk Copy functionality starting with version 20.

SSIS uses ODP.NET to


Provision Download credentials file
connect to Oracle ADB
ADW to SSIS system
A A

Install Visual Test ODP.NET


Install ODP.NET on the Configure
Studio with connectivity
Visual Studio system ODP.NET
SQL Server
connectivity
Data Tools
SSIS is now
configured

1. This document assumes that the Autonomous Data Warehouse (ADW) or Autonomous
Transaction Processing (ATP) has been provisioned and the corresponding credentials.zip
file has been downloaded to the system that has SQL Server Data Tools (SSDT) installed. For
the Oracle documentation to provision ADWC please check here. Also check Downloading
Client Credentials (Wallets).

2. Follow the instructions from the SSIS documentation to install SSDT software on your
machine. As a prerequisite, make sure that you have installed the ODP.NET 12.2 or higher
on the SSDT environment. You can download ODP.NET separately or as part of the Oracle
Database Client for Windows. Note: If you are using unmanaged ODP.NET, you must use 32-
bit Oracle Client installation to match the fact that SSDT is a 32-bit app.
3. All connections to Autonomous Database use certificate-based authentication and
Transport Layer Security/Secure Sockets Layer (TLS/SSL). Copy the client credentials file that
you downloaded in step 1 to the system running SSDT and uncompress it into a secure
folder.

4. We first validate that the Oracle Database Client can communicate with ADB, and since it is
installed on the same system as the SSDT and SSIS, it ensures that SSIS connectivity to
Oracle is also configured correctly.

5. Steps 5, 6 and 7 configure and test the Oracle Database Client. Edit the sqlnet.ora file,
replacing “?/network/admin” with the name of the folder containing the client credentials.

For example:

WALLET_LOCATION = (SOURCE = (METHOD = file) (METHOD_DATA =


(DIRECTORY=C:\extract\Oracle_wallet)))
SSL_SERVER_DN_MATCH=yes

6. Create the TNS_ADMIN system environment variable and set it to the location of the secure
folder containing the credentials file you saved in Step 3. The tnsnames.ora file provided
with the credentials zip file contains three database service names identifiable
as high, medium and low. The predefined service names provide different levels of
performance and concurrency for ADB.

7. Test the Oracle Client with Oracle SQL*Plus

sqlplus password/\"Password\"@ConnectString
or
sqlplus /nolog
sql> set define off
sql> connect username/password@connectString

8. SSDT and SSIS can use managed or unmanaged ODP.NET to connect to ADB. Transport Layer
Security (TLS) 1.2 support has been included in version 12.2 and higher.

9. Register managed or unmanaged Oracle Data Provider for .NET (ODP.NET) in the Global
Assembly Cache (GAC) so that it is recognized by .NET products, including SSDT. Note
that SSIS is a 32-bit application and we need to configure 32-bit ODP.NET for SSIS.

10. Open a command prompt in Administrator mode. You can do this by right-clicking on the
command prompt, then choosing “Run as administrator”.
11. Navigate to the <Oracle Home>\ODP.NET\managed\x86 directory and execute one of the
following commands.
• For managed ODP.NET:

OraProvCfg /action:config /product:odpm /frameworkversion:v4.0.30319


/providerpath:"../common/Oracle.ManagedDataAccess.dll"

• For unamanged ODP.NET:


OraProvCfg /action:config /product:odp /frameworkversion:v4.0.30319
/providerpath:"../../bin/4/Oracle.DataAccess.dll"

Below is the output from running the above command with managed ODP.NET 19c. You should
see the following output or similar depending on the ODP.NET version and type you use:

INFO: The following section has been added.


<section name="oracle.manageddataaccess.client"
type="OracleInternal.Common.ODPMSectionHandler,
Oracle.ManagedDataAccess, Version=4.122.19.1, Culture=neutral,
PublicKeyToken=89b483f429c47342" />

INFO: The following element added under DbProviderFactories.


<add name="ODP.NET, Managed Driver"
invariant="Oracle.ManagedDataAccess.Client" description="Oracle Data
Provider for .NET, Managed Driver"
type="Oracle.ManagedDataAccess.Client.OracleClientFactory,
Oracle.ManagedDataAccess, Version=4.122.19.1, Culture=neutral,
PublicKeyToken=89b483f429c47342" />

12. Newer Visual Studio versions include SSDT as an installable extra option. Once installed,
SSDT is integrated into Visual Studio. Open Visual Studio and create a new SSIS project.

11. Right click on Connection Managers area at the bottom of the project and click on New
ADO.NET Connection…
12. In the Configure ADO.NET Connection Manager pop-up, click “New…” to create a new
connection.

13. In the .NET Provider tree control, pick “ODP.NET, Managed Driver” or “ODP.NET,
Unmanaged Driver”. Only the ODP.NET providers you have specifically configured with
the OraProvCfg utility will appear. Press OK.
14. Enter in your ADB net service name in Data Source (e.g. stats2_medium), user id (e.g.
admin), and password information into the respective fields.
15. click Test Connection
If you have successfully tested the connection, your SSIS project can connect to ADB.

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy