Link server issue

Dear All,
We have Install:-
Windows server 2008, 64 bit.
MS SQL Server 2008.
Oracle 11g client, 64 bit.
odac 11g 64 bit.
We have oracle 10g on our live server that is alos on 2008, 64 bit.
Our requirment is to access oracle view from oracle 10g database to MS SQL server database. For that we have install all the above things.
But oracle is not visible while in the link server. To add link server we are following below steps,
In SQL server database Right click on link server, add link server but it does not show any oracle link.
We have install oracle client first and then ODAC.
are we missing any steps to add link server in SQL Database.
Thansks.

I found couple of good link when I said "access oracle database from sql server 2008" to google like :
1.http://stackoverflow.com/questions/307636/how-do-you-setup-a-linked-server-to-an-oracle-database-on-sql-2000-2005
2.http://www.sqlmag.com/article/oracle/connecting-sql-server-and-oracle-using-linked-servers-102313
3.http://www.dotnetfunda.com/forums/thread3238-connection-between-oracle-server-and-sql-server-2008.aspx
Just try to follow and let us know, if they help you.
Regards
Girish Sharma

Similar Messages

LINKED SERVER ISSUE on ORACLE DATABASE

Hi everyone
I have SQL 2008 R2 Running on Windows server 2003 R2 OS.
I have created a linked server to ORACLE 11
I have may jobs running process against this linked server and thy work fine
But soddenly I receive this error :
Cannot initialize the data source object of OLE DB provider "OraOLEDB.Oracle" for linked server "WMS". [SQLSTATE 42000] (Error 7303). The step failed
In this scenario the SQL SERVER AGENT Account is the Domain administrator.
When I restart the Server it begin to work fine again but from time to time I receive again the error mentioned above.
Have any one pass through this issue?

Is the network connection to Oracle box stable? Is it inside a firewall?
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

SQL Server Linked Server Issues with MVC 5

I have 2 linked servers
Server A = MYOB ( custom 32 it ODBC Driver )
Server B = SQL Server 64 Bit.
They link fine using windows authentication - and I can run the following no problem in SQL Management tools ( as part of a stored proc ) .
DECLARE @MaxID varchar(100)DECLARE @Query varchar(MAX)
-- Insert Sales
SELECT @MaxID = MAX(SaleID) FROM [r2hserver\SQLexpress].artoo.dbo.MYOB_Sales
SELECT @Query = 'INSERT [r2hserver\SQLexpress].artoo.dbo.MYOB_Sales SELECT * FROM OpenQuery(MYOB,''SELECT * FROM Sales WHERE SaleID > ' + @MaxID + ''')'
EXEC(@Query)
The problem is: Whenever execute the stored procedure from within a MVC 5 Web App ( EF6 ) - I get :
Unable to start a nested transaction for OLE DB provider "SQLNCLI11" for linked server "myserver/SQLexpress".
A nested transaction was required because the XACT_ABORT option was set to OFF.
and if I set XACT_ABORT ON - I get : Microsoft Distributed Transaction Coordinator (MS DTC) has stopped this transaction.
I cannot figure out how to make it run! I have turned firewalls off and tried many different config.
Ideas?

Hi Marty,
Thank you for your question.
I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
Thank you for your understanding and support.
Regards,
Charlie Liao
TechNet Community Support

Linked server issue

Hello. It's been a while since I've worked with Oracle, and in my latest project, we're having an issue with a linked server we believe. We can log into both databases separately, we've verified that linked servers to other dbs are working, but when trying to pull information from this one particular db (wx) while in another db (sx) we're getting a timeout error. we've noticed that the dbf's are quite full in (sx) in the System and User tablespaces - but we're able to pull data from other linked dbs on this db (sx). On the other db (wx), the most full tablespace is only at 80%? Both of these dbs (sx and wx) are on the same Oracle server, so there isn't a network connection error. does anyone have any ideas on what else to check? We're using version 9i...
Thanks!

ORACLE_HOME is the database software install. Do you have one Oracle install on the server, or two ?
What OS are you on ?
To use "tnsping" you need to have $ORACLE_HOME and $PATH set. Then try to "tnsping xxxx" and see what the error is. If this fails, then check the hostname and port in the tnsnames.ora file, and compare it to the hostname and port in the listener.ora file.

SQL Server Link Server issue.

Hi,
I have setup a linked sql in SQL Server 2000 to connect to an Oracle 9i database. When I try to select from a table through the link server I get the following error message.
Could not execute query against OLE DB provider 'OraOLEDB.Oracle'.
OLE DB error trace [OLE/DB Provider 'OraOLEDB.Oracle' ICommandText::Execute returned 0x80040155].
This is for a table without any nvarchar2 columns (I get a different error for tables containing those datatypes).
Any ideas?
Thanks
Sanjay

Ralph,
1. Right-click on the linked server you created, select Properties from the popup menu.
2. In Linked Server Properties dialog box, click Options... button under Provider Name dropdown combo.
3. Check (or enable) "Allow InProcess" option.
4. Click Apply button.
5. Click Ok button.
Sinclair

Linked server issue using SQLNCLI versions on SQL 2008 & 2014

Hi all,
Our product creates databases on a sql server 2008 instance and creates linked servers between them to use distributed queries.
This looks like: "EXEC sp_addlinkedserver 'linkDatabaseA', '', 'SQLNCLI10', '.', NULL, NULL, 'DatabaseA'"".
Distributed queries from second database to DatabaseA work fine in this scenario.
As we want to support both SQL 2008 and SQL 2014 in the next product version, I changed this to SQLNCLI11 as the provider
and tested on SQL 2008 after installation of the SQLNCLI11 driver.
This resulted in following error message:
Msg 468, Level 16, State 9, Line 7
Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.
This is very suprising as the SQL Server 2008 instance and both DB's have "SQL_Latin1_General_CP1_CI_AS" as their collation sequence.
Then I tried the opposite, installing SQLNCLI10 on SQL 2014. This gave exactly same error! Using SQLNCLI11 went fine ofcourse.
Generation sp_addlinkedserver statements with correct driver based on SQL version, I'd rather not do (some of the calls are
generated in SQL from settings in other db tables which are also used for external connx) and adding COLLATE to the queries also
has consequences like performance degradation. Adding collate on SQL 2014 with SQLNCLI10 as linked server provider results in
following error:
Msg 7399, Level 16, State 1, Line 1617
The OLE DB provider "SQLNCLI10" for linked server "linkDatabaseA" reported an error. Access denied.
Msg 7301, Level 16, State 2, Line 1617
Cannot obtain the required interface ("IID_IDBCreateCommand") from OLE DB provider "SQLNCLI10" for linked server "linkDatabaseA".
Q: Is there any way that SQLNCLI11 can be made to work for linked servers on SQL2008 (preferred solution) or SQLNCLI10 on SQL2014?
Thx for any feedback.
Regards, Jouke

Hi Sofiya,
Thx for replying.
For the deployment reasons mentioned above, I would prefer to use only one SQLNCLI version in both 2008R2 & 2012/2014 scenario's. Most preferred would ofcourse be SQLNCLI11 as this is the latest.
This would mean that I'd like to be able to configure linked server in SQL2008R2 using SQLNCLI11 driver.
I would expect that it would be downward compatible with SQLNCLI10 for all client usage, including linked server, which in essence is one SQL DB doing client access to another SQL DB either on same server instance or another. I suspect it requests DB
metadata from remote DB in order to make decisions and this seems not to work in my setup. If this metadata API is part of the public API, this could indicate that medadata API has been broken in SQLNCLI11 (heavy speculation on my part here!), which could
also affect other usage (eg. linked server between SQL2008(R2) and SQL2012/2014 instances, (I'll try to set this up and test this, might take a few days. If someone is volunteering, below are db table schemes and query, update @datasrc to point to remote sql
server instance)).
Regards, Jouke
-- This script to run on SQL2008(R2). On SQL2012/2014, install SQLNCLI10 and change @provider in sp_addlinkedserver call.
-- Pre:
-- - DatabaseA and DatabaseB are created manually in SSMS
-- - SQLNCLI11 has been installed
USE [DatabaseA]
GO
CREATE TABLE [dbo].[DatabaseATable](
[IdField] [int] NOT NULL,
[LinkField] [nchar](10) NULL,
CONSTRAINT [PK_DatabaseATable] PRIMARY KEY CLUSTERED
[IdField] ASC
) ON [PRIMARY]
GO
EXEC master.dbo.sp_addlinkedserver @server = N'linkDatabaseA', @srvproduct=N'',@provider=N'SQLNCLI11', @datasrc=N'.', @catalog=N'DatabaseA'
GO
USE [DatabaseB]
GO
CREATE TABLE [dbo].[DatabaseBTable](
[IdField] [int] NOT NULL,
[LinkField] [nchar](10) NULL,
CONSTRAINT [PK_DatabaseBTable] PRIMARY KEY CLUSTERED
[IdField] ASC
) ON [PRIMARY]
GO
SELECT b.*, a.*
FROM DatabaseBTable AS b WITH(NOLOCK)
JOIN linkDatabaseA.DatabaseA.dbo.DatabaseATable AS a
ON a.LinkField = b.LinkField
Hi Jouke Numan,
According to your description, I install SQL Native Client 11.0 OLE DB Provider in SQL Server 2008R2, and as you post, create two database on the same instance with collation in server default, then create Linked Server with SQLNCI11.0.
When I run the query statement, it can execute well. It also do not occur the collation conflict. I still recommend you check the collation of server, database, or column and so on.
SQL Server Native Client 11.0 provides OLE DB support to applications connecting to SQL Server versions 2005, 2008, 2008R2, 2012. So for the deployment reasons, you can choose the only SQLNCLI11.0 in both SQL Server 2008R2 and SQL Server 2012/2014.
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Dynamic Link Server Issues

Between the constant cc updates and the VERY spotty performance of the Dynamic Link "feature" I have wasted hours of valuable time this week. Adobe, you used to be SO reliable. Now, you are the definition of UN-reliable. You DO KNOW that some of us are trying to use this software in professional workflows, right???
[Please choose only a short description for the thread title.]
Message was edited by: Jim Simon

At least yours is working. I'm working on a bunch of newsletters and I can't get media encoder to read AE through Premiere at all. The AE dynamic link shows in PP but does not encode in AME. So I have to render everything in the foreground.
Patch soon please.

Memory leak issue with link server between SQL Server 2012 and Oracle

Hi,
We are trying to use the linked server feature with SQL Server 2012 to connect SQL server and Oracle database. We are concerned about the existing memory leak issue. For more context please refer to the link.
http://blogs.msdn.com/b/psssql/archive/2009/09/22/if-you-use-linked-server-queries-you-need-to-read-this.aspx
The above link talks about the issues with SQL Server versions 2005 and 2008, not sure if this is still the case in 2012. I could not find any article that talks about if this issue was fixed by Microsoft in later version.
We know that SQL Server process crashes because of the third-party linked server provider which is loaded inside SQL Server process. If the third-party linked server provider is enabled together with the
Allow inprocess option, the SQL Server process crashes when this third-party linked server experiences internal problems.
We wanted to know if this fixed in SQL Server 2012 ?

So your question is more of a information type or are you really facing OOM issue.
There can be two things for OOM
1. There is bug in SQL Server which is causing the issue which might be fixed in 2012
2. The Linked server provider used to connect to Oracle is not upto date and some patch is missing or more recent version is to be used. Did you made sure that you are using latest version.
What is Oracle version you are trying to connect(9i,10g, R2...)
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 Article
MVP

Linked Server : The old "Login failed for users "NT Authority\Anonymous Logon" issue

Two SQL Servers: SQL Server 2008 sp3 and SQL Server 2014We are transitioning from 2008 to 2014. We have need of some linked servers whilst this is ongoing.
We've used them before, and indeed I set them up quite easily or so I thought.
On the 2014 server, I can test the connection and everything ok. If I logon to the linked server instance (ie the 2008 server) on the 2014 server, and connect to 2014 server, and test, I get the Error: 18456 Login failed error message.
If I create a linked server on any instances of the 2008 server pointing to the 2014 server, no problems whatsoever going in that direction.
Note that I'm selecting "Be made using the login's current security context"
The 2008 sql server services is using a domain account as it's logon, whereas the 2014 server is using Managed Service Accounts.
I've checked the SPN's and they all seem to be set ok.
I then thought that perhaps there was an inconsistency with the Managed Service Account not being recognised (although does work when actually on the 2014 server). I then changed (using Sql Server config manager) the account being used for the MSSQLSvc
from the managed service account to the same account used by the 2008 sql server. This seems to have produced a certain degree of success. I can now test the connection from my local ssms and the 2008 server and these work ok for the most part.
I presumed I had a workaround and did further testing, however it doesn't always seem to run true. This could of course be due to me not taking the same steps to reproduce the original workaround.
This is effectively a transient condition as eventually we won't need the linked servers, however, they are needed for at least the next 2-3 months.
Could anyone help explain the nature of this problem and where I'm going wrong?
Regards
Ian

Hello,
In addition to what Ashwin has asked (though the anonymous error message kind of gives it away):
It does sound (I know you have you checked, but SPNs can be tricky devils) like an SPN issue or delegation issue
The first thing I would point you to is the Kerberos Checking Tool for SQL Server. It's pretty new but in my testing it's been very accurate. Download, run it, and check the output:
http://www.microsoft.com/en-us/download/details.aspx?id=39046
Secondly, I would point you to this entry (yes, made by me):
http://www.seangallardy.com/2014/05/using-kerberos-with-sql-server-part-1-double-hop/
The reason why it works when you login from the 2008 server or the 2014 server and go to either or is because you're not double-hopping. You're local to the server, there is no delegation involved.
Sean Gallardy | Blog
MCM 2008
MCSM:Data Platform Charter Member

Issue with linked server

We have created a linked server.We are getting below error when a trigger is executed from the source server.
1)OLE DB provider "SQLNCLI" for linked server "Destination server" returned message "The partner transaction manager has disabled its support for remote/network transactions."
2)Msg 7391, Level 16, State 2, Procedure trgScandetails, Line 21
The operation could not be performed because OLE DB provider "SQLNCLI" for linked server "Destination server" was unable to begin a distributed transaction.
3)OLE DB provider "SQLNCLI" for linked server "Destination server" returned message "No transaction is active."
Please help me on this.
Thanks in advance.

Using triggers are bad, things like this make it more worse.
I would say that using triggers in general is not bad, but it is a good way to implement validation of business rules which cannot be encoded in constraints, as well various forms of cascading updates. In short, any thing which is needed to uphold database
integrity.
But from this follows that as soon you stray outside the database you are doing something more. Maybe you have distributed your data over more than one database for some reason, and it is still a matter of referential integrity. If the databases are different
applications, it is probably not the correct solution.
And maybe you distributed your databases over several servers for load balancing or whatever. But then at the same time you also increase the complexity of your solution considerably. For instance, what happens if you have a disaster and must restore one
of the databases?
As for the actual question, getting MSDTC to work can be a breeze - and it can be a nightmare. My experience is that if you have a domain and there are no trust or double-hop issues, it works. But if you don't have a domain, but only a workgroup it can
be very difficult. It may work if the service accounts on the machines have the same name and password.
But you should also ask yourself: if the other server is down, what do you want to happen?
Erland Sommarskog, SQL Server MVP, [email protected]

Connecting to a cube via a linked server

Hi
I want to connect to a SSAS cube via a linked server. When I ran a query against the SSAS cube from directly from the SQL server it runs fine.
If however I run the query in SSMS from my PC I get
OLE DB provider "MSOLAP" for linked server "SSASServer01" returned message "The following system error occurred: .".
Msg 7373, Level 16, State 2, Line 1
Cannot set the initialization properties for OLE DB provider "MSOLAP" for linked server "SSASServer01".
In the properties on the linked server I've defined an account to use for the connection to get round the double hop issue
Any Ideas why I'm still getting the error?
Alex

Hi Mr P,
According to your description, you get the error 7373 with message "Cannot set the initialization properties for OLE DB provider "MSOLAP" for linked server "SSASServer01"." when connecting a SSAS cube via linked server.
Right?
In this scenario, based on the error code 7373, it points to the issue of MSOLAP provider, please firstly check the properties setting for MSOLAP. Make sure the "Allow Inprocess" is selected. You may also have other options selected depends on
your query.
Also check if ports for your server (1434 and 2383) are listening proper locally and externally. Please refer to a similar thread below:
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/9d5bd9e0-c380-4a0f-bdab-857751c71fba/ole-db-msolap-provider-issues?forum=sqlanalysisservices
If you have any question, please feel free to ask.
Best Regards,
Simon Hou
TechNet Community Support

How to create a view on SQLServer 2008 as an OPENQuery select to a MYSQL linked server

I am trying to create a view on SQLServer through Management Studio based on data on a MYSql server.
I have created the Linked server and I am able to query all data.
Using the syntax select * from OPENQUERY (linkedServer, 'select * from MYSQL-table') - This works fine
What I am trying to do now is issue the following statement
create view ViewnameToBeCreatedOnSQLServer
as select * from OPENQUERY (linkedServer, 'select * from MYSQL-table')
When I run this from SSMS I get the following error
OLE DB provider "MSDASQL" for linked server "TESTTSC2" returned message "[MySQL][ODBC 5.1 Driver][mysqld-5.0.95-log]Table 'FP.M3' doesn't exist".
Msg 7350, Level 16, State 2, Procedure FPMaster3, Line 2
Cannot get the column information from OLE DB provider "MSDASQL" for linked server "TESTTSC2".
The account I am using has create view privs and alter schema privs on the SQlServer side. I am assuming there are not isues on the MYSQL server side since I am able to successfully run the select statement using OPENQUERY. There must be one small
piece I am missing. has anyone experienced the same problem and were you able to find a solution?

All the configurations seem to be in place correctly since I can SELECT any data with no issues. The statement
select * from OPENQUERY (linkedServer, 'select * from MYSQL-table')
works fine and I can change the table I am selecting from which all return data. Therefore, the objects all exists in MYSQL.
The DSN is set up, the linked Server is good, the provider is set up, the DB account has all privs.
It only fails when I try to create the view on SQLServer as a select from a remote table accessed via the linked MYSQL server. I connect to SQLServer with DB account PS which has full privs including CREATE VIEW and ALTER SCHEMA. The MYSQL pass-through account
has read access to all objects in the MYSQL schema. I am trying to figure out if I might be missing some little part of this puzzle when trying to create a new object (CRESTE VIEW) vs. just reading the data (SELECT).
The kicker in all this is that I did create a view on SQLServer in this manner about a year ago and I am able to see the view definition and that view still works! So, this is quite interesting that I am not able to create a new object.
If there any specific information I could provide which might help, I am happy to do that. Just did not want to provide the details on all of the puzzle pieces if it can be avoided but if it comes to that then that's OK also.
Thanks very much! I appreciate your help.

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

Error: An error occurred while preparing the query in openquery on ServiceNow ODBC Link Server

Hi Team,
Greetings of the Day!!!!!
I have a created a link server on SQL Server 2008 R2 databse of Service Now ODBC driver. And written a stored procedure using openquery to get the data from link server.
Now problem is that, when i have scheduled that stored procedure in sql jobs. When this job runs automatically then we are getting below error while when i start the job mannually then it's not giving error.
An error occurred while preparing the query "..........."
Please help me to resolve this issue.
Regards,
Brijendra Pandey

Hi Fanny,
I had reviewed the job history. I am getting below message where as table is exist in the database.
Message
Executed as user: NT AUTHORITY\SYSTEM. OLE DB provider "MSDASQL" for linked server "SNOWDSN" returned message "[DataDirect][ODBC OpenAccess SDK driver][OpenAccess SDK SQL Engine]Base table:incident not found.[10129]". [SQLSTATE 01000] (Message 7412) OLE
DB provider "MSDASQL" for linked server "SNOWDSN" returned message "[DataDirect][ODBC OpenAccess SDK driver][OpenAccess SDK SQL Engine]Base table:sysapproval_approver not found.[10129]". [SQLSTATE 01000] (Message 7412) OLE DB provider "MSDASQL" for linked
server "SNOWDSN" returned message "[DataDirect][ODBC OpenAccess SDK driver][OpenAccess SDK SQL Engine]Base table:problem not found.[10129]". [SQLSTATE 01000] (Message 7412). The step succeeded.
Regards,
Brijendra Pandey

Error while linked server is used to verify the existence of a table

Hi All,
Pls help me solve an issue related to linked Server..
Following is my query:
IF EXISTS (select 1 from [LinkedServerName].Sales.sys.tables where name = 'SalesTable')
BEGIN
DECLARE @LastSales varchar(25)
SET @LastSales = (select CONVERT(VARCHAR(25),max(LastSalesTime)) from [LinkedServerName].SalesDB.dbo.SalesTable)
END
What should happen is, it should check the existence of SalesTable on Linked Server (select 1 from [LinkedServer].Sales.sys.tables where name = 'SalesTable'), and only after the it returns 1, the variable @LastSales should be alloted a value.
But in my case, as soon as I run the code, it gives the error:
The OLE DB provider "SQLNCLI10" for linked server "LinkedServerName" does not contain the table ""Sales"."dbo"."SalesTable"".
The table either does not exist or the current user does not have permissions on that table.
My question is that if the condition fails at the very outset returning null (as the table does not exist), then why it is entering BEGIN and throwing the error.
All your valuable inputs are appreciated !!

Inconsistency is the hailmark of SQL Server.
If you say:
IF EXISTS (select 1 from Sales.sys.tables where name = 'SalesTable')
BEGIN
DECLARE @LastSales varchar(25)
SET @LastSales = (select CONVERT(VARCHAR(25),max(LastSalesTime)) from SalesDB.dbo.SalesTable)
END
This will work as you expect. That is, if the table does not exist, the batch will parse and produce no result. This is because SQL Server has deferred name resolution for tables. If a table is missing at compile time, SQL Server suppresses the error in
hope that the table will be there at run-time.
But there is an exception to this. For table sources on remote data sources, there is no deferred name resolution, but the table has to be there at compile time. This is quite ironic. Personally, I think deferred name resolution (which was introduced in
SQL 7) is a big misfeature, but I could buy if there was deferred name resolution for objects on linked server, since the server may be down, and you have coded for this like you have above. Well, if the server is down, the IF EXISTS will fail to compile to.
You will need to introduce a new scope somewhere to avoid the problem. For instance:
IF EXISTS (select 1 from [LinkedServerName].Sales.sys.tables where name = 'SalesTable')
BEGIN
DECLARE @LastSales varchar(25)
EXEC [Linkedservername].SalesDB.sys.sp_executesql
N'SET @LastSales = (select CONVERT(VARCHAR(25),max(LastSalesTime)) from SalesTable)',
N'@LastSales varchar(25) OUTPUT', @LastSales
END
Erland Sommarskog, SQL Server MVP, [email protected]

Link server issue

Similar Messages

Maybe you are looking for