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: "infected with 11"
Date: Oct 11 2000 7:18PM

When running a stored proc from a Perl script, we received the following
error;

Sybase error: 20047
Sybase error: DBPROCESS is dead or not enabled.

The Sybase errorlog reported the situation as;

00:00000:00018:2000/10/10 16:44:46.22 kernel  current process
(0x18cf0084) infected with 11
00:00000:00018:2000/10/10 16:44:46.23 kernel  Address 0x46d104
(_sparclock+0x4), siginfo (code, address) = (1, 0x0)
00:00000:00018:2000/10/10 16:44:46.23 kernel
************************************
00:00000:00018:2000/10/10 16:44:46.23 kernel  SQL causing error :
some_stored_proc
00:00000:00018:2000/10/10 16:44:46.23 kernel
************************************
00:00000:00018:2000/10/10 16:44:46.23 server  SQL Text: some_stored_proc

00:00000:00018:2000/10/10 16:44:46.23 kernel  curdb = 9 pstat = 0x10000
lasterror = 0
00:00000:00018:2000/10/10 16:44:46.23 kernel  preverror = 0 transtate =
0
00:00000:00018:2000/10/10 16:44:46.23 kernel  curcmd = 195 program =
some_program


This is followed by a stack trace.  We are inclined to believe that it
may have something to do with object id's being out of sink.  The stored
proc referenced a table in another database that had earlier been
restored from a dump taken on a different server.  I might also mention
that the server running the stored proc was running 11.9.2.2 whereas the
dump was created on a server running 11.0.3.3.

I know this sounds a bit odd, but I'm hoping if someone else has
experienced this that perhaps they can provide some insight?