Our application is built and packaged with oracle 11g Oracle.DataAccess.dll and in the same box we have installed 12.2 Oracle Client (No other oracle client is installed). The Oracle server is running on 12.2 version. Now, when we are installing our product, it is trying to communicate to Oracle Server via the client. But the Oracle.DataAccess.dll of our product (which is basically 11g version) is not able to communicate to 12.2 Oracle Client. Is there a way we can communicate successfully?

The recommended provider ('Oracle.DataAccess.Client') is not installed. You can continue with your current provider, however it has been deprecated and may not work correctly. Confused from these messages. I'm using MS Office 2013 32 bit version. Have the Power query Plug-in enabled. I have Oracle client installed and have 2 Oracle homes in my machine (Windows 10.

We don't want to package the 12.2 dll with our installer and release it immediately. Please suggest if there is any tweak which can make it compatible. Thanks, Arindam. No, version of Oracle Client and version of Oracle.DataAccess.dll have to match. You may face problems even if the minor versions are different, e.g. Client Version 12.1.0.2.x vs. Oracle.DataAccess.dll version 12.1.0.1.x.

But it should be no problem, provided the ODP.NET (i.e. Oracle.DataAccess.dll) is installed with Oracle Client. The GAC should include Policies like Policy.4.112.Oracle.DataAccess.config -> It does not matter whether your application was build with ODP.NET version 11.2, the policy should redirect it to installed version 12.2 automatically. Otherwise go to one of these pages • • and download the matching XCopy version.

Extract correct Oracle.DataAccess.dll file from ZIP and provide it together with your application.

The chronicles of narnia 2005 in hindi download mp4. Installing Oracle Data Provider for.NET Oracle Data Provider for.NET is part of Oracle Data Access Components (ODAC), which can be downloaded from OTN. Beginning with ODAC 11.1.0.6.20, Oracle Data Provider for.NET can be installed through XCopy or Oracle Universal Installer.

• XCopy Administrators use XCopy to deploy Oracle Data Provider for.NET to large numbers of computers for production deployments. The XCopy has a smaller installation size and fine-grain control during installation and configuration than Oracle Universal Installer. • Oracle Universal Installer (OUI) Developers and administrators use Oracle Universal Installer for automated ODP.NET installations. It includes documentation and code samples that are not part of the XCopy. Note: This section describes installation using the Oracle Universal Installer. For installation and configuration using the XCopy install, refer to the README.TXT file that is part of the XCopy installation. Additionally, Oracle Data Provider for.NET Dynamic Help is registered with Visual Studio, providing context-sensitive online help that is seamlessly integrated with Visual Studio Dynamic Help.

With Dynamic Help, the user can access ODP.NET documentation within the Visual Studio IDE by placing the cursor on an ODP.NET keyword and pressing the F1 function key. Oracle Data Provider for.NET creates an entry in the machine.config file of the computer on which it is installed, for applications using ADO.NET 2.0 and OracleClientFactory class. This enables the DbProviderFactories class to recognize ODP.NET. Note: If the machine has the corresponding.NET Framework installed, then the Oracle.DataAccess.dll assembly is added to the Global Assembly Cache (GAC) as well.