tag:blogger.com,1999:blog-5215551487816981140.post3079590491245539236..comments2024-01-23T06:10:31.184-08:00Comments on ORA-00001: Unique constraint violated: ODP.NET minimal, non-intrusive installMorten Bratenhttp://www.blogger.com/profile/12300886042835631690noreply@blogger.comBlogger10125tag:blogger.com,1999:blog-5215551487816981140.post-7128184834477118942013-03-10T05:39:39.875-07:002013-03-10T05:39:39.875-07:00@Anonymous: "my development environment does ...@Anonymous: "my development environment does not have any Oracle Client installed. I am just using the latest version of ODAC/ODP.NET with Visual Studio 2010"<br /><br />Unless you are using the ODP.NET "Managed Driver" (which is currently in Beta), you must always have an Oracle Client on any machine running (Unmanaged) ODP.NET. <br /><br />"What's the best practice for dealing with legacy applications that are accessing older versions of Oracle?"<br /><br />I suggest you leave them alone, and "sandbox" any new applications with their own set of assemblies, as described in this blog post.<br /><br /><br />"what do I need to do in order to upgrade to the version of Oracle that will support the Entity Framework while still supporting legacy apps?"<br /><br />I have no personal experience with Entity Framework, but as far as I can tell, the new ODP.NET Managed Driver will work with EF.<br /><br />http://www.oracle.com/technetwork/database/windows/downloads/odpmbetainstall-1696475.html<br /><br />As mentioned, the Managed Driver is still in beta, but you may want to look into it to simplify deployment of new apps:<br /><br />"ODP.NET, Managed Driver is 100% fully managed. Developers can deploy a single assembly, side by side with other ODP.NET versions easily in a deployment package smaller than 10 MB."<br /><br />http://www.oracle.com/technetwork/topics/dotnet/whatsnew/index.html<br /><br /><br />- MortenMorten Bratenhttps://www.blogger.com/profile/12300886042835631690noreply@blogger.comtag:blogger.com,1999:blog-5215551487816981140.post-72331672531232273362013-03-07T12:56:38.258-08:002013-03-07T12:56:38.258-08:00Currently our web applications are installed on Wi...Currently our web applications are installed on Windows 2003 Server, IIS 6.0. Yes, this seems like the dark ages...years behind. They have an older version of the Oracle Client on the machine (11.0.1). This version does not support Oracle.DataAccess 4.x. .NET Framework 4.0 is installed on the Windows 2003 server. This version also does not support the Entity Framework.<br /><br />However, my development environment does not have any Oracle Client installed. I am just using the latest version of ODAC/ODP.NET with Visual Studio 2010. I am able to create apps locally with the Entity Framework but unfortunately cannot get them to work on the server because there of the older Oracle Client on that machine. Also there are approx. 50 applications on that server that are accessing this old version of OracleDataAccess 2.116.0 with references hard coded in the web.config. What's the best practice for dealing with legacy applications that are accessing older versions of Oracle?<br /><br />In short, what do I need to do in order to upgrade to the version of Oracle that will support the Entity Framework while still supporting legacy apps? Do I go for an Oracle Client upgrade or I just merely get the latest version of ODAC/ODP.NET installed on that server? <br /><br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-5215551487816981140.post-34078630435825162612011-11-16T07:34:08.456-08:002011-11-16T07:34:08.456-08:00I tried the steps you gave and it works fine for w...I tried the steps you gave and it works fine for windows application.<br />when i tried for web (asp.net and iis7.5) its not working...<br /><br />Please guide!!Rahul Mehtahttps://www.blogger.com/profile/03025832260031267941noreply@blogger.comtag:blogger.com,1999:blog-5215551487816981140.post-29805032084076842482011-07-25T23:50:20.582-07:002011-07-25T23:50:20.582-07:00Hello,
I discovered a problem when using this app...Hello,<br /><br />I discovered a problem when using this approach on a computer with a newer version of ODP already installed.<br /><br />The GAC wins, and the newer Oracle.DataAccess.dll was loaded. The DllPath in config still has the final word as to where the native dll's should be loaded from. Thus there will be a mismatch between the managed and native dll's - and ODP won't work (an exception is raised).<br /><br />My solution is to avoid using the GAC. Problem is: the GAC always win! It can't be turned off. Solution is to remove the strong name from the bundled Oracle.DataAccess.dll - the GAC relies on strong naming.<br /><br />The strong name can be removed easily with a tool like Strong Name Remove. It is generally not recommended to do, but as long as you trust the dll, you shuld be fine.<br /><br />Strong Name Remove<br />http://www.codeproject.com/KB/security/StrongNameRemove20.aspxespennoreply@blogger.comtag:blogger.com,1999:blog-5215551487816981140.post-64086665584725542532010-12-23T19:55:01.595-08:002010-12-23T19:55:01.595-08:00Hi Michael,
It sounds like you don't have any...Hi Michael,<br /><br />It sounds like you don't have any Oracle installations on your server. This means that the global machine.config file won't get updated to have the oracle.dataaccess.client section registered.<br /><br />You can fix this by adding it to your web.config file.<br /><br /><configuration><br /> <configSections><br /> <section name="oracle.dataaccess.client" type="System.Data.Common.DbProviderConfigurationHandler, System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089"/><br /> </configSections><br /></configuration><br /><br />Hope that helps.<br />DavidDavidhttps://www.blogger.com/profile/10375807309514100505noreply@blogger.comtag:blogger.com,1999:blog-5215551487816981140.post-75611402068972910072010-10-26T07:55:21.934-07:002010-10-26T07:55:21.934-07:00Hi Morten!
I really lika your approach to this pr...Hi Morten! <br />I really lika your approach to this problem and I tried to follow your instructions, but failed when it came to the configuration part.<br />I am using .NET 4 and WPF.<br />I got an Exception saying:<br /><br />Unrecognized configuration section oracle.dataaccess.client<br /><br />Any ideas what I'm doing wrong.<br /><br />Thanks / MichaelAnonymoushttps://www.blogger.com/profile/07522725898696907890noreply@blogger.comtag:blogger.com,1999:blog-5215551487816981140.post-79584978170911637152010-10-15T04:06:22.461-07:002010-10-15T04:06:22.461-07:00@Jay: I see there is a file called "Oracle Da...@Jay: I see there is a file called "Oracle Database 11g Release 2 Client (11.2.0.1.0) for Microsoft Windows (x64)" on this page: http://www.oracle.com/technetwork/database/enterprise-edition/downloads/112010-win64soft-094461.html<br /><br />And the "64-bit Oracle10g Release 2 ODAC for Windows x64" is on this page: http://www.oracle.com/technetwork/database/windows/downloads/index-090165.html<br /><br />Both are first hits on a Google search for these terms, by the way... :-)Morten Bratenhttps://www.blogger.com/profile/12300886042835631690noreply@blogger.comtag:blogger.com,1999:blog-5215551487816981140.post-73381247847862361732010-10-14T13:55:04.775-07:002010-10-14T13:55:04.775-07:00Any idea if a 64-bit version of both the .NET and ...Any idea if a 64-bit version of both the .NET and Oracle Client libraries are available for 64-bit?Jayhttps://www.blogger.com/profile/00056998276522847403noreply@blogger.comtag:blogger.com,1999:blog-5215551487816981140.post-65930751382704406862010-02-12T04:52:48.594-08:002010-02-12T04:52:48.594-08:00@Mike: Thanks for the tip, this looks interesting....@Mike: Thanks for the tip, this looks interesting. While I am unlikely to throw out ODP.NET now, I will certainly evaluate your product when I have some free time.Morten Bratenhttps://www.blogger.com/profile/16506692325808919895noreply@blogger.comtag:blogger.com,1999:blog-5215551487816981140.post-8263275820327079872010-02-09T12:48:42.658-08:002010-02-09T12:48:42.658-08:00Hi Morten, after reading your blog entry, which is...Hi Morten, after reading your blog entry, which is interesting an informative, I thought I would reach out to you and see if you were aware of and had tested with the Connect for ADO.NET provider from Progress DataDirect? The Connect provider is 100% managed, meaning that you could skip the step of installing the 30-100MB Oracle client altogether. In addition, the Connect provider delivers better performance while using less memory and supports the Entity Framework.<br /><br />If you're interested in learning more, free copies of the Connect for ADO.NET provider are available for download at the DataDirect website (http://www.datadirect.com/products/net/net_for_oracle/index.ssp). I invite you to evaluate it and publish your thoughts on how it compares with the provider from ODP.NET<br /><br />Thank you,<br />Mike Frost<br />Progress DataDirectMike Frosthttps://www.blogger.com/profile/01123631001929963843noreply@blogger.com