very urgent linked server issue.

Question

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

spaghettidba SSC Guru Points: 105732 More actions · Answer 1

You're not giving out much information...

Can't you avoid using DSNs?

-- Gianluca Sartori

striker-baba SSCrazy Points: 2170 More actions · Answer 2

Inorder to create a linked server to teradata, we use DSN and then mention the DSN in the datasource coloumn while creating linked server.

here are complete details:

Firstly, I checked all server by pinging (making sure no network issues)

Next I tried to create the Linked server in my development server to teradata server. And its working.

But, when I create same Linked server in my prod to teradata server. its not working.

I am using just a simple query using openquery statement, and also using sp_testlinkedserver [LS_name]

to test the things.

Do you think I need to restart the prod server (since the Linked server is working in dev but not in prod.)

Thanks,

spaghettidba SSC Guru Points: 105732 More actions · Answer 3

Can you set up the linked server directly, usgin the teradata oledb provider?

Some ideas here:

-- Gianluca Sartori

striker-baba SSCrazy Points: 2170 More actions · Answer 4

Hello guys,

Not only my teradata linkedserver, but also my sybase linked server in not working.

when I run a small 1 row select query, Its taking infinite time.

at least iam not getting any error mssgs like timout or any other messages.

can some one let me know where do i need to look into.

spaghettidba SSC Guru Points: 105732 More actions · Answer 5

Just a guess, but maybe the providers are loaded in process and you won't get them back working without restarting SQL Server.

It's something I experienced in the past with a DB2/400 provider. I had to change the settings to load it out of process.

-- Gianluca Sartori

striker-baba SSCrazy Points: 2170 More actions · Answer 6

Actually, One of our DBA was saying that

it initially gave an error message sayiing that

"catastrophic failure".

I tried to google this and they say that this might be due to the failure of the odbc drivers.

Can any one help me on this ?

striker-baba SSCrazy Points: 2170 More actions · Answer 7

Thanks all for the replies,

I actually restarted the server (using cluster environment, I just failed over).

And then it was working fine.

The problem is with the ODBC drivers on the prod server.

All the linked servers with ODBC as provider were having some problem.

I fixed it by restarting the server. It did not help me technically but atleast I could resolve the problem.

I appreciate for the help.