Installing ODAC for .Net - odac

I have Visual Studio.Net 2008 in my Windows XP machine.
I have Oracle 10g client.
As one of my applications uses ODAC, I need to install ODAC now. The latest version of ODAC is ODAC 11.2 Release 3 (11.2.0.2.1) with Oracle Developer Tools for Visual Studio.
My question is, as I already have C:\Oracle\ folder if I install this ODAC again it installs one more oracle_home folder which I dont need.
Could you please suggest how how I can install it?
Thanks

No, you will need to install the version of the Oracle client that the ODAC wants. You also have to decide between 32 bit and 64 bit.
One caution if you are new to Oracle and .Net, you will have to install the oracle client on the server and that creates a lot of problems.

In case someone stills have a similar inquietude ODAC doesn't install an oracle client in the machine, Odac will use the oracle client to communicate with Database Server, so no it won't create a new oracle_home folder.

Related

odac setup error ins-50013 Oracle Developer Tools for Visual Studio .NET Error

I move from here Beyond it is the same issue. The problem i am facing is different.
I want to install ODAC 122011. I have windows 64 bits.. And i am using Visual Studio 2017/2019 32bits.
I intented to install ODAC 64 bits, but, due to my Visual Studio version is 32 bits, i am trying to install ODAC 122011 called ODTwithODAC122011.zip. It is the ODAC 122011 32 bits i found.
When i run the setup, I face this problem..
Following this article I installed ODTforVS2017_122011.exe I think it was unnecesary.
Nevertheless, the problem remains.
What I am missing?
Try to install Oracle Developer Tools for Visual Studio before installing the ODAC
For EX: I installed - > ODTforVS2017_122010 for VS2017 from https://www.oracle.com/database/technologies/dotnet-odacmsi-vs2017-downloads.html
then I installed ODAC it worked for me

Microsoft SSIS Connectors by Attunity Version 4.0 NOT showing on Visual Studio 2015

In one of our company meetings with Microsoft we were advised to use Microsoft SSIS Connectors by Attunity Version 4.0 if we extract data from Oracle. We used to extract the data from Oracle using Oracle Provider for OLE DB.
I have tried to install the recommended components without success. I have oracle clients 32 bits (ODTwithODAC122010.zip) and 64 bits (ODAC122010_x64.zip) installed and then I attempted to install SSIS Attunity Connectors as explained on this post. It's supposed that after the installation I would see the components on the SSIS toolbox (Data Flow section) but no matter what I do they simply don't show up.
I can successfully connect to oracle server using the component we have always used.
My SSIS projects target version is SQL Server 2016. Visual Studio 2015 Enterprise. My OS: Windows 10 Enterprise.
I tried to install v4 32-bit version of the attunity connector and it did not work, I also tried to install v3 64-bit version of the attunity connector and the installation failed because I don't have SQL Server 2014 installed only 2016, which is why I'm supposed to use v4 64-bits.
Any advice from anybody who had an issue like this before?
You need both x86 and x64 versions of the Oracle clients.
And you should install both 4.0 and 5.0 x64 (x86 will be added automatically) versions of Attunity connectors.
After that you should be able (almost guaranteed) to see Attunity connectors in the SSIS Toolbox in VS2015.
Hope this helps.

Why is current Oracle ODAC connectability not visible in VS 2013?

I'm trying to setup my first Oracle database connection in Visual Studio 2013 and the only option available for the Data Source is a selection "Oracle Database". But that selection says it's deprecated (and it doesn't even allow me to choose the schema as I could do in VS2012, regardless, so it's unusable).
I already have an ODAC installed that works great for VS 2012 (11.2.0.3). Is there any way to get VS 2013 to recognize that I already have that installed (tried putting in a reference to the Oracle Data Client and that didn't work). Choosing "Other" doesn't provide me any other choices.
Am I forced to install ODAC 12c just so that VS 2013 sees it? Why wouldn't it see ODAC 11? I'd rather not do the 12c install due to other projects that rely on the older one (and, yes, we could go down a VM path, but that's not an immediate option).
You have to rerun the ODAC installer, you will be asked to reinstall .NET +.ASP components (I just excluded the examples package.)
My situation was a bit different: I Installed at first VS 2013 with ODAC and then VS 2012. The result was that VS 2012 didn't see the ODAC part: like you said the Data source with the "Oracle Database" choice. Rerunning the installer fixed this issue.
I think it's the same situation as mine. ODAC shouldn't be dependent on Visual Studio version but on the .NET framework in use.

ODAC 10.20221 visual studio integration

I've downloaded ODAC1020221.exe from oracle website. It installed 10g client but neither VS2008 nor VS2010 sees ODAC provider. Oracle client 11 doesn't work with our oracle server (9.1 version), but just for the sake of test I've tried to install it and visual studio sees ODP.NET fine.
ODP.NET 10 supports only 1 and 2 framework? VS2008 and 2010 do not see ODP.NET 10 because of that?
Odac is only compatible with 10g and up

OraOLEDB.Oracle not showing in SQL Server Management Studio providers

I'm trying to add an Oracle server as a linked server to SQL Server. I've downloaded and installed Oracle's instant client and ODAC software. However, OraOLEDB.Oracle does not show up in the list of providers in SSMS. My machine is running Windows 7 (64 bit) and MSSQL Server 2008 R2.
I am trying to fix this same issue. I found this detailed set of instructions, however they didn't work for me. I encountered some installation errors with ODAC. Perhaps they can be of help to you though.
Installing 64-bit Oracle ODAC 11.2 to Microsoft SQL Server 2008 R2 x64
http://nampark.wordpress.com/2011/01/20/installing-64-bit-odac-11-2-to-microsoft-sql-server-2008-r2-x64-for-replication/
OraOLEDB provider is not installed with instant client. You have to install the full client.

Resources