PEPPLER.ORG
Michael Peppler
Sybase Consulting
Menu
Home
Sybase on Linux
Install Guide for Sybase on Linux
General Sybase Resources
General Perl Resources
Freeware
Sybperl
Sybase::Simple
DBD::Sybase
BCP Tool
Bug Tracker
Mailing List Archive
Downloads Directory
FAQs
Sybase on Linux FAQ
Sybperl FAQ
Personal
Michael Peppler's resume

sybperl-l Archive

Up    Prev    Next    

From: Thomas Santamaria <Thomas dot Santamaria at msdw dot com>
Subject: Random Sybase Outages - Sybase Error 20009
Date: Jul 21 2000 3:34PM

Now that we have moved a number of our batch jobs in an automated
scheduler, we occasionally receive the following error message from
Sybase;

Sybase error: 20009
Sybase error: Unable to connect: SQL Server is unavailable or does not
exist.

The accompanying OS Error varies from run to run.  Here are some
examples;

OS Error: Bad file number
OS Error: No such file or directory
OS Error: Interrupted system call
OS Error: Error 0

Could it be volume related, now that a number of jobs are running at
once?  The SQL server is definitely up and the interfaces file is in
place.  Has anyone encountered a situation similar to this and what did
you do to resolve it?

Thanks for your help,
Tom