Oracle.dataaccess.dll Download 64-bit

[Heberto Calderon]

Iam using ODP.NET in my asp.net project in order for the application to talk to oracle 11 g Express on Windows 2008 server (32 bit). While on development machine I had Windows 7 (32 bit). I installed Windows 8 (64 bit) on the development machine and tried to run the application from visual studio 2012, It gave the error 'Could not load file or assembly 'Oracle.DataAccess''. After a little search I realized that I have to install ODP.NET (64 bit) in order to use it on 64-bit machine, so I uninstalled the 32 bit version and installed 64-bit ODP.NET. Removed the reference to old Oracle.DataAccess but still facing the same issue. Am I missing something??

To install ODP.NET, I use 64bit ODAC

After installing it, to check if Oracle.DataAccess 64bit assembly is properly installed go to folder: c:\Windows\Microsoft.NET\assembly\GAC_64 and check if Oracle.DataAccess folder is present there.

In the folder there should be a subfolder containing the version of Oracle.DataAccess dll you are using.

In Visual Studio, you must add the reference by looking in Assemblies->Extensions (not by using Browse)

Also check your build configuration in Visual Studio to make sure that your application's active solution platform is 64 bit.

To run your website, you must use IIS since visual studio's development server only run in 32 bit mode.

In IIS application pool, set your application to run in 64 bit. (The setting is in advanced settings)

The bit-ness of the machine does not matter - the bit-ness of the hosting application does. The development web server included with Visual Studio is 32 bit, consequently you'd need to install the 32 bit version of odp.net. You could run it in IIS instead if you wanted to test with the 64 bit version. I install both.

In this case, I'd guess the problem is more likely to be version number -your application originally referenced a different version than the one you've installed. The simple thing to do is delete/re-add the reference to the newly installed Oracle.DataAccess.dll. However the fact that you have to do this somewhat indicates that you are installing the full client instead of just the ODP.net install. For some reason (other than the oracle universal installer being a total hunk of junk), the full client does not include the publisher policy (which would redirect the reference), but the odp.net install does.

To use data from an Oracle database in your report, you must have a dataset that's based on a report data source of type Oracle. This built-in data source type uses the Oracle Data Provider directly and requires an Oracle client software component. This article explains how to download and install drivers for Reporting Services, Power BI Report Server, Report Builder, and Power BI Desktop.

The following commands that use Oracle's OraProvCfg.exe tool to register Oracle's Managed and Unmanaged ODP.NET drivers are provided as examples for use with the above Microsoft products. For the configuration of the ODP.NET drivers specific to your environment, you may need to contact Oracle support or reference Oracle's documentation for Configuring Oracle Data Provider for .NET.

On the Oracle download site, install the Oracle 64-bit ODAC Oracle Universal Installer (OUI). You only need the following steps when using Oracle ODAC drivers 12.2 and later. Otherwise, they install by default to a non-machine-wide configuration for a new Oracle home installation. These steps assume you've installed the ODAC 18.x files to the c:\oracle64 folder.

Microsoft Report Builder uses Managed ODP.NET for authoring paginated (RDL) reports. You only need the following steps when using Oracle ODAC drivers 12.2 and later. Otherwise, they install by default to a non-machine-wide configuration for a new Oracle home installation. These steps assume you've installed the ODAC 18.x files to the c:\oracle32 folder where Microsoft Report Builder is installed. Follow these steps to register Managed ODP.NET:

Power BI Report Builder uses Managed ODP.NET for authoring paginated (RDL) reports. You only need the following steps when using Oracle ODAC drivers 12.2 and later. Otherwise, they install by default to a non-machine-wide configuration for a new Oracle home installation. These steps assume you've installed the ODAC 18.x files to the c:\oracle64 folder where Power BI Report Builder is installed. Follow these steps to register Managed ODP.NET:

Power BI Desktop uses Unmanaged ODP.NET for authoring Power BI reports. You only need the following steps when using Oracle ODAC drivers 12.2 and later. Otherwise, they install by default to a non-machine-wide configuration for a new Oracle home installation. These steps assume you've installed the ODAC 18.x files to the c:\oracle64 folder for 64-bit Power BI Desktop or the c:\oracle32 folder for 32-bit Power BI Desktop. Follow these steps to register Unmanaged ODP.NET:

Contact your database administrator for connection information and for the credentials to use to connect to the data source. The following connection string example specifies an Oracle database on the server named "Oracle18" using Unicode. The server name must match what is defined in the Tnsnames.ora configuration file as the Oracle server instance name.

To create a dataset, you can either select a stored procedure from a drop-down list or create an SQL query. To build a query, you must use the text-based query designer. For more information, see Text-based Query Designer User Interface (Report Builder).

If the query includes query variables, corresponding report parameters are automatically generated. Named parameters are supported by this extension. For Oracle version 9 or later, multivalue parameters are supported.

Report parameters are created with default property values that you might need to modify. For example, each report parameter is data type Text. After the report parameters are created, you might have to change default values. For more information, see Report Parameters (Report Builder and Report Designer).

Before you can connect an Oracle data source, the system administrator must have installed the version of the .NET Data Provider for Oracle that supports retrieving data from the Oracle database. This data provider must be installed on the same computer as Report Builder and also on the report server.

I log on to it with an account that has elevated admin privileges and also an account that does not. Before the hard drive crash and OS upgrade, I was successfully using TOAD to connect to local 11g and remote 10g & 11g databases.

pasting in a screenshot showing what TOAD's seeing for my oracle_homes. The first one I don't know how it is finding it. The second one is what I'm passing in. You can see that the bin dir is in the PATH. The oci.dll is in the bin dir.

You must use 32-bit client with that version of toad. It will not see the 64-bit home. If you use the instant client make sure that TNS_ADMIN env var is set

and make sure that your instant client home dir in first on you window PATH env var

You may have issues with the 64-bit ODAC drivers not connecting to the EFTDB when attempting to analyze the database for its upgrade. This happens because they do not havethe option to install the ODAC components to GAC and register them in machine config (www.oracle.com section Machine-Wide Configuration).

Look in c:\Windows\Microsoft.NET\Framework64\ to see the correct versions for .net. There should be a v4.0.xxxx folder. Use this string as frameworkversion, as shown in above example. This will register the oracle ado.net provider in machine configuration and allow the EFT installer to use it.

The Oracle Data Access Components (ODAC) package is required on the Meridium APM Application Server machine so that it can connect to the Oracle database on the Database Server machine. The following ODAC software is required on the Application Server:

Oracle Data Provider for .NET (ODP.NET): A database connectivity layer for use with .NET applications, like Meridium APM. You can use these instructions to install both the required 32-bit and 64-bit versions.

Read the 32-bit Post Installation information, and complete any necessary steps, as indicated in the command prompt window. For example, you may need to change the NLS_LANG to a value that is compatible with the Database Server. If you are asked to restart the machine, do not do so until after the 64-bit version is installed.

Read the 64-bit Post Installation information, and complete any necessary steps, as indicated in the command prompt window. For example, you may need to change the NLS_LANG to a value that is compatible with the Database Server.

I have an SSAS Project where the Data Source is an Oracle 10g database and OLAP is running on a 64-bit server. I have installed and tried the Oracle 10g drivers but found that to be a miserable experience (the drivers fail because of the '(' in the path to the executable for SSMS and BIDS, gotta love Oracle for caring about their customers and wanting to fix that little gotcha!!!), I have installed the ODAC 11g drivers (Oracle Data Access Components), and can connect to my Oracle server with the 'Test Connection' button in the DS configuration, but when I try to process a Dimension, I get connection errors - "Unknown User Name or Bad Password", even though Im using the same User / Pswd..

You will simply need to make sure you have the 64bit Oracle drivers installed on the server and on your workstation where you are doing your development the 32bit Oracle drivers. As you stated BIDS (Visual Studio) is only a 32bit application. Same thing in regards to driver setup if you are using SSIS (64bit on server and 32bit on workstation).

You the option to save the password and you shouldn't have any issues. Currently using Oracle 11g with SSAS 2008 on Windows Server 2008 with no issues (upgraded from SSAS 2005 and Windows Server 2003).

I am facing the same problem when I try to process a dimension. But I am using Oracle 10g client. I have installed both 32bit and 64bit Oracle 10g clients on the server. After developing the SSAS project (on the server itself), I have deployed it on to the SSAS server without processing using Deployment wizard. Then I have created an SSIS package to process the dimension in that SSAS database. Then an SQL Agent job to execute this SSIS package. But, when I run this job, I am still getting the same "Logon failure: unknown user name or bad password" error.

3a8082e126