Only 32-bit Oracle.DataAccess.dll

Similar Questions

• Not able to see the 64-bit oracle.dataaccess.dll of GAC

  Hello
  I installed the client of 11g oracle 64-bit with ODP.net and deployed Oracle.DataAccess.dll in the GAC (it is deployed on C:\Windows\Microsoft.NET\assembly\GAC_64\Oracle.DataAccess). But I'm not able to return this dll to a project in Visual Studio, it does not appear in the window "Add reference". Please help me solve this problem. My system is a 64-bit computer.
  
  I did not submit this problem in the 32-bit computer. In 32-bit computer, I installed the client 32-bit oracle 11g and deployed Oracle.DataAccess.dll in the GAC (it is deployed on C:\Windows\Microsoft.NET\assembly\GAC_32\Oracle.DataAccess). I could see this dll to the project in visual studio.
  
  
  
  Kind regards
  
  Kiran.

  Hello

  Do you mean the .net tab? I think the problem is u cant reference 64-bit dll like that, since the studio is a 32-bit application. We had the same problem and our solution was to install 32-bit odp.net on our 64-bit machines, and refer instead.

• How to refer to 64-bit Oracle.DataAccess.dll in VS2010?

  Hello!
  
  We installed the ODAC 64-bit 4.112.2.0 on our new developer computers. With the 32-bit version of the ODAC, we would do this option to add the oracle references: Add reference-> tab .NET and add Oracle.Web.dll and Oracle.DataAccess.dll. But after our transition to 64-bit files exist no more. We could do something like make a local reference (include the bin folder in project and place the files and point of reference to them for an example) but this does not seem like a good solution. Has anyone else experienced this problem and solved?
  
  /regards

  You need not reference on x 64 version. You can add the reference on x 86 version. If you want to run the VS project, you need x 86 version customer Oracle VS x 86 application.

  The two DLLS ODAC (x 86 and x 64) has the same signature. If you build the project with the option "any cpu" then right what ODP.NET version is used for execution.

• Oracle.Dataaccess.dll using unmanaged for 32 and 64 bit Winform application.

  Hello

  I am new to oracle ODP.

  I have a few questions about her.

  1. If I give the reference only and do not include gac Oracle.Dataaccess.dll (suppose 2.11.3.XX) in my project and the client system has the access.dll of oracle version 2.11.2.XX(or autres) then what happens?

  Be it use the 2.11.2.xx DLL to GAC or error.

  2. I need to create some app for 32 and 64-bit client then should I develop a version for two separate, or are there other alternatives (I can't use the managed oracle DLLS due to .net 2.0).

  I've already lost two days on managing versions of oracle as oci.dll ddll, oraop11s.dll etc.

  Please suggest any other alternative if you have

  Thank you

  I think that if you run an application on machine Win x 64 with AnyCPU, 64-bit .NET will be always charged. I don't think you can change this even if you try to load a 32-bit DLL. There may be a way, but I do not know myself.

  If you ODP.NET 11.2.0.3 on your system, I don't see why you need to install an earlier version of ODP.NET, such as 11.2.x

• Intermediate language of the oracle.dataaccess.dll version

  Is there an intermediate version of the oracle.dataaccess.dll that we can use to compile 64-bit applications using 32-bit computers?
  
  We develop our applications on x 32 and deploy on x 64 (it is strictly enforced by our Organization. This means that there is no option for execution of x 32 code on an x 64 server).
  
  The oracle.dataaccess.dll only comes in 2 versions from what I can tell; x 32 or x 64. This forces us to use x 64 build servers. We need the x 32 ODP installed on our machines to dev for the development and the x 64 ODP installed on the servers of x 64 compilation. Dev of 32-bit machines cannot compile an application with an x 64 native dll.
  
  Example:
  1. create a new class library.
  2. Add the oracle.dataaccess reference.
  3. change the platform target in the properties of the project to x 64.
  4 compile the application.
  5 examine the dll in the bin directory. (I used the reflector, but you can use the corflags util)
  
  The target platform for the class library is x 64. The target platform for the oracle.dataaccess.dll is x 86. Application will not work when you run it as x 64.
  
  ODP.NET is the only 3rd-party product .NET we use which doesn't seem to have an intermediate language dll, and so the only reason why we allocate and maintain separate x 64 build servers to compile our code for x 64 deployment.
  
  It's been a while since I looked into that, so I was wondering if there is a solution now.

  I guess the poster is after a fully managed version of the provider, but maybe not.

• Release of the ODAC 4 & 5 - Oracle.DataAccess.dll 4.112.3.0

  Has anyone else noticed that ODAC version 4 and 5 have the same 4.112.3.0 AssemblyVersion?

  Oracle (ODAC) for Windows data access components

  It took me a while to spot the problem.  I use Entity Framework 5 and hitting a machine with version 4.  He threw a completely misleading exception on the laundry.

  System.Reflection.TargetInvocationException: Exception was thrown by the target of a call. -> System.TypeInitializationException: the initializer for type for 'Oracle.DataAccess.Client.OracleConnectionStringBuilder' threw an exception. -> System.TypeInitializationException: the initializer for type for 'Oracle.DataAccess.Client.RegAndConfigRdr' threw an exception. ---> System.Configuration.ConfigurationErrorsException: MySchema.MyPackage.MyProcedure.RefCursorMetaData.CUROUT.Column.1 is not valid

  at Oracle.DataAccess.Client.RegAndConfigRdr.AddMetadataForRefCursor (String refCursorKey, String metadataInfo, Hashtable & schemaTable)

  to Oracle.DataAccess.Client.RegAndConfigRdr.RetrieveInfoFromConfig (NameValueCollection nvc, Hashtable & schemaTable, Boolean bIsCallFromODT)

  to Oracle.DataAccess.Client.RegAndConfigRdr... cctor()

  Since version 4 ODAC has been installed, the machine had Oracle.DataAccess.dll (4.112.3.0) in the GAC.  So, my application could not use my local copy of Oracle.DataAccess.dll (4.112.3.0) of version 5.

  There are problems with having the AssemblyVersion similarly for version 4 and 5.  Can we get an extra release with an updated version?

  There are two questions in your last post:

  (1) Oracle.DataAccess.dll versioning

  (2) DLL's Client Oracle unmanaged referenced by Oracle.DataAccess.dll

  The forum post you quote refers to the #2 problem.

  Problem #1, preferred the ODP.NET team is at version every single Oracle.DataAccess.dll version. We can not due to a conflict with the policy of general correction of Oracle. With the help of AssemblyInformationalVersionAttribute is the best compromise.

  If you have already downloaded an Oracle patch, you will notice the files share the same version number as other patches within a family group of patches Oracle. With each new group of patches or major version, Oracle.DataAccess, dll can then increase its version, just like every other DLL of Oracle.

• Problem with access to the Oracle.DataAccess.dll in the application folder

  Hi all.
  http://StackOverflow.com/questions/3935808/how-can-i-deploy-a-NET-application-that-uses-ODAC-without-installing-the-whole
  
  Issue. It works with 11g? I don't want to install the whole ODAC on client computers
  
  who is Ellen
  
  Published by: 902645 on 21.01.2012 14:20
  
  Published by: 902645 on 22.01.2012 11:39

  Download the 11g ODAC Xcopy installation. It is around 50 MB compressed upward and you offer the minimum installation size possible. It is the smallest possible at this moment production which is taken in charge by Oracle. There is a 32-bit version and 64-bit, depending on the version of your .NET Framework.

  Be on the lookout for the beta of managed provider ODP.NET fate soon. Which will further reduce the size.

• Could not load file or assembly Oracle.DataAccess

  I have a VB.Net application that worked fine on a Windows 2003 32-bit secure server for many months. Exe has already been compiled on a 32-bit Vista machine and then the exe has been copied to the server. Today, I was delivered a new 64-bit Windows 7 computer. I installed the 32 bit ODAC 11.2.0 and added a reference to Oracle.DataAccess.dll in Visual Studio 2010. The program compiles and runs normally on my 64 bit Windows 7 computer. In Visual Studio 2010, I 'CPU target' defined on x 86.
  
  When I copy the exe on the 32-bit server, the following error message is returned: "could not load file or assembly Oracle.DataAccess.
  
  The server has two facilities of ODAC 32bits, 11.2.0.2 and 10.2.0. Why does this work?
  
  Published by: Francis November 1, 2012 13:02

  It's been awhile that I'm on version issues, so I'm a little fuzzy, but I think the problem here is that you develop against a newer version (even if only a little) of the Assembly, that which exists on the deployment target computer. There are policy files to redirect the old versions of the assembly to the latest version installed on the computer, but it does not work to redirect a newer version (i.e. 2.112.2.0) downwards (i.e. 2.112.1.0).

• Could not load file or assembly ' Oracle.DataAccess error on server

  I construisent.net application on my Machine local Windows 7 and I have the 32-bit Microsoft installed on my machine that works well with VS 2010.
  
  I placed it on the server and when I open the page that accesses data from Oracle, I get the error below. The server and my local computer have the Oracle.DataAccess
  DLL installed and both have the same public token 89b483f429c47342. I changed the CPU of Any CPU target to x 86 and published a Release version of my project to the server.
  
  Why I get the below error?
  
  ==========================================================================================================
  Could not load file or assembly 'Oracle.DataAccess, Version = 4.112.2.0, Culture = neutral, PublicKeyToken = 89b483f429c47342' or one of its dependencies. The system cannot find the specified file.
  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 its origin in the code.
  
  Exception details: System.IO.FileNotFoundException: could not load file or Assembly 'Oracle.DataAccess, Version = 4.112.2.0, Culture = neutral, PublicKeyToken = 89b483f429c47342' or one of its dependencies. The system cannot find the specified file.
  
  Source error:
  
  An unhandled exception is generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception below stack trace.
  
  Assembly Load Trace: the following information may be helpful to determine why the assembly 'Oracle.DataAccess, Version = 4.112.2.0, Culture = neutral, PublicKeyToken = 89b483f429c47342' could not be loaded.
  
  
  WRN: Assembly binding logging is disabled.
  To enable the failure of link Assembly record, set the registry value [HKLM\Software\Microsoft\Fusion! EnableLog] (DWORD) to 1.
  Note: There is some pain associated with a record of failure performance link Assembly.
  To disable this feature, remove the registry value [HKLM\Software\Microsoft\Fusion! EnableLog].
  
  
  
  Stack trace:
  
  
  [FileNotFoundException: could not load file or assembly 'Oracle.DataAccess, Version = 4.112.2.0, Culture = neutral, PublicKeyToken = 89b483f429c47342' or one of its dependencies.] The system does not find the specified file].
  antac.dashboard.Page_Load (Object sender, EventArgs e) in C:\Users\George\Documents\Visual Studio 2010\Projects\antac\antac\dashboard.aspx.cs:92
  System.Web.Util.CalliHelper.EventArgFunctionCaller (fp IntPtr, Object o, object t, e As EventArgs) + 25
  System.Web.UI.Control.LoadRecursive () + 71
  System.Web.UI.Page.ProcessRequestMain (Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) + 3048
  
  
  
  
  --------------------------------------------------------------------------------
  Version information: Microsoft .NET Framework Version: 4.0.30319; ASP.NET Version: 4.0.30319.1

  This isn't the only DLL that is required. You must fully install ODP.NET on the server.

• C# Oracle.DataAccess calling a stored procedure with a date parameter throws formatexception

  C# Oracle.DataAccess CommandType.StoredProcedure is OracleDbType. Date

  I can't get my code to call an oracle procedure that has an order date.

  I receive a System.FormatException occurred in Oracle.DataAccess.dll

  I tried to assign the param. Value = DateTime and also tried assigning as a string formatted with no luck.

  What is the magic formula, I need to call this function?

  Here is a code snippet:

  OracleCommand cmd = new OracleCommand();

  cmd connection group appConn;.

  cmd.CommandText = "mypackage.myprocedure";

  cmd.CommandType = CommandType.StoredProcedure;

  Param = new OracleParameter ("iDateParamter", OracleDbType.Date, ParameterDirection.Input);

  Param. Value = "August 31, 2015."

  Here are other formats I' tried... ved param. Value = myDateValue.ToString ("dd - MMM-yyyy"). ToUpper(); (/ / "MM/dd/yyyy"); 'YYYY-MM-dd'); "MM-dd-yyyy");

  cmd. Parameters.Add (param);

              BindByName. cmd = true;

              cmd ExecuteNonQuery());

  Shame on me..., you can close this message

  It was not for the error on my date field, I had another parameter that has been attributed to a string instead of an integer.

  For the record, this has worked well for me:

  Param = new OracleParameter ("iActvyPerDate", OracleDbType.Date, ParameterDirection.Input);

  Param. Value = li. ActvyPerDate.ToString ("dd-MMM-yyyy"). ToUpper();

• Change of version of Oracle.DataAccess?

  Hello.
  
  In a standard client 11 GR 2 installation, ODP.net comes with the 2.112.1.0 version. When you install the developer tools for VS, the installer replaces this version with 2.112.1.1.
  
  When an application is built and then given to someone who doesn't have the developer tools, it has here a problem of version and the application fails to load the assembly (and therefore does not work).
  
  So my question is this - why the developer tools contain a different version of Oracle.DataAccess.dll, and what is the best way to get around that?
  
  Thank you.

  Have you already checked the FAQ? You can target the previous versions of ODP using a newer ODT...
  http://www.Oracle.com/technology/tech/dotnet/Col/odt_faq.html#olderodpnet

  Greg

• Oracle.DataAccess 32 bit and x 64 with a build? There is no corresponding version?

  We used Oracle.DataAccess to generate a .net assembly. version has been 10.1.0.400. I can't seem to find the x 64 native install for this 10.1.0.400 version we are running IIS in 64-bit mode. so I need an x 64 native bit Assembly.
  
  We deploy our .net assembly for a 32-bit and x 64 bit machines. so I need to install a version of Oracle.DataAccess with the same 32-bit and x 64 bit version.
  
  I can't find a version in common 32-bit and x 64 bit.
  
  It seems that the closer, I can get is 2.102.3.2 for x 64 and 2.102.2.20
  
  I have no problem re-construction of the Assembly, and as long as I can get the same fix on both 32 bit and x 64 bit version in the GAC, it should work very well. help, where can I find a corresponding 32-bit and x 64 bit version to install?

  Hello

  Yes, you must have a support account in order to login to metalink and get the fixes.

  Part of the ODP.NET installation includes installation of policy files in the GAC which redirect use the latest version installed, so I think you should be fine compilation on 10.2.0.2.21 x 86 (for example) and the distribution to the 10.2.0.3.02 x 64. You must compile a version<= the="" version="" you="" want="" to="" be="" able="" to="" run="" it="" on="">

  Greg

• There are 2 versions of Oracle.DataAccess on the system with the same public token

  Hello
  can someone please explain this
  1 Oracle.DataAccess... x 86... 2.112.1.0... 89b483f429c47342
  2 Oracle.DataAccess... x 86... 2.112.2.0... 89b483f429c47342
  
  I have a reference in Visual Studio to one of these DLLs. My question:
  (1) what are the differences?
  2. what assembly is loaded by my application?
  
  greetings and thanks
  Ellen

  Hi Ellen,.

  All versions of the ODP assemblies have the same public key token. The difference is your case is you two versions (2.112.1.0 and 2.112.2.0) installed, and the difference between new features, bug fixes, etc.

  ODP also installs policy files by default that can come into play here, but it depends on which version you installed last. If you have installed 2.112.2.0 last, then the policy file would automatically redirect apps looking for 2.112.1.0 to use 2.112.2.0 instead.

  If you have installed 2.112.1.0 last, then the file 2.112 strategy would only redirect apps more 2.112.1.0 to use 2.112.1.0.

  If you're wondering how to determine what your application assembly IS actually responsible, the best way is via a tool like Process Explorer, which will allow that see you what libraries are loaded into a process.

  Greg

• Oracle.DataAccess 2.112.1.0 - connection Pool problem

  Hello
  
  Oracle.DataAccess 2.112.1.0 is having problem of connection pool. The no. TCP to Oracle database connections continue to increase until the session of the server to run out of limit. My application created connections, use them, close them and dispose of them properly. When using previous Oracle.DataAccess 2.111.6.20, no. of the TCP connections do not increase.
  
  My database connection string has "Min Pool Size = 3 and Max Pool Size = 150".
  With 2.111.6.20 version, TCP connection remains at 3.
  With 2.112.1.0, TCP connection continue to increase for all 5 minutes. I tried to disable Auto Tuning, but still can not prevent connections of the increase.
  
  Later today, I downloaded Oracle.DataAccess 2.112.1.2 (it comes with ODAC 11.2.0.1.2) and test again, the problem is solved... no more connection increases... but it's only for 32-bit Windows.
  
  Unfortunately, there is no Oracle.DataAccess 2.112.1.2 for 64-bit Windows Server 2008.
  
  I know how I can solve this problem on 64-bit windows installed with Oracle 11 g R2 client, which comes with Oracle.DataAccess 2.112.1.0, which has serious problems... (according to this 11.2 ODP.NET causing test failures runner )
  
  Thank you very much for your time and your answers!
  
  Published by: user1502907 on Sep / 04/2010 23:01

  Hello

  The only thing that POPs in the description of your problem is that connections are increased every 5 minutes. Are you sure its every 5 minutes and not 3 minutes, which is the interval of time used by the installation of connection pool to perform maintenance on connection pool. If this happens even when the application is inactive then you could if filed against 11.2.0.1.0 and fixed 11.2.0.1.2 known issue run in what follows.

  Bug 9711600 - CONNECTIONS beyond MAX POOL SIZE INCREASE EVERY 3 MINUTES

  It is specific to using the CommandBehavior.CloseConnection option when calling execute reader. You are using this option and then also close the connection in code before closing the datareader object, if so you can be hitting this bug. You can also generate a trace ODP at level 15 of the behavior and if you see a negative mix counties, it's also a diagnosis that points to this bug.

  This problem is fixed in 11.2.0.1.0 Patch 3 or later version for x 64. If you support, I recommend that you open a service request to check if this is your problem and if a set of patch can help you.

  Concerning
  Jenny B.

• Could not load file or assembly ' Oracle.DataAccess, Version = 4.112.4.0?

  Hi guys,.

  As the title says "could not load file or assembly ' Oracle.DataAccess, Version = 4.112.4.0. The program crashes when I try to run the following code.

  OracleConnection Con = new OracleConnection (ConfigurationManager.ConnectionStrings ["ConnectionString1"]. (ToString());

  SqlCmd OracleCommand = new OracleCommand();

  OracleDataReader dr;

  sqlCmd.Connection = Con;

  Con.Open ();

  sqlCmd.CommandText = "INSERT INTO ADFG values (0, 0, 0, ' ', sysdate);

  sqlCmd.ExecuteNonQuery ();

  sqlCmd.Clone ();

  MessageBox.Show ("inserted record!");

  Any help would be appreciated.

  Hello

  This occurs generally when there is an inconsistency in the application of ILO version and the version of ODP.NET bits.

  If you compiled/built the application with Any CPU option, please modify X 86 or X 64 and build and run the code.

  Thanks and greetings

  Vincent

  Support of Oracle