In your deployment directory there should be 5 files now: 2 Data Provider DLLs and 3 Instant Client ones. Even though first 2 names are the same, file sizes differ - so don't mix up DLLs from different distributions. For Lite version they are oci.dll, orannzsbb11.dll, and oraociicus11.dll (~31M). For Basic version they are: oci.dll, orannzsbb11.dll, and oraociei11.dll (111M). Upon downloading the client, copy 3 DLLs from it to our deployment directory. All client-side messages are in English.īasic is going to add ~105M to your distribution Basic Lite is ~32M.
It comes in a ZIP archive, unpack it to temp directory. At the moment the available version is 11.1.0.6.21, size 43M.
Registration is required to download software, but it is free and if you work with Oracle, registering at OTN is a good idea anyway.
It is coming bundled along with other Oracle Data Access Components (ODAC) and available on Oracle OTN site. They will be shipped to client as part of our XCOPY deployment.įirst, we'll need to download ODP.NET provider. Also we only bother about supporting English language.ĮTL stands for Extract, Trash, and depLoyĭeployment files come from ODP.NET and Instant Client, so create a directory for extracted DLLs. Only 32-bit clients are discussed, 64-bit components for 11.x are not yet available at the moment of writing.
In the coming post we will write a complete program connecting to any Oracle database and running arbitrary SQL statement passed as a parameter - with no need for any Oracle software installed on the client. Connection settings will be hardcoded for simplicity. In this post we will create a small Visual Studio project for program fetching sysdate from Oracle database. We can deploy all components needed to access databases with XCOPY method without messing with client machine's registry or other settings. To developers, this means we can now enjoy all the luxuries of genuine ODP.NET and relax prerequisite requirements. And the major pitfall was that ODP.NET didn't work with the Instant Client.įinally in 2008 Oracle released production version of ODP.NET provider for NET 2.0 which could work over Instant Client.
At that time Oracle also shipped Instant Client which was "only" 80M in size, but required no installation.
NET Provider came in 174M package and contained ODP.NET dlls along with full-blown client. The provider still needs Oracle Client software to be installed and configured on the user's machine.
On the downside it doesn't support SYSDBA connections, unable to configure fetch buffer size, and has no adequate method to retrieve Oracle error number from Exception.
NET runtime) plus moderate functionality. Its main advantage was zero installation (the provider comes with. That time's choice was OleDB data provider from Microsoft. While ago I wrote about choosing right Data Provider to access Oracle.