Oracle Oledb Provider Download

[Rubi Strycker]

Toconnect with the ORACLE we should be having ODBC or OLEDB provider. So i downloaded ODBC provider from market.qlik.com website but i couldn't find the OLEDB Provider for Qlikview. I tried to download it from oracle.com website but i couldn't find the exact driver and when i installed one OLEDB provider by downloading from the oracle website i didn't get that provider in Qlikview to connect with Oracle.

A system running Win 2008 with MS SQL 2008. Has a linked server (several, actually) referencing oracle databases. It uses the oracle OLEDB provider. This particular server has two oracle homes, one for an old client install and one for the OTG, to enable db links from oracle to MSSQL. (The gateway is not part if the current issue. Here we are working with MSSQL to Oracle.). Since there are two ORACLE_HOMEs, there was also a setting of local environment variable TNS_ADMIN, pointing to E:\app\oracle\tns_admin -- a directory created solely to be the target of tns_admin and hold tnsnames.ora and sqlnet.ora.

Now, because of a spate of server migrations coming down the pike, we decided to implement a single, central tns admin. We set tns_admin=\\myserver\myshare\tnsadmindir, where myserver is a file server. I know some will complain that oracle does not officially support this, but I've done it many, many times and it has never been an issue. Using both tnsping and sqlplus on the MSSQL server, we can confirm that they use the shared tns files. But when we opened MS SQL Management Studio and tested the linked server, it threw errors. Eventually we got it working after a full restart of the entire Win 2008 server. Unfortunately we did not keep careful notes of exactly where we stood and test results along the way, but the overall conclusion was that MSSQL / OLEDB for oracle was not relocating/re-reading tnsames on every request, but appeared to be caching some information.

But now things get really weird. Once we had everything working on the db server, We opened Management Studio from a desktop. From there, referencing the same SQL Server and its linked server, we got ora-12154. On the desktop machine, we could have tns_admin pointing to either a local directory or to the shared location at \\myserver\myshare\tnsadmindir. Didn't matter. The only way we could use one of the linked servers on the MSSQL machine, from another machine, is if the MSSQL machine is using a local tnsnames file.

Bottom line is both I and my MSSQL guy are at a loss. There appears to be something about the oledb provider that is handling the locating and use of the tns config files differently than any other client modules.

After some more research, I found the issue to my problem. In the readme.htm file that's included in the unzipped 64-bit providers folder, it explains that after you install the files through install.bat, you need to place the location you installed the files in the PATH variable for windows. For example, if you use the install.bat file to install the files at C:\Oracle, you need to place the paths "C:Oracle" and C:\Oracle\bin" in the PATH variable. You can find this variable by right-clicking on My computer and selecting Properties (for Windows Vista/7 users, it's right clicking on Computer then properties then advanced system settings). Click on the Advanced tab and click the Environment Variables button. In the Systems variables list, you'll find the PATH variable. I hope this helps someone else.... I worked on getting the oledb provider to work for days...

I want to access my oracle database through linked server in SQL server 2008 R2.But to create a new linked server I could not find OraOLEDB provider in SSMS. My SQL Server 2008 R2 and Oracle database are on the same system.

I am a newbie and I am currently doing my first SAP NW Identity Management 7.2 installation. At the moment, I am at the phase where I need to do the initial configuration, but I am stuck at the first step of Identity Center configuration wizard. The reason is that I am missing "Oracle provider for OLE DB" in the Data Link Properties. I know there are several discussions on the topic, which I went through and I did all the suggestions but none of them worked for me. What I have so far is :

I read that Oracle Provider for OLE DB is included as part of the Oracle installation, this is why I searched for ojdbc.jar files in both installation folders for the client(\oracle_client64x) and the database(\oracle). I found several ojdbc5.jar, ojdbc6.jar,ojdbc14.jar, etc. I started changing the path to each of these jdbc drivers in the the Java options in the Identity Center Management Console and testing to see if "Oracle provider for OLE DB" will appear in the Data Link Properties. Unfortunately, none of the steps above worked and now I am clueless how to solve this, so I really need help. I will really appreciate any advice or hint or a solution for my problem.

Thank you for your response. My first action was to install 32-bit client, as it was said in the guide. Unfortunately, I did not manage to see the correct provider in the data link properties, this is why I decided to remove the 32bit client as well as the 32bit JRE and replace them with their 64x bit equivelent. I will try installing the 32bit versions again and removing the client from the PATH and see what will happen.

You don't need to install anything for MS OLE DB Provider for Oracle, please check ODBC Data Source Administrator (odbcad32.exe). You should see the driver listed there as this comes with Windows by default. In you case you need the Oracle Client to use "Oracle Thin Driver". As Matt says please use 32 bit instead.

generally this issue derives from the Oracle client installation on the machine. I have seen somes issues running oracle client version 11.2.0.3 however 11.2.0.2 should work. Probably try uninstall client and reinstall and see if this helps.

With the 11.2.0.3 Version of the oracle client there is an issue, that the installer does not register the OLE driver correctly in windows. There are patches to resolve this problem. Or you can run "C:\Windows\SysWOW64\regsvr32 \Client32\bin\OraOLEDB11.dll".

Linked servers with the Oracle Provider for OLEDB on RDS for SQL Server lets you access external datasources on an Oracle database. You can read data from remote Oracle data sources and runcommands against remote Oracle database servers outside of your RDS for SQL Server DB instance. Usinglinked servers with Oracle OLEDB, you can:

Perform a reboot of the RDS for SQL Server DB instance after turning on, turning off, or modifyingthe OLEDB_ORACLE option in your option group. The option groupstatus displays pending_reboot for these events and isrequired.

Distributed transactions (XA) are supported. To activate distributed transactions, turnon the MSDTC option in the Option Group for your DB instance andmake sure XA transactions are turned on. For more information, see Support for Microsoft Distributed Transaction Coordinator in RDS for SQL Server.

To work with linked servers with Oracle, create an option group or modify an option groupthat corresponds to the SQL Server edition and version of the DB instance that youplan to use. To complete this procedure, use the AWS Management Console or the AWS CLI.

You can view and change the properties of the OLEDB provider. Only the masteruser can perform this task. All linked servers for Oracle that are created on the DBinstance use the same properties of that OLEDB provider. Call thesp_MSset_oledb_prop stored procedure to change the properties of theOLEDB provider.

You can view and change the properties of the OLEDB driver when creating a linked server forOracle. Only the master user can perform this task. Driver propertiesdefine how the OLEDB driver handles data when working with a remote Oracle data source.Driver properties are specific to each Oracle linked server created on the DB instance.Call the master.dbo.sp_addlinkedserver stored procedure to change theproperties of the OLEDB driver.

We have two SQL 64-bit clusters in our organization: a four-node productioncluster and a two-node dev/test cluster. We recently migrated a database fromSQL that relied on an Oracle linked server for some of it's computations. No big deal, right? Install the Oracle client software and create the linkedserver just like in the other SQL version right? Be sure to repeat the processon both nodes for failover-sake, right? Wrong. In the case of 64-bitSQL instances we have a few extra steps we need to take to get an Oracle linkedserver configured and working properly.

64-bit computing is coming of age. In most cases, our installation andconfiguration processes do not change from 32-bit to 64-bit: setting up logins,creating SQL Agent jobs; nothing inherently different there. Inconsistenciesdo exist however. Take for example linked servers - more specifically linkedservers to Oracle databases. In 32-bit environments we simply install theOracle client software, create the linked server, add remote logins and move onto the next project. In the 64-bit world the process is slightly more difficult- and in the case of one critical step it impacts any existing users on the instance!

I will leave it up to you to secure the software by either download from theirsite or media available via any licensing agreements you may have with Oracle. The important steps are outlined below. You only need the barest install ofthe client. Simply go ahead and select the InstantClient option from the openingdialog form and click Next.

The following screens simply require you to click Next when enabled. Theseare in place to present the internal checks and summaries of work to be completedonce you accept the install parameters. Proceed through the screens, clickInstall, and then Finish once the installation is complete.

Once you have an installed 64-bit Oracle Home you can proceed with installingthe ODAC drivers for a 64-bit environment. The OraOLEDB.Oracle driver installedin this step is what you need to set up your linked server. You'll find thesetup.exe for this installation located in the unzipped Install folder. Istrongly suggest you review your previous installation of the client software viaselecting the Installed Products button. You want to verify that you havea valid 64-bit Oracle Home that you'll be installing against during this process. We would not be DBAs if we were not overly cautious. It's quite Darwinian: the brash and risky don't last long as Database Administrators.

3a8082e126