Welcome to the dBforums forums.

You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today!

If you have any problems with the registration process or your account login, please contact contact support.

If you prefer not to see double-underlined words and corresponding ads, place your cursor
here for ContentLink opt out.

Go Back  dBforums > Database Server Software > Sybase > Testing connectivity from command prompt

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 12-18-07, 12:47
MAlongi MAlongi is offline
Registered User
 
Join Date: Dec 2007
Posts: 1
Testing connectivity from command prompt

Hello everyone. I'm new here to the forums as well as Sybase in general and just have a few questions.

I seem to be having a problem with some clients' ability to connect to our Sybase database. Currently they are configured through ODBC, with all the correct registry keys and whatnot. The problem is this: The first time a client tries to connect, it won't see the database. However, if we go in to the configure panel in the Data Sources (ODBC) utility, choose the database and 'test connect' the client will connect, and then from then on connect no problem.

I have no problem doing this, however, not for all 1000+ clients. So my question is, is there anyway to issue a command similiar to a tnsping for oracle from the command prompt, so I can put it into a batch and just have client machines run the batch?

I apologize if this is a silly question.
Reply With Quote
  #2 (permalink)  
Old 12-19-07, 06:46
trvishi trvishi is offline
Registered User
 
Join Date: Sep 2003
Location: Switzerland
Posts: 371
It depends how your application connects. If its a local odbc source, then you have the option of pushing the odbc entries thro network, just like you push any other software. Talk to your network administrator.

Or if its thro sql.ini same case.
Reply With Quote
Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On