Solved

How to test the sybase connection.

Posted on 2008-10-10
4
3,126 Views
Last Modified: 2012-05-05
Hai !
       we are pulling the data from a sybase remote machine.
Before extracting i need to test the sybase connection status. How to do this ?

How can we determine that the connection failed (sybase database down) ?
0
Comment
Question by:vishali_vishu
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
4 Comments
 
LVL 2

Expert Comment

by:navid86
ID: 22690737
If I understand the question properly, you need to check the ODBC connection.  This is under the control panel in Windows XP.  Control Planel > Administrative Tools > Data Sources (ODBC).

Under user DSN or system DSN you should see your ODBC connection.  Highlight your connection then click Configure.  At the bottom of the Configure screen there is a Test Connection button.  You can click that to test your connection.

Hope this helps!
0
 
LVL 19

Accepted Solution

by:
grant300 earned 500 total points
ID: 22690844
I am betting that you are doing the data pull automatically in some kind of script and want to put a check of the Sybase connection into the process so you can tell what is wrong.  Since you specify Unix, I figure there is no ODBC.  That's O.K.; it actually makes things easier.

Since you are on a Unix/Linux platform, you will have the Sybase Client Library (CT-lib) and it's associated components installed.  On Windows machines there is a utility called "sybping" for testing connections but there is no equivalent on Linux or Unix.  The script below will do roughly the same thing using ISQL and some shell commands to determine success or failure.  I believe this was posted somewhere by Michael Peppler, a well know Sybase guru.  It looks like it might be a little rough yet.

Regards,
Bill



#!/bin/sh
 
srv=$1
logfile=/tmp/sybping.$$
isql -Usa -PTryItNow -S$srv >$logfile 2>&1
 
# ASE
grep 'Login failed' $logfile >/dev/null
if [ $? -eq 0 ]
then
echo "Server $srv is up"
exit 0
fi
 
# Generic message when connection fails.
grep "connect two endpoints failed" $logfile >/dev/null
if [ $? -eq 0 ]
then
echo "Server $srv is unreachable"
exit 1
fi
 
echo "Unknown sybping error:"
cat $logfile
exit -1

Open in new window

0

Featured Post

MS Dynamics Made Instantly Simpler

Make Your Microsoft Dynamics Investment Count  & Drastically Decrease Training Time by Providing Intuitive Step-By-Step WalkThru Tutorials.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Background In several of the companies I have worked for, I noticed that corporate reporting is off loaded from the production database and done mainly on a clone database which needs to be kept up to date daily by various means, be it a logical…
Using SQL Scripts we can save all the SQL queries as files that we use very frequently on our database later point of time. This is one of the feature present under SQL Workshop in Oracle Application Express.
This video shows how to set up a shell script to accept a positional parameter when called, pass that to a SQL script, accept the output from the statement back and then manipulate it in the Shell.
This video shows how to Export data from an Oracle database using the Datapump Export Utility.  The corresponding Datapump Import utility is also discussed and demonstrated.
Suggested Courses

617 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question