November 29, 2005 at 10:45 am
Good Morning. I have a linked server to a Sybase database. The Sybase server has been replaced with a new Sybase server. I went into ODBC and changed the server name, so that the linked server name would not change. My openquery statement just hangs. I tried creating a new linked server, still hangs. Any ideas would be appreciated.
Thanks
Dorothy
November 30, 2005 at 1:22 pm
I've never really worked with a Sybase linked server but have worked directly with Sybase servers and databases for quite a while. You say that you have a 'new' server. I'd check to see that the user account on the Sybase side still exists and the appropriate access and permissions needed are still intact. I've seen many databases moved without their corresponding logins and permissions, especially server roles on Sybase. Also you may have all of those things moved and appearing correct but on the Sybase side you can still lose permissions because the sid in master..syslogins does not match the sid in your_user_database..sysusers. If your Sybase DBA needs a script to fix this I may have on onsite for you.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
December 1, 2005 at 10:40 am
I talked to the Sybase guy. He can login as my user and access the database.
The 'new' server is a replacement. I currently can't connect to the 'old' server either. I have tried creating a new ODBC data source, modified the sybase\sql.ini file and created a new linked server. I don't get any errors, it just hangs.
December 1, 2005 at 10:54 am
I found that that connections to Sybase worked smoothly when on the same box and/or on the same subnet; but when on a different subnet that they required the "commlinks=tcpip" parameter in the connect string. When I say "subnet" let me clarify... if the IP address is 142.99.111.98, the .111. part must be the same... if it is .113., for instance, the commlinks parameter is needed (above, plus host= and port= parameters). and I also remember that improperly specifying "commlink" vs. "commlinks" caused it not to work, as well. it's not just from SQL to Sybase... Sybase Central and other Sybase tools also require this parameter.
Hope this is of some help.
December 1, 2005 at 4:27 pm
Where do I put the "commlinks=tcpip" parameter? In the ODBC data source?
December 2, 2005 at 11:11 am
Figured it out. I was told that ";" was used to comment out the old connections.. Wrong. I removed the commented lines and it works.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply