This content has been marked as final. Show 6 replies
I don't run Oracle server locally just avoid stuff like this, but since you installed an x64 server while having the application running in x86 mode, one potential issue is that the binding redirect you were using is no longer working because it's set for the 64 bit version instead. You don't have 188.8.131.52 on the machine at all, so try deleting that reference and pointing directly at your ODAC version.
Alternately reconfigure the project to compile for x64 and disable 32 bit mode in IIS, then use the 64 bit client.
Thanks for the replay Tridus.
Normally I install 11gR2 x64 then install the ODAC afterwards. Then everything works on my application, but when I do that I have issues with logging in using windows authentication at the command prompt other items like that.
the assembly is still present in the C:\Windows\assembly directory...
Oracle.DataAccess 184.108.40.206 x86
Isn't there anyway to get the applications to see this assembly in the GAC? since it is truly there?
It should be. Have you tried removing the reference your application has now and re-adding it for the version you want to use?
Alternately if it's something you can use in your situation, have you tried using the managed provider beta? That's just a single assembly that doesn't rely on Oracle clients at all and really solves a lot of this type of stuff.
Well since we have a bunch of applications that all use the same version and production uses that same version, I was trying not to modify the reference.
If I install 11gR2 then install the ODAC everything works fine on the applications, but I can't login with the operating system credentials and I can't use OEM.
Yeah that sounds like the classic case of multiple Oracle clients on the same system not playing nice. I've found it easier to just avoid it whenever possible, so I can't be of much help troubleshooting it. Sorry.
(If you have a chance though, try the managed provider beta for your client software instead. It's shaping up to be a great solution to this type of thing.)
Sorry , but I did know where to place my question, so I decided to place it here , because this topic is closer one to my question.
If I use Oracle Express Edition (11g) in developping my application , and I would like to use ODAC driver for .Net Entity framework in order to access Oracle DB from .Net application, have I pay for ODAC driver or not in this case?
I did not find any information about this.