Skip to Main Content

ODP.NET

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

What to do about Oracle.ManagedDataAccess Mismatch?

superfreak3-JavaNetFeb 24 2017 — edited Mar 29 2017

Hi all,

We have a web app, as part of which we deploy Oracle.ManagedDataAccess.dll.  We will be supporting connection to an Oracle Db with out next release so we've begun testing.  What we've noticed is this...

If we install the application directly on the Oracle Db server we found that it just didn't work properly.  What we found in research and troubleshooting is that if we removed the Oracle.ManagedDataAccess assembly from the Global Assembly Cache, our app would then run properly.  So, we guessed there is some type of version mismatch at play.

We can't very much, nor should we, yank something out of the GAC just so our app would work.  Someone later figured out that if we Update the GAC assembly with the latest version of the .dll/assembly then our application would work.

So, I've been instructed to install the latest version into the GAC via our web app's installation.  I'm not so sure I like that idea.  I'm not a big fan of messing with 'stuff' set up as part of another application.  Would this be harmful?  If so does Oracle provide an update mechanism for this assembly that we could point users to before installing and running our app?

Or, is there another way we should be handling this altogether from our application?

Any help appreciated!!

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Apr 26 2017
Added on Feb 24 2017
4 comments
2,379 views