Linked Server SQL 2008 64 bit Windows Server 2008 64 bit

Hello there,
I'm trying to access my customers Oracle database with a SQL Linked Server. The error I get is:
Cannot create an instance of OLE DB provider "OraOLEDB.Oracle" for linked server...
I did the following steps:
1. Installed Oracle client 10g with a custom installation and selected everything.
2. Created a tnsnames.ora
dev =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = dijkora01)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = dev)
3. Tested this with tnsping dev, which said that the connection is OK.
4. Activated 'Allow inprocess' for my OraOLEDB.Oracle provider for the linked servers in my SQL Server Management Studio.
5. Created a new linked server with:
Linked Server: IAP
Provider: Oracle Provider for OLE DB
Product name: Oracle
Data source: dev
In the security tab I activated 'Be made using this security context'. When I now press 'OK' I get the above error message.
Can someone help me with this?

Windows 7 Enterprise 32-Bit
Installed the version 12 for 32 bit ODAC and it worked. The key is to Install as Administrator once it is unzipped.
Was able to set up Listener then
Was able to set up ODBC using the ODAC. Connect MS Access 2010 to the Oracle views.
Then, tried to install the 64 Bit onto Windows 2008 Server.
It locked up during installation both times.
Installed ODAC without an error.
However, the ODBC setup will not provide a list of the servers in the ODBC TNS Service Name listbox for Server 2008.
In Windows 7, it populates the TNS Service Name.
The list box in Windows 2008 is empty.
Do you know what would cause that?
The .ORA file scrips look the same on Windows 2008 as they do on Windows 7 except it does not have the (server = Dedicated) argument.
Thanks.

Similar Messages

Distributed transaction using linked server not working in SQL Server 2008 64 bit

Hi. I have had an issue trying to get distributed transactions to work in SQL Server 2008 using a linked server. The error message I get is
OLE DB provider "SQLNCLI10" for linked server "pod1" returned message "No transaction is active.".
Msg 7391, Level 16, State 2, Line 3
The operation could not be performed because OLE DB provider "SQLNCLI10" for linked server "pod1" was unable to begin a distributed transaction.
My Environment:
Windows Server 2008 Enterprise 64 bit, SQL Server 2008 Enterprise 64 bit
Problem occurs with multiple different builds of SQL Server 2008 - I have been able to reproduce the problem with 10.0.1600.0, 10.0.1779.0 (CU 2), as well as 10.0.2531 (SP1)
I am aware that other people have had this issue and have reviewed all existing posts. I have verified that the MSDTC is configured correctly on both machines. I have also used DTCTester to verify that DTC is working correctly on all machines in question.
None of the mentioned resolutions has solved this problem for me.
I am not seeing this problem occur on my 32 bit test machines - it is only occurring if at least one of the two machines is 64 bit.

Hi All,
I realise that this topic may be a little bit out-of-date but if someone gets here from some search engine trying to find a solution for DTC problems, this MAY be useful.
So... I recently had the same issue, tried all the approaches described in KB and other articles, but it didn't help. Because my task to solve this was not of the highest priority I forgot about it for some time.
Today I was troubleshooting some other issue and, by accident discovered source of that first problem:
In the EventViewer I found Error entry logged by MSDTC saying:
"The local MS DTC detected that the MS DTC on vm-server1 (other machine name that also runs DTC - my comment) has the same unique identity as the local MS DTC. This means that the two MS DTC will not be able to communicate
with each other. This problem typically occurs if one of the systems were cloned using unsupported cloning tools. MS DTC requires that the systems be cloned using supported cloning tools such as SYSPREP. Running 'msdtc -uninstall' and then 'msdtc -install'
from the command prompt will fix the problem. Note: Running 'msdtc -uninstall' will result in the system losing all MS DTC configuration information."
So I followed suggestion and run:
msdtc -uninstall
msdtc -install
This solved my problems with DTC. Hope it will help someone.
Piotr

SQL Developer / JDK On Windows Server 2008 64 bit R2

Does anyone have the recipe to fix the annoying message: "Cannot find a J2SE installed at path: C:\Program Files\Java\jre6"? I get the same message, when trying to set up and run SQL Developer on a Windows 2008 server with SQL Developer 32 bit, Java 1.6 and Java 1.7 32 bit, and now trying with SQL Developer 64-bit with JDK 64 bit. Thank-you.

SQL Developer requires a JDK, not a JRE. When you are asked to select the path you need to into "C:\program files\jdk1.6.0_35\bin" (or whatever) rather the the jre6 directory.
If you are using SQLDeveloper 3.2, then you need to be using the latest JDK 1.6 release. The bittage of the JDK should match your SQL Developer (and your oracle client if you are using one).

Sharepoint 2007 and SQL 2008 SP3 on Windows Server 2008 Enterprise SP2 (64-bit)

Is there any documentation we can check if SQL 2008 SP3 is compatible with Sharepoint 2007 SP2 or SP3? Both Sharepoint and SQL servers are running on separate Virtual machines (Windows Server 2008 Enterprise SP2(64-bit)). Currently DB is running on
SQL server 2008 SP2, and we would like to have SP3 loaded on it, but want to find if there is any compatibility issue?
Thanks in advance!
mh

I'm not aware of any known issues with SQL Server 2008 SP3 and SharePoint 2007. I did a quick check and saw one person reporting an issue with their Central Admin site after applying the SQL Server update, but that's it.
With that being said, I would strongly encourage you to test out the application of that SQL Server service pack in a non-production environment well before you apply it in production. There is always a chance that your environment has something set up in
it that would cause an unexpected issue, and the best way to get an idea of whether or not an issue exists is by doing it somewhere else first before you do it in prod.
John
MCITP and MCTS: SharePoint, Virtualization, Project Server 2007
My books on Amazon: The SharePoint 2010 Disaster Recovery Guide and
The SharePoint 2007 Disaster Recovery Guide.
My blog: My Central Admin.

DB Link to SQL Server (11gR2 64-bit Windows 7)

Without going into all the gruesome details, it is mostly straightforward to set up a DB Link to SQL Server from an Oracle 10 instance on 32 bit Windows 7. However I simply cannot get the link to work on 11gR2. I tried the simplistic ds4odbc interface and the more complex SQL Server gateway. Nothing works. The connection always times out. Has anyone been able to create a SQL Server DB link from 11gR2 on Windows 7? (The Oracle instance is 32 bit. The OS is 64 bit). I know Win7 is unsupported at present.
Edited by: user2190753 on Oct 14, 2010 4:51 PM

Hi,
first of all you need to check the ODBC connectivity between Oracle and SQL Server and the Data source,try to load data from oracle to Sql Server to check the ODBC connection is working properly and then create database link from sql server to oracle ,you can create stored procedures in SQL server to get data from Oracle to sql server or Oracle PL/SQL Packages to data from sql server to Oracle Database
To setup ODBC and datasource
see this link
http://www.databasejournal.com/features/oracle/article.php/3442661/Making-a-Connection-from-Oracle-to-SQL-Server.htm
and then create link server in sql server after you test connenction with oracle

SQL linked server twice as slow in Windows 7 as XP

We have a transaction based synchronization from SQL Server to Oracle, i.e. both must commit or rollback in one distributed transaction. We achieved this using MSSQL Linked Server using the Oracle Provider for OLE DB and triggers running openquery for speed.
The SQL Sever 2008 was on XP (doesn't need a server) and the Oracle 11g was on Red Hat 5EL. In testing from the first trigger firing to the last trigger finishing, a save test took ~11 Seconds, not perfect but acceptable. Yet when we moved to Windows 7 this time rose to 19 Seconds.
We contacted Microsoft support and they seen to thing it is a multi platform issue. So to prove them wrong we created an oracle DB on a Windows 7 system and ran the tests again, same issue. They will not look into the issue without us paying for premium support at an hourly rate, due to the Oracle DB. So we created one more test environment to try to prove it was a Microsoft issue and not an Oracle driver issue we created 2 SQL servers and ran tests to see if we got the same issue. We got the following results, which seems to point the finger at the Oracle OLE Driver on Win 7:
Windows XP sync to Windows 7:
SQL Server to Oracle = ~8 seconds
SQL Server to SQL Server = ~6.5 seconds
Windows 7 sync to Windows 7:
SQL Server to Oracle = ~19 seconds
SQL Server to SQL Server = ~5.5 seconds
Has anybody else found this issue and if so have they found a cause?
We Have run NetMon and analysed the results and the packets seem to take twice as long in Win 7 as Win XP. This seemed to point to a network issue, but does not explain why 100% Microsoft is faster when synchronising Win 7 to Win 7, as opposed to Win XP to Win 7.
I get the feeling the issue lies somewhere in the changes that were made by Microsoft in Vista in the networking protocols and configuration, causing a side affect in the OLE Driver. It could be that the driver works, but needs to be tuned with the new networking protocols from Microsoft.
We have tried countless network settings, even the ones suggestions from MS Support made no difference at all.
Edited by: 925129 on 03.04.2012 03:57
Corrected a couple of types

Hi Greg,
Thanks for the answer, sorry for the late reply, I was away for Easter.
What we have done is to alter the triggers to record their names, start and end times to an SQL Server table. I delete the contents of the table then run a test and run several queries to analyse the trigger data. the difference between the min start time and the max end time is how we get the total time. We run many queries over the data. I can send you the table DDL and some test run results DML, as well as, the queries I use to analyse the results.
On top of this test we have run Microsoft's NetMon to analyse the network traffic and there it is clear that the packets take roughly twice as long in Win 7 as in Win XP, both in 32-bit and 64-bit OS versions. I know there has been some major network changes after Win XP and Microsoft are convinced this is an Oracle issue. The same OLE Driver is used for both Win 7 and Win XP OS's (excluding the one for 32-bit and one for 64-bit) and my guess is something needs to be tuned for the networking in Win 7. We have really tested this so much over the last 2 months and tried all kinds of network setting tuning in windows but nothing has worked at all.
After creating an SQL DB to act in the place Oracle DB, the same issue was not present, so it really is a heterogeneous platform issue. In fact if the sync is SQL to SQL it is faster in Win 7 not slower.
If you would like any of the results of our testing to see if you can spot the issue, you would be welcome.
Guy
Edited by: 925129 on 16-Apr-2012 05:40
Edited by: 925129 on 16-Apr-2012 05:41

SQL 2000 LINKED SERVER ERROR 7303 WITH SQL 2012 ON WINDOWS SERVER 2012 R2

Hi all,
I have a problem with SQL Server 2012 and a linked server for SQL 2000 database.
System specification:
Windows server 2012 64 bit
SQL SERVER 2012 64 bit
REMOTE SERVER SQL 2000 32 bit
I've installed sql native client 32bit,create a SYSTEM DSN odbc connection with "SQL Server" driver named "MYSERVER".
Create a linked server with the query below in SQL 2012:
EXEC master.dbo.sp_addlinkedserver @server =N'MYSERVER', @srvproduct=N'MYSERVER', @provider=N'MSDASQL', @datasrc =N'MYSERVER', @location=N'System';
EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'MySERVER',@useself=N'True',@locallogin=NULL,@rmtuser=NULL,@rmtpassword=NULL
GO
but when i browse the linked server i receved error 7303.

You need 64-bit MSDASQL. It is the bitness of the server you are connecting from that matters. 64-bit executables cannot hook into 32-bit DLL.
However, I suspect that you will not get things to work anyway. At least I have not seen anyone this far who has been able to set up a linked server from SQL 2012 to SQL 2000. I know that when I tried this, the following providers had this result:
SQLNCLI11 - does not support connections to SQL 2000.
SQLNCLI10 - failed with some obscure message that I don't recall.
SQLNCLI - Don't recall that the problem was here.
SQLOLEDB - SQLOLEDB is always replaced with the most recent version of SQLNCLI, so this fails because of lack of support.
I don't think I got through all version of the ODBC drivers, though.
Erland Sommarskog, SQL Server MVP, [email protected]

User created SQL Agent Job that uses linked server with Windows authentication

OK, here's what I want to do, but not sure exactly what I need to accomplish it.
Environment
Windows 2008 Enterprise
SQL 2012 Enterprise
SQL Server & SQL Agent running under AD account (which has local Windows Administrative privileges...yes, I know..bad!)
Linked server to Teradata utilizing AD account mappings (the linked server works successfully and each windows login is mapped to a Teradata LDAP login)
Requirement
Allow non sysadmins to create SQL Agent jobs which execute TSQL statements which use OPENQUERY(LDAPLinkedServer, '....) syntax
I've already given the non sysadmins the necessary permissions to create and run SQL Agent jobs, and I understand that the jobs run under their login context, but I suspect that I'm missing something when it comes to the linked server.
Each windows user could have access to different databases/tables on the Teradata system that even I (the SQL Server sysadmin) don't have access to.
How can I facilitate this functionality? Any ideas?

I think I may have been over complicating the Teradata piece. The authentication methodology in Teradata is LDAP, which just means that it authenticates against AD, but you still have to submit your Windows login & password. It doesn't automatically
authenticate you just because you're logged into Windows.
The linked server has the mapping for the individual windows logins like:
Local Login = <domain>.<windows id>
Remote User = <windows id>
Remote Password = <windows password>
This setup requires the user to have to change the passwords in the linked server whenever they change their passwords according to domain policy (every xx days)...but we've created a utility proc that they can use to do this.
So, I'm thinking that Teradata isn't really part of this equation.

Connect Non-SAP Oracle db (32bit) in sql 2005 (64 bit) using linked server

Hi,
I am connecting Oracle 10g database from SQL 2005 using linked server, in which i get the error
"Cannot initialize the data source object of OLE DB provider "MSDAORA" for linked server "L2ORACLE".
OLE DB provider "MSDAORA" for linked server "L2ORACLE" returned message "Oracle client and networking components
were not found. " (Microsoft SQL Server, Error: 7303)
SAP Server with sql 2005 db is in 64 bit server / Windows 2003
Non-SAP Oracle 10g is in 32 bit windows 2003 server.
i have installed Oracle 64 bit client in the SAP Server and also copied the 64 bit version of dboraslib.dll to the DIR_LIBRARY path. I am able to view the oracle tables in the oracle client.
But, when i create the linked server, it gives the above error.
If i install 32 bit version of Oracle client in the SAP Server, i am able to create the linked server in the db level, but, it says "Work Process restarted, session terminated" message in the Z program in SAP.
The same works in the test environment where both are 32 bit servers. problem is when SAP server is in 64 bit and non sap is in 32 bit.
Please suggest.
Thanks and Regards,
Nagu

"Cannot initialize the data source object of OLE DB provider "MSDAORA" for linked server "L2ORACLE".
OLE DB provider "MSDAORA" for linked server "L2ORACLE" returned message "Oracle client and networking components
were not found. " (Microsoft SQL Server, Error: 7303)
check the workprocess traces for errors (and/or SM21). It seems that the system is "not aware" that an Oracle client is installed.
64bit programs can´t load 32bit libraries/DLLs that´s why the workprocess dumps when you use the 32bit client.
Markus

How could I create a "Linked Server" link from SQL Server 2008R2 64-Bit to Oracle Database 11.2 64-Bit?

How could I create a "Linked Server" link from SQL Server 2008R2 64-Bit to Oracle Database 11.2 64-Bit?
Let's say the SQL Server and Oracle Database are in the same Company Internet Network.
I have the code, but I do not know how to use it. Such as what is System DSN Name? Where could I get it. What does it look like?
Do I need to install any Oracle Client Software in order to link from SQL Server to Oracle? Or SQL Server has the built-in drivers installed already that I can directly create a Linked Server from SQL Server to Oracle?
I need to know details. Thanks.
USE master
go
EXEC sp_addlinkedserver
     @server  = '{Linked Server Name}'
    ,@srvproduct = '{System DSN Name}'
    ,@provider  = 'MSDASQL'
    ,@datasrc  = '{System DSN Name}'
EXEC sp_addlinkedsrvlogin
     @rmtsrvname = '{Linked Server Name}'
    ,@useself  = 'False'
    ,@locallogin = NULL
    ,@rmtuser  = '{Oracle User Name}'
    ,@rmtpassword = '{Oracle User Password}'

You need an OLE DB provider for Oracle. There is one that ships with Windows, but it only supports very old versions of Oracle. Oracle has an OLE DB provider that you can use. I don't know if it's part of Oracle Client or how it is bundled.
You should not use MSDASQL or any DSN.
Erland Sommarskog, SQL Server MVP, [email protected]

Linked Server - SQL Server 2008 R2

I want to use AD groups which I have given access to SQL Server to utilitize a linked server but it does not allow this. It gives "Anonymous Login not allowed". I have checked the box - "Be made using the login's current security
context". The group is setup on both servers (Running SQL Server 2008).
Any help is appreciated!

Please check below link:
http://www.sqlservercentral.com/Forums/Topic807231-1526-1.aspx
None of the parameters are accepting windows group.
from BOL also:
[ @locallogin = ] 'locallogin'
Is a login on the local server. locallogin is sysname, with a default of NULL. NULL specifies that this entry applies to all local logins that connect tormtsrvname.
If not NULL, locallogin can be a SQL Server login or a Windows login. The Windows login must have been granted access to SQL Server either directly, or through its membership in a Windows group granted access.
[ @rmtuser = ] 'rmtuser'
Is the remote login used to connect to rmtsrvname when @useself is FALSE. When the remote server is an instance of SQL Server that does not use Windows Authentication, rmtuser is
a SQL Server login. rmtuser is sysname, with a default of NULL.
Best Wishes, Arbi; Please vote if you find this posting was helpful or Mark it as answered.

Cannot kill a session that is running a query on a linked server in SQL Server 2008 R2

Hi,
Cannot kill a session that is running a query on a linked server in SQL Server 2008 R2.
When I try to kill, it status shown as "KILLED/ROLLBACK"
I have facing the issue from long back. I searched many and none of them worked for me
Any help is greatly appreciated
Thanks
Jaison
Carver

I guess its stuck, can you see some blocking or any other process blocking the rollback.
can you check rollback status using below command. Or you can use sp_who2 and check status column
select percent_complete,estimated_completion_time from sys.dm_exec_requests
where spid=xxx
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

SQL 2008 Problem Calling an SP on an Oracle 10G Linked Server

Hi everyone
I've read through a number of posts on many sites about this issue but haven't found anything that has helped me so far. The machine I'm using is running Microsoft SQL Server 2008 64bit and the linked server I've created to Oracle 10G is using OraOLEDB.Oracle. If I test the connection in SQL Management Studio it succeeds and for any queries I have using OpenQuery to select from the Oracle DB I have no problem getting results.
The Oracle 32bit client and 64bit client versions are installed on the machine.
My problem is that I need to exec an Oracle SP which in turn inserts into various Oracle tables. I previously had this all working fine on 32bit SQL Server 2000 installation connected to Oracle 10G. Using the same code in SQL Server 2008 I get the following error:
Msg 7357, Level 16, State 2, Line 1
Cannot process the object "{CALL INTF.INTF_TW_PO_REQ_INTERFACE.MAIN(NULL, 15.000000, 0.000000, 'BLPO0099998', 'BLPO0099998', '', '', 39804, 21883, 'BLPO0099998', 249, 1, 950, 'Main', 190506, 37336, '1', TO_DATE( '20090706','YYYYMMDD' ), TO_DATE( '20090706','YYYYMMDD' ), 'INCOMPLETE',37336, {RESULTSET 1, P_Success})}". The OLE DB provider "OraOLEDB.Oracle" for linked server "ORACLE" indicates that either the object has no columns or the current user does not have permissions on that object
The call is made by the following piece of code in SQL:
SET @execCmd = N'SELECT
P_Success
FROM
OPENQUERY( ORACLE, '''+ @oracleCmd + ''')';
EXECUTE (@execCmd);
Where @oracleCmd = {CALL INTF.INTF_TW_PO_REQ_INTERFACE.MAIN(NULL, 15.000000, 0.000000, ''BLPO0099998'', ''BLPO0099998'', '''', '''', 39804, 21883, ''BLPO0099998'', 249, 1, 950, ''Main'', 190506, 37336, ''1'', TO_DATE( ''20090706'',''YYYYMMDD'' ), TO_DATE( ''20090706'',''YYYYMMDD'' ), ''INCOMPLETE'',37336, {RESULTSET 1, P_Success})}
I also tried using the below snippet from another post I found and got no joy either.
declare @result varchar(255)
exec ('BEGIN
?:= your_SP_Name(''arg1'', ''arg2'', etc);
END;
',@result OUTPUT) at your_LinkedServerName;
select @result;
OLE DB provider "OraOLEDB.Oracle" for linked server "ORACLE" returned message "ORA-06550: line 3, column 7:
PLS-00222: no function with name 'INTF_TW_PO_REQ_INTERFACE' exists in this scope
ORA-06550: line 3, column 1:
PL/SQL: Statement ignored".
I can't figure out why it doesn't work in SQL 2008 when it worked fine in SQL 2000 - PLEASE HELP!
Thank you
Alida Hope

Why development on 10g and production on 8i? Either both should be 8i or both should be 10g.
If you will keep production on 8i and development on 10g then you cannot stop such errors as there are features that are enabled by default in 10g and both the versions have very big differences.
Just go ahead and install 8i.

About SQL 2008 on any Windows Small Business Server

Hi, I try to install only 1 Server, we need that server run all setting (manage) of domain controller, active directory and sql. Please let me know if its possible install SQL 2008 (What ever versión) on Windows Small Business Server what
ever year (2012, 2008, Etc.) without having problems with the domain controller, firewall, sharing the SQL to network computer and the Windows Server year and versión we need? Thank!

Hi,
Please refer to following article and check the operating system requirements for SQL Server 2008.
Hardware and Software Requirements
for Installing SQL Server 2008
Based on your description, I understand that you want to install the SQL Server on a DC.
For security reasons, it is recommended that you do not install the SQL Server on a domain controller. So, it would be better if you put the SQL server on a second server or a virtualized server rather than on the SBS itself.
You may encounter problems when installing SQL Server on
a domain controller
Using SQL Server in Windows Small
Business Server 2008 Premium Edition
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu

Create linked server between MS SQL Server 2008 standard edition to MS SQL Server 2008 express edition

For the captioned issue, is it possible? We have successfully created linked server between 2 MS SQL server 2008 standard edition, but failed for the standard and express edition. Is there any trick to setup? Thanks.

Hello,
SQL Server Management Studio Express Edition may not allow to create a linked server, but the workaround is to use the T-SQL. You can use sp_addlinkedserver and sp_addlinkedsrvlogin.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Linked Server SQL 2008 64 bit Windows Server 2008 64 bit

Similar Messages

Maybe you are looking for