Issues with different versions of Oracle.DataAccess.dll

I have a .net web service application which references version 10.2.0.100 of Oracle.DataAccess.dll. A client has setup Oracle 10g database on the server, but I think the server has a patch set installed so it appears that the versions of Oracle.DataAccess.dll in my web service and on the database server do not match. When I issue a query via the web service on my local machine using my oracle 10g client, the web method returns the correct data. If I issue the same query using the same .net web service on the clients database server, I get the following error: Oracle.DataAccess.Client.OracleException: ORA-00923: FROM keyword not found where expected. There's nothing wrong with the query syntax, I can run the same query from SQL Plus on the database server and get the correct data. Could it be a compatibility issue between the Oracle.DataAccess.dll referenced in my web service application and the file on the sever. I'm not sure what else to look for, any advice is greatly appreciate, and I can answer any questions if needed.
Thanks,
NA

I would not expect an ORA-923 if your the Oracle client was not installed properly. I would expect an exception or a crash.
You can run an ODP.NET trace to find out what query is getting the ORA-923 by doing the following:
1) Shutdown web server on the machine that runs the webservice (middle tier),
2) In windows registry, on the machine that runs the webservice (middle tier), change registry value \\HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ODP.NET\4.112.1.1\TraceLevel to 1
3) Reproduce the ORA-923 only
4) shutdown webserver
5) Undo the registry value (set it back to 0)
6) In the generated file (c:\odpnet2.0.trc) do a search for "923", hopefully you can find it. Just before that error, you should see the SQL that was executed. This will obviously not be what you expect and will hopefully point you to the cause of the problem.

Similar Messages

Browser compatibility issues with different versions of IE

I'm looking for an online resource or book on identifying/troubleshooting JSP browser compatiblility issues focusing on recent versions of IE (5.0 - 6.0).
Any sugguestions?

A JSP runs on a server. It is actually a servlet that merely outputs HTML (usually) to the browser. Your browser does not (really) know the difference between a JSP and a static HTML page and PERL cgi generated page. There is no interaction what-so-ever between the JSP portion and your browser. There will not be any books about compatibility issues between JSP and browsers since its a non-issue.
The previous reply suggesting JavaScript conflicts is entirely true. If you want a flipping nightmare job, write javascript that is compatible on NN 3.0 and above and IE 4.0 and above. It's a godd**ned mess.

Oracle.DataAccess.dll 2.112.1.0 vs 2.111.7.0

Hi,
I built a windows 7 64 bit dll application with Oracle 11g, my Oracle.DataAccess.dll version is 2.112.1.0. when I create setup package, I exclude Oracle.DataAccess.dll. When I install it on my user's machine, which have 2.111.7.0 version of Oracle.DataAccess.dll. Now it stop working.
what's the best solution:
a) install 2.112.1.0 version of Oracle.DataAccess.dll in my setup package and install it on user's machine
b) uninstall my 2.112.1.0 version of Oracle client, install 2.111.7.0 one
c) other... ?
also, should I use 64 bit Oracle 11g client?
Thank you,
Wes

wesbird wrote:
When I install it on my user's machine, which have 2.111.7.0 version of Oracle.DataAccess.dll. Now it stop working.
a) install 2.112.1.0 version of Oracle.DataAccess.dll in my setup package and install it on user's machineJust wanted to point out that if "2.111.7.0" means the user's machine has Oracle 11.1.0.7 something installed, then simply including a "2.112.1.0" dll is not enough i.e. whole 11.2 Client install is needed. Having multiple Oracle homes on a Windows pc might not work well for some apps (think dependencies/support requirements for 3rd part Oracle apps).
Perhaps ODAC Xcopy deployment package could help simplify deployment.
32-bit ODAC Xcopy version
http://www.oracle.com/technetwork/database/windows/downloads/utilsoft-087491.html
64-bit equivalent
http://www.oracle.com/technetwork/database/windows/downloads/index-090165.html
Edited by: orafad on Aug 24, 2011 1:10 AM

Upgraded to 64 bit Oracle DataAccess.dll and now more open cursors errors

Hi, We recently converted from .net framework 1.1 application to .net 4.0 framework for 64 bit. We installed the 64 bit version of Oracle DataAccess dll. It now seems like we are getting many more open cursor error messages in our application. The open_cursor value set in the database has not changed and other than the 64 bit Oracle and .net 4.0 framework nothing has changed. I was just curious if anyone else that has converted to the 64 bit Oracle DataAccess dll has experienced an increased number of open cursor errors? If so, what was the resolution.
I apprecieate any feedback.
Thanks

What do you have /32BIT flag set to in the assembly? Ie, was it compiled with AnyCPU, x86, etc? You can use corflags.exe with the .net sdk to find out.
Prior to VS2010, the default was AnyCPU which meant it ran as 64 bit on 64 bit OS, and 32 bit on 32 bit OS.
As of VS2010, the IDE defaults to x86, which means it runs as 32 bit no matter what.
32 bit apps need 32 bit odp/client. 64 bit apps need 64 bit odp/client.
The error you're getting usually means you have the wrong bits (32/64) of the Oracle client installed.
Assuming you have the wrong client bits installed, you could either
a) make the app run as the other bits by setting/clearing the 32BIT flag (also by using corflags.exe)
b) install the other bits of Oracle client software. a 32 bit home and a 64 bit home play rather nicely together for the most part, but you need to install them into separate homes.
Hope it helps,
Greg

Oracle.DataAccess.dll FileNotFundException in VS 2010 project

Hello,
I've got a troubleshot whith my Windows Service App, build in VS 2010 (Professional & Ultimate ed.) (build in both x64 & x32) :
FileNotFoundEcxeption
"Could not load file or assembly 'Oracle.DataAccess, Version = 4.112.2.30, Culture = neutral, PublicKeyToken = 89b483f429c47342'or one of its dependencies. The specified file is not found."
Same things when i'll try to run the examples project in ODP.NET Package 11.2.0 (FrameWork V2.x and V4).
My Windows Service worked correctly before, but stoped working since few days. Maybe new updates of .NET frameworks ?
Thanks for your help.

wesbird wrote:
When I install it on my user's machine, which have 2.111.7.0 version of Oracle.DataAccess.dll. Now it stop working.
a) install 2.112.1.0 version of Oracle.DataAccess.dll in my setup package and install it on user's machineJust wanted to point out that if "2.111.7.0" means the user's machine has Oracle 11.1.0.7 something installed, then simply including a "2.112.1.0" dll is not enough i.e. whole 11.2 Client install is needed. Having multiple Oracle homes on a Windows pc might not work well for some apps (think dependencies/support requirements for 3rd part Oracle apps).
Perhaps ODAC Xcopy deployment package could help simplify deployment.
32-bit ODAC Xcopy version
http://www.oracle.com/technetwork/database/windows/downloads/utilsoft-087491.html
64-bit equivalent
http://www.oracle.com/technetwork/database/windows/downloads/index-090165.html
Edited by: orafad on Aug 24, 2011 1:10 AM

Oracle.DataAccess.DLL connection issues...

Greetings, all. This Oracle Novice is having some right fun trying to talk to ODP.NET. I am actually very successful at using the 9.2.0.1.0 drivers, so talking to the db is no problem. But I cannot seem to get ODP.NET to work.
I installed all of the available components from the latest ODP.NET download except the one for the Transaction Server. The code I am using is trying to talk to ODP.NET to facilitate a BLOB upload. Here is the line that .NET comes to s screeching halt on:
<%@ Register TagPrefix="oda" Namespace="Oracle.DataAccess" Assembly="Oracle.DataAccess, Version=9.2.0.11, Culture=neutral, PublicKeyToken=89b483f429c47342" %>
And here is the error I receive:
Assembly Load Trace: The following information can be helpful to determine why the assembly 'Oracle.DataAccess' could not be loaded.
=== Pre-bind state information ===
LOG: DisplayName = Oracle.DataAccess, Version=9.2.0.11, Culture=neutral, PublicKeyToken=89b483f429c47342
(Fully-specified)
LOG: Appbase = file:///c:/inetpub/wwwroot
LOG: Initial PrivatePath = bin
Calling assembly : (Unknown).
===
LOG: Publisher policy file is found at C:\WINDOWS\assembly\GAC\policy.9.2.Oracle.DataAccess\9.2.0.700__89b483f429c47342\Policy.9.2.Oracle.DataAccess.config.
LOG: No redirect found in host configuration file (C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\aspnet.config).
LOG: Using machine configuration file from C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\config\machine.config.
LOG: Post-policy reference: Oracle.DataAccess, Version=9.2.0.11, Culture=neutral, PublicKeyToken=89b483f429c47342
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/root/2135a508/8d69a834/Oracle.DataAccess.DLL.
LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v1.1.4322/Temporary ASP.NET Files/root/2135a508/8d69a834/Oracle.DataAccess/Oracle.DataAccess.DLL.
LOG: Attempting download of new URL file:///c:/inetpub/wwwroot/bin/Oracle.DataAccess.DLL.
WRN: Comparing the assembly name resulted in the mismatch: Revision Number
I am totally lost as to what all this means. Can someone offer some guidance to this wayward newbie? Thanks!
OH! I should mention that I now have a copy of Oracle.DataAccess.DLL in each of the directories mentioned above.
Steve

Hello,
What was the resolution to this? I am facing the same issue and am completely lost.
One additional info in my case....Please bear with me..I am novice .NET developer. my aspx pages seem to work fine with Oracle client 9.2 but not on machine with Oracle 10g. I get the same error listed above.
I noticed Oracle.DataAccess.dll had different dates. The one under ORACLE_HOME was newer compared to the ASP.NET/bin dir.
Any help would be appreciated.
Thanks

Oracle.DataAccess.dll targets a different processor than the application

I need help to solve the error message for Referenced assembly 'bin\Oracle.DataAccess.dll' targets a different processor than the application
I have try two different verison 11 and 10 has the samething
Anyone know what causeing this problem?

I had this and changed the platform target in VS to x86 and the warning disappeared. I think it's because the Oracle.DataAccess.dll is targetted specifically for the x86 platform.

ODAC Release 4 & 5 - Oracle.DataAccess.dll 4.112.3.0

Has anyone else noticed that ODAC Release 4 & 5 have the same AssemblyVersion 4.112.3.0?
Oracle Data Access Components (ODAC) for Windows
It took me a while to spot the problem. I'm using Entity Framework 5 and hit a machine with Release 4. It threw an completely misleading exception on load.
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.TypeInitializationException: The type initializer for 'Oracle.DataAccess.Client.OracleConnectionStringBuilder' threw an exception. ---> System.TypeInitializationException: The type initializer for 'Oracle.DataAccess.Client.RegAndConfigRdr' threw an exception. ---> System.Configuration.ConfigurationErrorsException: MySchema.MyPackage.MyProcedure.RefCursorMetaData.CUROUT.Column.1 is invalid
   at Oracle.DataAccess.Client.RegAndConfigRdr.AddMetadataForRefCursor(String refCursorKey, String metadataInfo, Hashtable& schemaTable)
   at Oracle.DataAccess.Client.RegAndConfigRdr.RetrieveInfoFromConfig(NameValueCollection nvc, Hashtable& schemaTable, Boolean bIsCallFromODT)
   at Oracle.DataAccess.Client.RegAndConfigRdr..cctor()
Since ODAC Release 4 was installed, the machine had Oracle.DataAccess.dll (4.112.3.0) in GAC. Thus, my application could not use my local copy of Oracle.DataAccess.dll (4.112.3.0) from Release 5.
Having the same AssemblyVersion for Release 4 and 5 causes issues. Can we get an additional release with an updated version?

Can you elaborate on the versioning policy for ODAC? What I'm looking for ideally is an incrementing AssemblyVersion with releases as was done previously with Oracle 11 R3, R4, R5. For example,
ODAC 12c Release 1
AssemblyVersion = 4.121.1.0
AssemblyInformationalVersionAttribute = 4.121.1.0 12c R1
ODAC 12c Release 2
AssemblyVersion = 4.121.2.0
AssemblyInformationalVersionAttribute = 4.121.2.0 12c R2
In your post https://forums.oracle.com/message/11264632#11264632 you describe best practice.
The best practice is to install 64-bit ODP.NET following the install instructions. To make sure each application can find its correct unamanged Oracle Client DLLs, I recommend setting the DllPath setting described in Chapter 2 of the ODP.NET Dev Guide. Typically, the problem people run into with multiple ODP.NET versions on the same machine is ensuring each ODP.NET version uses its correct Oracle Client version (i.e. avoiding DLL Hell). Setting DllPath is a straightforward to ensure all your ODP.NET apps will use the right dependent Oracle Client DLLs.
If we are to follow your recommend best practice then we must have different AssemblyVersions with each release. Otherwise, we could load the wrong ODP.NET Oracle.DataAccess.dll from the GAC that doesn't match the unmanaged Oracle Client dlls we specified with the DllPath setting.
If I've missed something, please let me know.

Is it safe to Corflag Oracle.DataAccess.dll

Hello,
Is it safe to use CORFLAGS.EXE to change the bit-architecture of the Oracle.DataAccess.dll (the version included in Oracle Client 11gR2) to AnyCPU by clearing up the 32bit flag?
This dll (in the Oracle Client 32 bit installation) originally has the 32bit flag set to 1 like this:
PE        : PE32
32BIT     : 1
but all the rest of the dlls (some are 3rd party) in my projects have this flag clear b/c they are AnyCPU. They are set like this:
PE        : PE32
32BIT     : 0
so at runtime it throws BadImageFormatException b/c some dlls are AnyCPU and others are 32bit
If I copy the 32bit Oracle.DataAccess.dll to my project's local folder, change the project to reference this local copy, and clear the dll's 32bit flag with corflags, making it AnyCPU, that works around the exception, and the project runs w/o apparent issues. But I wonder whether clearing this flag would make this dll unsafe or poses any other problem.
I'd appreciate if you could talk about the implications or side-effects, or if there's another way to solve this architecture/bit dilemma
Is there an AnyCPU Oracle Client out there?
Thank you in advance
Sincerely,
Richard

Thanks to Mark for your advice. Let me say for the sake of clarity that I'd never think of corflag-ing the original dll not place an adultered dll in the GAC; I was thinking to place the changed dll in a local folder under the project (bin), and refer to this local copy
I'm interested in the Managed Provider but I know nothing about it yet, and I'm sure I'd have to make source code changes in the projects. I'm not sure if the developers of the Oracle Client realize that we're not in a vacuum out here, and when something stops being supported, it breaks things businesses are using for day-to-day work; when a product stops being backwards compatible, it creates lots of problems that affect businesses. For example, I see recommendations like to rebuild the project as 32bit or 64bit, but these are not Hello World or demo projects, these projects depend on 3rd party components that aren't available in those architectures, they are only AnyCPU. There are also other dlls from other teams in-house, from which I don't own the source code. It's impractical to ask people who are busy working on their own assignments, to convert 6 or 7 projects which have been untouched for years w/o having a business need. Another issue with changing everything to 64bit is that these apps are running on development, test, and production servers, which are 32bit, so in order to move them to 64bit, infrastructure would have to migrate each one of these environments to new servers, then the apps would have to be tested by users of the business, wasting their time all over again again... Not practical
All this trouble comes b/c I'm just moving my development machine to 64bits. I'm not supposed to be working/wasting time rewriting code that's locked under source control and has been tested and approved, and has been running in production for years. That's the reason why I'm not very pleased with the idea of the Managed Provider, b/c code that's in production, will have to be rewritten, deployed again in test, re-tested, and then released to production again, when there should be an AnyCPU version of the client and that'd be the end of it. All apps we have use the client, so eventually would everything have to be rewritten for this Managed Provider?
If I install the Managed Provider is it likely to create issues with the Oracle Client I already have installed?
Thank you very much
Richard

'The provider is not compatible with the version of Oracle client error' popping up randomly

I have several asp.net pages running on an application server which generally work without issue. However I've had the Server error "The provider is not compatible with the version of Oracle client error" crop up twice seemingly randomly that affects all of my pages that interact with the DB server. A simple reboot of the application server solves the issue and the pages run again with no problems. What could be causing this problem?

Sorry if I wasn't clear initially. Basically I've got 2 different applications in 2 different IIS folders on the webserver, each with several asp.net pages. They work fine for a period of time and then inexplicably that error gets thrown and affects all of my asp.net pages in both applications. The admin tells me that the other older applications on the same server are unaffected. A simple reboot of the server fixes the issue until the next time it happens (I can't identify any consistent point where this crash happens, the admin originally suggested that there might be something in my code causing a memory issue). I had the same applications hosted on my local machine for a time and this never happened as well as it never happening when I run them in localhost. How can I trace whether or not another part of my application is trying to load ODP.NET by itself? How can I verify the DLL search order for my application?

Problem using oracle.dataaccess.dll

Hi,
I have an web application which uses Oracle.DataAccess.dll to communicate with and Oracle db. The web application deployed on 32 bit windows system works but not on windows server 2008 64 bit. I installed 10204_vista_win2k8_x64_production_db package, referenced the installed dll (version 2.102.4.0) from the project but I get the following error:
Could not load file or assembly 'Oracle.DataAccess, Version=2.102.4.0, Culture=neutral, PublicKeyToken=89b483f429c47342' or one of its dependencies. The system cannot find the file specified.
Any help is appreciated. Thanks in advance.

I had this problem too.
I have not found any way to get ODP to work on a 64 bit machine. I have gone through more than 30 permutations of install combinations and all have their problems.
Your's is one I remember.
The error message does not give a good description of the problem. It CAN find it, but it can't load it.
The main problem in my opinion is that Visual Studio is a 32 bit app and so are its tools. MS will say that is no big deal because they don't want to rewrite native code sooner than they have too. It is going to stay that way for 2010. Visual Studio is going to load a .dll to connect to Oracle in server explorer and in any datasets you have created with the designer...its going to use a 32 bit .dll now your application wants a 64bit .dll... see the problem? I beleive that when you install the ODP registry settings are made for viual studios sake, but I don't know what happens under the hood.
Does visual studio give you any option at all to choose what assemblies to use for the IDE tools? nope
I have tried 32 bit client, 64 bit client, ODACwithODP and every combination of them in every version oracle offers on their download site. Nothing worked 100%.
I got
1) "cannot load file x" when x is at the specified path
2) BadImageFormat exception
3) App worked but visual studio tools crashed the IDE
4) installed all 3, but used the old system.data.oracleclient and tools worked sluggish or crashed.
You can also combine the problem of Oracle provider along with the fact that 1/2 of Visual Studio's tools don't care about 64 bit programming. For example, I made a wcf service that as going to access my database. Well, guess what you can't use Visual Studio's WCF debugger because WcfSvcost.exe is 32 bit. Will it give you an informative error message? nope. Just a BadImageFormat Exception with no clue which file is causing the problem. spent a week of precious time on that one and thought it was an oracle provider issue.
I have given up using ODP for now and am forced to use (4) System.Data.OracleClient just for the sake of getting any coding done at all instead of hacking my environment. It sucks. I got that working by installing 11r2 64 bit client in one home and 11r2 64bit client in another, then ODP in a 3rd. That way I can still use more friendly tools made for Oracle and let VS use the 32 bit client with the old System.Data.OracleClient dll.
If anyone has the magic step but step to get both a working IDE with its tools remaining functional along with a working application on Windows 7 64bit, than please please let me know!

Error :"The provider is not compatible with the version of Oracle client"

Hi guys!
I'm facing this problem:
When my .Net application tries to access the DB, I get this error message above.
The application is into the same machine of DB and the operational system is Windows Server Enterprise 64 bits.
I'm comparing to another machine that has the same scenario but runs in Windows Vista 64 bits. This problem doesn't happen and I can normally access the DB.
The both database versions are 10g Release 2 (10.2) and all components from Oracle Database Components 10.2.0.2.21 are installed as the containing bellow:
-Oracle Data Provider for .NET 1.x 10.2.0.2.20
-Oracle Data Provider for .NET 2.0 10.2.0.2.20
-Oracle Developer Tools for Visual Studio .NET 2003 10.2.0.2.20
-Oracle Developer Tools for Visual Studio 2005 10.2.0.2.20
-Oracle Provider for OLE DB 10.2.0.2.20
-Oracle Objects for OLE 10.2.0.2.20
-Oracle Services For Microsoft Transaction Server 10.2.0.1.0
-Oracle Net 10.2.0.1.0
-Oracle Universal Installer 10.2.0.2.0
Oracle.DataAcces.DLL is 2.102.2.20 and it is reference in my .Net app (that is published and located into IIS).
These are the Oracle assemblies installes in 'C:\Windows\Assembly':
Windows Vista Machine:
ASSEMBLY NAME VERSION CULTURE PUBLIC KEY TOKEN PROCESS ARCHITECTURE
Oracle.DataAccess 10.2.0.100 Neutral 89b483f429c47342
Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 pt-BR 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 it 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 fr 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 es 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 de 89b483f429c47342
Oracle.Management.Omo 2.102.2.20 Neutral 89b483f429c47342 x86
Oracle.VsDevTools 2.102.2.20 Neutral 89b483f429c47342 x86
Policy.10.1.Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
Policy.10.2.Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
Windows Server Machine:
ASSEMBLY NAME VERSION CULTURE PUBLIC KEY TOKEN PROCESS ARCHITECTURE
Oracle.DataAccess 10.2.0.100 Neutral 89b483f429c47342
Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
Oracle.DataAccess 2.102.2.20 Neutral 89b483f429c47342 x86
Oracle.DataAccess.resources 10.2.0.100 pt-BR 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 zh-CHT 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 zh-CHS 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 ko 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 jp 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 it 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 fr 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 es 89b483f429c47342
Oracle.DataAccess.resources 10.2.0.100 de 89b483f429c47342
Policy.10.1.Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
Policy.10.2.Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
Policy.9.2.Oracle.DataAccess 10.2.0.100 Neutral 89b483f429c47342
Policy.9.2.Oracle.DataAccess 1.102.2.20 Neutral 89b483f429c47342
What should I check and do to solve this problems?
Thanks for help,
Anderson

Hi,
Often the error "The provider is not compatible with the version of Oracle client" is raised when the unmanaged dll OraOpsX.dll can't be found, can't be loaded, or is the wrong version. For version 10.2.0.x of ODP.NET and .NET Framework 2.x the file should be called "OraOps10w.dll" and should be found in the %ORACLE_HOME%\bin directory.
Since the ODAC pieces are installed on the same host as the database, are they in a separate Oracle Home or the same Oracle Home as the database software? If there are multiple Oracle Home directories, which one is in the system path first?
I would start with verifying the version of OraOps10w.dll and the system path on the server. You might also confirm that the Oracle Home directory (and everything under it) has the following permissions for Authenticated Users:
- Read & Execute
- List folder contents
- Read
Regards,
Mark

The provider is not compatible with the version of Oracle client

We are running Server 2012 64 bit with multiple homes one is 32 bit and the other 64 bit. We installed the 64 bit first then the 32 bit next in order to get our Classic ASP WebSite that is using COM+ and OLEDB to see the provider.
C:\oracle\product\12.1.0\x86
C:\oracle\product\12.1.0\x64
The other Websites are ASP.Net 4.0 and are running in 64 bit application pools. They are using a DAL .Net assembly built x64 with a reference to the 64 bit ODP.Net version 4.121.1.0 in C:\oracle\product\12.1.0\X64\client_1\odp.net\bin\4.
I also see there is another folder C:\oracle\product\12.1.0\X64\odac_1\odp.net\bin\2.x with version 2.121.2.0. We are on running Framework 4.0 but when I switch to this version it works but with the version out of the bid\4 we are receiving the following error when the 64 bit Websites call the assembly:
The provider is not compatible with the version of Oracle client
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: Oracle.DataAccess.Client.OracleException: The provider is not compatible with the version of Oracle client
Source Error:
Line 87: mDataSource = dataSource
Line 88: mConnectionString = GetDBConnectionString(dataSource)
Line 89: mConnection = New OracleConnection(mConnectionString)
Line 90: mParams = New List(Of IDbDataParameter)
Line 91: End Sub
I have not been successful in getting this to work after spending endless hours, so any help would be appreciated.

Hi,
Oracle Client/ODP build with certified Visual C++ Libraries so application using ODP.NET requires "runtime components of Visual C++ Libraries" to be installed.
Oracle Database Client installation includes the Visual C++ Libraries but ODAC doesn't contain these libraries which may cause such issue.
Please check the Note 43208.1 for the particular version of Visual C++ installs with Oracle Database Client installation(e.g. 11.2.0 Database Client installs Visual C++ .NET 2005) and also you can refer the windows event log error massage to verify which version of Visual C++ is missing.
thanks and regards
Venkat

'The provider is not compatible with the version of Oracle client' exceptio

Hi
I installed ODAC-11.1.0.7.10 Beta on my development system and developed a .net application which uses Oracle.DataAccess.dll to connect to Oracle10g database.
the application is working fine, means opening connection successfully when I run it from my development system. but the same application is throwing
'The provider is not compatible with the version of Oracle client' exception when I run it on my 10g database server system.
what I need to do to run the application successfully on the machine where 10g server exists?
any help is appreciated.
thanks,
harry

Hi Harry,
I am not sure why you installed 11.1.0.7.10 Beta as 11.1.0.7.20 has been released and you should not be using the beta at this time. That error message is because the dependencies being loaded by the process are the wrong version. When you deploy an ODP .NET application using 11.1.7.x, you need to make sure you deploy it to a machine where the 11.1.0.7.x dependencies are installed. My guess is if I read your poat correctly is that Oracle.DataAccess.dll version 11.1 is loaded but its finding 10.2 dependencies on the target deployment box.
HTH
Jenny

Oracle.DataAccess.dll on Windows 7 64 bit

Hi,
I am migrating a .Net 3.5 windows class library from WinXP 32 bit to Win7 64 bit. I use Oracle 11g 64 bit client to connect to database.
my code works in Debug build but not in Release build. here is the error message:
"An attempt was made to load an assembly with an incorrect format:"
I did not complete uninstall by Oracle Deinstall, and re-install it.
Debug build have a waring:
"Assembly generation -- Referenced assembly 'Oracle.DataAccess.dll' targets a different processor."
Release build still the same incorrect format error.
here is more information:
under C:\Windows\assembly
Oracle.DataAccess 2.112.1.0 89b483f429c47342 AMD64
Oracle.Web 2.112.1.0 89b483f429c47342 AMD64
How should I fix it? should I download and install "64-bit Oracle Data Access Components (ODAC)"? What's difference between ODP.net in Oracle client and in ODAC?
Thank you,
Wes
Windows 7 Pro, 64 bit, Visual Studio 2010, Oracle 11g 64 bit client

What do you have /32BIT flag set to in the assembly? Ie, was it compiled with AnyCPU, x86, etc? You can use corflags.exe with the .net sdk to find out.
Prior to VS2010, the default was AnyCPU which meant it ran as 64 bit on 64 bit OS, and 32 bit on 32 bit OS.
As of VS2010, the IDE defaults to x86, which means it runs as 32 bit no matter what.
32 bit apps need 32 bit odp/client. 64 bit apps need 64 bit odp/client.
The error you're getting usually means you have the wrong bits (32/64) of the Oracle client installed.
Assuming you have the wrong client bits installed, you could either
a) make the app run as the other bits by setting/clearing the 32BIT flag (also by using corflags.exe)
b) install the other bits of Oracle client software. a 32 bit home and a 64 bit home play rather nicely together for the most part, but you need to install them into separate homes.
Hope it helps,
Greg

Issues with different versions of Oracle.DataAccess.dll

Similar Messages

Maybe you are looking for