Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Unable to connect...

0 views
Skip to first unread message

Pablo Sanchez

unread,
Sep 18, 1996, 3:00:00 AM9/18/96
to fric...@stripe.colorado.edu

In article <frickell....@stripe.Colorado.EDU>, fric...@stripe.Colorado.EDU writes:
> hi, i'm having a problem with starting the sql server on our irix5.3
> machine (version 10.0.2). i run startserver, and then try to connect using
> isql and i get:
>
> Operating-system error:
> Invalid argument
> DB-LIBRARY error:
> Unable to connect: SQL Server is unavailable or does not exist.
>
> everything previously worked just fine, and then it just decided to
> have a fit. it's not a problem with the monitor server or clients.
> i have had this problem once before and it "magically" corrected
> itself. this time, there is no magic however. the error log just
> says where the kernel is using the area of disk for boot
> information, but nothing else. none of the usual startup is in
> there. it doesn't create the $SYBASE/SYBASE.krg and .srg0 files.
>
> anybody with ideas, please let me know!
>

Hi Jen,

Didn't we talk before? Anyway, take a look at your /var/adm/SYSLOG
file and see if there are any messages in it. If there are and it
doesn't make any sense to you, snip and mail me that part. Also, cut
and paste the output of the "starserver ..." command.

Thx.

Pablo Sanchez | Ph # (415) 933.3812 Fax # (415) 933.2821
pa...@sgi.com | Pg # (800) 930.5635 -or- pab...@corp.sgi.com
===============================================================================
I am accountable for my actions. http://reality.sgi.com/pablo [ /Sybase_FAQ ]

\JenJenJenJenJen\

unread,
Sep 18, 1996, 3:00:00 AM9/18/96
to

hi, i'm having a problem with starting the sql server on our irix5.3
machine (version 10.0.2). i run startserver, and then try to connect using
isql and i get:

Operating-system error:
Invalid argument
DB-LIBRARY error:
Unable to connect: SQL Server is unavailable or does not exist.

everything previously worked just fine, and then it just decided to have a
fit. it's not a problem with the monitor server or clients. i have had this
problem once before and it "magically" corrected itself. this time, there
is no magic however. the error log just says where the kernel is using the
area of disk for boot information, but nothing else. none of the usual startup
is in there. it doesn't create the $SYBASE/SYBASE.krg and .srg0 files.

anybody with ideas, please let me know!

thanks!
\\jen
fric...@colorado.edu


0 new messages