Michael Peppler
Sybase Consulting
Sybase on Linux
Install Guide for Sybase on Linux
General Sybase Resources
General Perl Resources
BCP Tool
Bug Tracker
Mailing List Archive
Downloads Directory
Sybase on Linux FAQ
Sybperl FAQ
Michael Peppler's resume

sybperl-l Archive

Up    Prev    Next    

From: Lee Falkenhagen <falkenl at crl dot com>
Subject: Re: Kill Zombies
Date: Dec 15 1997 4:16PM

Sybase has a known least through 11.03 where zombie processes 
can and will exist.  There is no known solution, according to Tech 
Support.  However, these processes are somewhat different from what you 
are referring to.  In the cases that I have seen, with Powerbuilder 3.x 
and 4.x, the process disappears from sysprocesses but still appears to 
have locks.  The problem with this in an OLTP environment is that it 
prevents the log from truncating after a dump because a tranaction will 
never commit.  We were working in a 1 GB transaction log (lots of batch 
processes...) so if we did not catch this bug, then the log would fill 
and we would have to shut down the server to clear the log.  Very 
painful process on this size of log.

And by the way...we were never able to "duplicate" this issue for Sybase 
Tech support...all we could do is send them output from selects on the 
system tables.

Lee Falkenhagen, Certified Sybase Professional

> -----Original Message-----
> From:	Christopher J. Brophy []
> Sent:	Monday, December 15, 1997 8:48 AM
> To:
> Subject:	Re: Kill Zombies
> Sorry for not providing more background.
> This is on Solaris 2.5.1
> Sybase 11.0.1
> Chris
> At 06:15 PM 12/9/97 -0800, you wrote:
> >
> >good god !  this scares me.  what platform are you running System
> >11 under ?  i haven't noticed this at all on our platform (sun
> >solaris 2.6).
> >
> >doug
> >
> >On Tue, 9 Dec 1997, Christopher J. Brophy wrote:
> >
> >> I am seeking seeking help on whether System 11 supports a
> configuration
> >> parameter which will automatically kill a process after a certain
> clock
> >> time has expired, say ten minutes.
> >> 
> >> We have a situation where a browser client or Web Server client
> (SybPerl)
> >> is being terminated before the Sybase server has returned all the
> results.
> >> The Sybase process then goes into a sleep state but holds locks
> needed by
> >> other processes indefinitely.
> >> 
> >> Thanks in advance for any help.
> >> 
> >> Chris 
> >> 
> >
> >