June 21, 2007 at 12:44 pm
I am trying to create a linked server using a Teradata ODBC DSN in SQL 2005. When I create the linked server, I recieve the following error trying to connect:
The OLE DB provider "SQL Server" for linked server "(null)" reported an error. One or more arguments were reported invalid by the provider.
Cannot obtain the schema rowset "DBSCHEMA_CATALOGS" for OLE DB provider "SQL Server" for linked server "(null)". The provider supports the interface, but returns a failure code when it is used. (Microsoft SQL Server, Error: 7399)
I have a similar linked server in SQL 2000, set up exactly the same with no connection issue.
I've read an article posted by someone having the same issue using a DB2 DSN and they mentioned it is a bug in SQL 2005.
Anyone know anything about or seen this issue?
Thanks!
June 21, 2007 at 2:44 pm
This may or may not be relevant. But...
Glancing through the error message it appears your are attempting to link to server "(null)", this is in the error message twice.
Are you adding the linked server through SSMS or script?
SSMS - [Server Objects] - [Linked Servers] - [Providers]
good luck
June 22, 2007 at 12:33 am
You have created an ODBC then you do you use an OLEDB provider you can create linked servers with ODBC connections.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
June 22, 2007 at 9:55 am
Yes. I have created the ODBC DSN and tested the connection to the Teradata server using a .udl file. So the connectivity works.
When I create the linked server in SSMS, I receive this error:
The OLE DB provider "SQL Server" for linked server "(null)" reported an error. One or more arguments were reported invalid by the provider.
Cannot obtain the schema rowset "DBSCHEMA_CATALOGS" for OLE DB provider "SQL Server" for linked server "(null)". The provider supports the interface, but returns a failure code when it is used. (Microsoft SQL Server, Error: 7399)
June 25, 2007 at 4:10 pm
I am having the same problem.....
creating linked server, I specify:
provider: Microsoft OLE DB provider for ODBC drivers
product name: ODBC system DSN
Data Source: ODBC system DSN
I do not specify anything else for provider string, location or catalogue; for security options I identify valid credentials and then create the link. the test connection to the linked server succeeds but I'm unable to open the catalog and see the tables -- this is when I get the error message reported by other users in this thread
October 9, 2007 at 5:46 am
Hi Folks
I have same problem but with strange instance that I ave created 2 LInked servers with MYSQL server using 2 different databases. Created ODBC System DSNs for them. One of Linked server working fine and show catalogs. But another server giving this same error.
The OLE DB provider "SQL Server" for linked server "(null)" reported an error. The provider reported an unexpected catastrophic failure.
Cannot obtain the schema rowset "DBSCHEMA_CATALOGS" for OLE DB provider "SQL Server" for linked server "(null)". The provider supports the interface, but returns a failure code when it is used. (Microsoft SQL Server, Error: 7399)
Please help....
Thanks in Advance
SqlIndia
November 1, 2007 at 3:47 pm
We are having a similar problem. Trying to create a linked server in SQL2000, to an Oracle server, using the MSDAORA.DLL as the OLE DB provider.
Here is our error when we try to connect to the linked server:
OLE DB provider 'MSDAORA' reported an error. (Microsoft SQL Server, Error: 7399)
Thanks in advance for any ideas.
November 1, 2007 at 11:33 pm
Is oracle clint installed in the sql server machine. if so can yu post us the exact error message that you get.
Cheers,
Sugeshkumar Rajendran
SQL Server MVP
http://sugeshkr.blogspot.com
November 2, 2007 at 8:27 am
Yes, we have the Oracle 9i client installed on the SQL Server 2000 machine.
Here is the error:
TITLE: Microsoft SQL Server Management Studio
------------------------------
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
OLE DB provider 'MSDAORA' reported an error. (Microsoft SQL Server, Error: 7399)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=08.00.2040&EvtSrc=MSSQLServer&EvtID=7399&LinkId=20476
Thanks in advance for any insight you might have.
cheers,
Kevin
November 2, 2007 at 8:41 am
Have you modified client registry? If not check BOL , "linked servers, access Oracle database instance".
What's about TNS names, is there an entry for oracle server you are trying to link?
November 2, 2007 at 4:31 pm
That was the problem. We didn’t update our reg values ( HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOCI ) when we installed the Oracle 9i client
BEFORE:
OracleXaLib = xa80.dll
OracleSqlLib = SQLLib80.dll
OracleOciLib = oci.dll
NOW:
OracleXaLib = oraclient9.dll
OracleSqlLib = orasql9.dll
OracleOciLib = oci.dll
Many thanks for your help!
December 17, 2007 at 6:14 pm
I am having the same issue. Did you find the solution to this if Yes, Please share.. Apprecaite your help!
May 22, 2008 at 4:02 pm
I have a similar problem connect sql server 2005 to Oracle. The thread did not show any resolution. Were you able to correct the problem?
Thanks
Jim Schellenberg
July 28, 2008 at 12:39 pm
I had a similar problem -- error 7399 -- with a FoxPro linked server.
I had to give the SQL account (domain account that logs in to SQL) full control to the folder containing the FoxPro table files.
I also had to check off / enable 'Allow inprocess' for the VFPOLEDB provider, I don't know if this is something necessary for the Oracle provider...
HTH Tom
September 12, 2008 at 10:26 am
This turned into an Oracle thread and we lost the connection to the original question. I think someone might have touched on the (null) server issue but no one seems to have followed up on that. I'm having the same issues. The test connection's OK but when I attempt to browse the linked db I get the same error as above. Any more ideas?
Viewing 15 posts - 1 through 15 (of 22 total)
You must be logged in to reply to this topic. Login to reply