Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Failed to kill spid

6 posts in General Discussion Last posting was on 2009-10-07 11:49:56.0Z
Yaniv C. Posted on 2009-10-05 16:46:38.0Z
Sender: 535f.4aca1fda.1804289383@sybase.com
From: Yaniv C.
Newsgroups: sybase.public.ase.general
Subject: Failed to kill spid
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4aca22ee.53af.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 5 Oct 2009 09:46:38 -0700
X-Trace: forums-1-dub 1254761198 10.22.241.41 (5 Oct 2009 09:46:38 -0700)
X-Original-Trace: 5 Oct 2009 09:46:38 -0700, 10.22.241.41
Lines: 33
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28404
Article PK: 77646

Hi
Last week I faced difficult situaction and I would like to
share it with you for advice.

The problem: A process was "stuck" in Sybase and failed to
be killed.

The environment:
Sybase ASE 15.0.2 #ESD2 on Linux Red-Hat 4.2

A connection was open for three weeks
(according to syslogsdhold) in a transaction.
the spid apears in sysprocesses and syslogshold.
by running dbcc sqltext: the SQL text was simple select from
applicative table. ( select after an update in the
transaction)
The application is a Jboss application server that uses
connection pulls.

The problem was that the transaction was "stuck" and almost
filled up our transaction log.
In sysprocesses: the status was sleeping, the command was
"EXECUTING".
when running kill command inside Sybase, no errors report in
console.The error log just reported the kill. Actually the
spid did not killed and no status changed.
I have to restart the 24*7 production environment to get rid
of the spid.
Have anyone ever incured this problem?
Have anyone find the "super kill" command? ...

Thanks,
Yaniv


Rob V [ Sybase ] Posted on 2009-10-05 20:30:11.0Z
Reply-To: "Rob V [ Sybase ]" <robv@DO.NOT.SPAM.sypron.nl.REMOVE.THIS.DECOY>
From: "Rob V [ Sybase ]" <robv@DO.NOT.SPAM.sypron.nl.REMOVE.THIS.DECOY>
Newsgroups: sybase.public.ase.general
References: <4aca22ee.53af.1681692777@sybase.com>
Subject: Re: Failed to kill spid
Lines: 72
Organization: Sypron BV / TeamSybase / Sybase
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4aca5753@forums-1-dub>
Date: 5 Oct 2009 13:30:11 -0700
X-Trace: forums-1-dub 1254774611 10.22.241.152 (5 Oct 2009 13:30:11 -0700)
X-Original-Trace: 5 Oct 2009 13:30:11 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28405
Article PK: 77648

I know of one particular issue that seems to fit your description, but it is
not possible to say it was the same as you hit. The bugid is # 465981, and
it was fixed in 15.0.2 esd#3.
I recommend you check with Sybase Techsupport to determine whether you've
hit this; some detailed information would need to be verified for that.

BTW, the problem for things like these is not that a stronger 'kill' is
needed. When things get stuck in certain situations, the only safe solution
can be to reboot the ASE server: by forcefully removing the spid, there
would be risks of memory corruption and hence database corruption, and that
is to be avoided at all cost. This sort of situation would typically be the
result of an ASE bug -- and the one above got fixed.
(so, the stronger kind of 'kill' actually exists: it's a shutdown with
nowait ;-)

HTH,

Rob V.
-----------------------------------------------------------------
Rob Verschoor

Certified Sybase Professional DBA for ASE 15.0/12.5/12.0/11.5/11.0
and Replication Server 15.0.1/12.5 // TeamSybase

Author of Sybase books (order online at www.sypron.nl/shop):
"Tips, Tricks & Recipes for Sybase ASE" (ASE 15 edition)
"The Complete Sybase ASE Quick Reference Guide"
"The Complete Sybase Replication Server Quick Reference Guide"

mailto:rob@YOUR.SPAM.sypron.nl.NOT.FOR.ME
http://www.sypron.nl
Sypron B.V., Amersfoort, The Netherlands
Chamber of Commerce 27138666
-----------------------------------------------------------------

<Yaniv C.> wrote in message news:4aca22ee.53af.1681692777@sybase.com...
> Hi
> Last week I faced difficult situaction and I would like to
> share it with you for advice.
>
> The problem: A process was "stuck" in Sybase and failed to
> be killed.
>
> The environment:
> Sybase ASE 15.0.2 #ESD2 on Linux Red-Hat 4.2
>
> A connection was open for three weeks
> (according to syslogsdhold) in a transaction.
> the spid apears in sysprocesses and syslogshold.
> by running dbcc sqltext: the SQL text was simple select from
> applicative table. ( select after an update in the
> transaction)
> The application is a Jboss application server that uses
> connection pulls.
>
> The problem was that the transaction was "stuck" and almost
> filled up our transaction log.
> In sysprocesses: the status was sleeping, the command was
> "EXECUTING".
> when running kill command inside Sybase, no errors report in
> console.The error log just reported the kill. Actually the
> spid did not killed and no status changed.
> I have to restart the 24*7 production environment to get rid
> of the spid.
> Have anyone ever incured this problem?
> Have anyone find the "super kill" command? ...
>
> Thanks,
> Yaniv


Yaniv C. Posted on 2009-10-06 08:07:08.0Z
Sender: 535f.4aca1fda.1804289383@sybase.com
From: Yaniv C.
Newsgroups: sybase.public.ase.general
Subject: Re: Failed to kill spid
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4acafaac.75d8.1681692777@sybase.com>
References: <4aca5753@forums-1-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 6 Oct 2009 01:07:08 -0700
X-Trace: forums-1-dub 1254816428 10.22.241.41 (6 Oct 2009 01:07:08 -0700)
X-Original-Trace: 6 Oct 2009 01:07:08 -0700, 10.22.241.41
Lines: 103
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28406
Article PK: 77649

Hi Rob

Thanks for the reply.

Are you talking about bug id 465981 ?
I google it and from :
http://www.sybase.com/detail?id=1063631

The description is as followed:
"In rare circumstances, Adaptive Server may hang and a stack
trace which includes the modules 'buf__writewait' and
'buffree' may be reported when running a select-into
statement."

If it what you meant, this is not the case.
Since my ASE did not hang, all other processes worked great.
Just this single spid refuced to be killed.

Anyway, I have to fill now a report to the customer why I
restart his production machine...

Yaniv

> I know of one particular issue that seems to fit your
> description, but it is not possible to say it was the same
> as you hit. The bugid is # 465981, and it was fixed in
> 15.0.2 esd#3. I recommend you check with Sybase
> Techsupport to determine whether you've hit this; some
> detailed information would need to be verified for that.
>
> BTW, the problem for things like these is not that a
> stronger 'kill' is needed. When things get stuck in
> certain situations, the only safe solution can be to
> reboot the ASE server: by forcefully removing the spid,
> there would be risks of memory corruption and hence
> database corruption, and that is to be avoided at all
> cost. This sort of situation would typically be the
> result of an ASE bug -- and the one above got fixed. (so,
> the stronger kind of 'kill' actually exists: it's a
> shutdown with nowait ;-)
>
> HTH,
>
> Rob V.
> ----------------------------------------------------------
> ------- Rob Verschoor
>
> Certified Sybase Professional DBA for ASE
> 15.0/12.5/12.0/11.5/11.0 and Replication Server
> 15.0.1/12.5 // TeamSybase
>
> Author of Sybase books (order online at
> www.sypron.nl/shop): "Tips, Tricks & Recipes for Sybase
> ASE" (ASE 15 edition) "The Complete Sybase ASE Quick
> Reference Guide" "The Complete Sybase Replication Server
> Quick Reference Guide"
>
> mailto:rob@YOUR.SPAM.sypron.nl.NOT.FOR.ME
> http://www.sypron.nl
> Sypron B.V., Amersfoort, The Netherlands
> Chamber of Commerce 27138666
> ----------------------------------------------------------
> -------
>
> <Yaniv C.> wrote in message
> > news:4aca22ee.53af.1681692777@sybase.com... Hi
> > Last week I faced difficult situaction and I would like
> > to share it with you for advice.
> >
> > The problem: A process was "stuck" in Sybase and failed
> > to be killed.
> >
> > The environment:
> > Sybase ASE 15.0.2 #ESD2 on Linux Red-Hat 4.2
> >
> > A connection was open for three weeks
> > (according to syslogsdhold) in a transaction.
> > the spid apears in sysprocesses and syslogshold.
> > by running dbcc sqltext: the SQL text was simple select
> > from applicative table. ( select after an update in the
> > transaction)
> > The application is a Jboss application server that uses
> > connection pulls.
> >
> > The problem was that the transaction was "stuck" and
> > almost filled up our transaction log.
> > In sysprocesses: the status was sleeping, the command
> > was "EXECUTING".
> > when running kill command inside Sybase, no errors
> > report in console.The error log just reported the kill.
> > Actually the spid did not killed and no status changed.
> > I have to restart the 24*7 production environment to get
> > rid of the spid.
> > Have anyone ever incured this problem?
> > Have anyone find the "super kill" command? ...
> >
> > Thanks,
> > Yaniv
>
>
>


Neal Stack [Sybase] Posted on 2009-10-06 15:55:07.0Z
From: "Neal Stack [Sybase]" <nstack@nospam.com>
User-Agent: Thunderbird 2.0.0.23 (Windows/20090812)
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: Failed to kill spid
References: <4aca5753@forums-1-dub> <4acafaac.75d8.1681692777@sybase.com>
In-Reply-To: <4acafaac.75d8.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4acb685b@forums-1-dub>
Date: 6 Oct 2009 08:55:07 -0700
X-Trace: forums-1-dub 1254844507 10.22.241.152 (6 Oct 2009 08:55:07 -0700)
X-Original-Trace: 6 Oct 2009 08:55:07 -0700, vip152.sybase.com
Lines: 13
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28412
Article PK: 77655

Hello,

Can you do a "dbcc traceon(3604)" and then "dbcc stacktrace(spid)" (replace "spid" with
the actual spid that is hanging).

The stacktrace of the hung spid would give us much more detail about why it is hung.

Also, if you log a case with Sybase Technical Support, they may provide you with
instructions on how to perform a manual shared memory dump of the server which would
provide them with an even greater level of detail to analyze the situation.

Regards,
Neal


Rob V [ Sybase ] Posted on 2009-10-07 10:39:02.0Z
Reply-To: "Rob V [ Sybase ]" <robv@DO.NOT.SPAM.sypron.nl.REMOVE.THIS.DECOY>
From: "Rob V [ Sybase ]" <robv@DO.NOT.SPAM.sypron.nl.REMOVE.THIS.DECOY>
Newsgroups: sybase.public.ase.general
References: <4aca5753@forums-1-dub> <4acafaac.75d8.1681692777@sybase.com>
Subject: Re: Failed to kill spid
Lines: 129
Organization: Sypron BV / TeamSybase / Sybase
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.5843
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-RFC2646: Format=Flowed; Original
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4acc6fc6$2@forums-1-dub>
Date: 7 Oct 2009 03:39:02 -0700
X-Trace: forums-1-dub 1254911942 10.22.241.152 (7 Oct 2009 03:39:02 -0700)
X-Original-Trace: 7 Oct 2009 03:39:02 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28416
Article PK: 77659

Yeah, thats the one I meant. But the description does not mean that ASE
hangs as a whole -- it's just that particular spid which hangs.

HTH,

Rob V.
-----------------------------------------------------------------
Rob Verschoor

Certified Sybase Professional DBA for ASE 15.0/12.5/12.0/11.5/11.0
and Replication Server 15.0.1/12.5 // TeamSybase

Author of Sybase books (order online at www.sypron.nl/shop):
"Tips, Tricks & Recipes for Sybase ASE" (ASE 15 edition)
"The Complete Sybase ASE Quick Reference Guide"
"The Complete Sybase Replication Server Quick Reference Guide"

mailto:rob@YOUR.SPAM.sypron.nl.NOT.FOR.ME
http://www.sypron.nl
Sypron B.V., Amersfoort, The Netherlands
Chamber of Commerce 27138666
-----------------------------------------------------------------

<Yaniv C.> wrote in message news:4acafaac.75d8.1681692777@sybase.com...
> Hi Rob
>
> Thanks for the reply.
>
> Are you talking about bug id 465981 ?
> I google it and from :
> http://www.sybase.com/detail?id=1063631
>
> The description is as followed:
> "In rare circumstances, Adaptive Server may hang and a stack
> trace which includes the modules 'buf__writewait' and
> 'buffree' may be reported when running a select-into
> statement."
>
> If it what you meant, this is not the case.
> Since my ASE did not hang, all other processes worked great.
> Just this single spid refuced to be killed.
>
> Anyway, I have to fill now a report to the customer why I
> restart his production machine...
>
> Yaniv
>
>
>
>> I know of one particular issue that seems to fit your
>> description, but it is not possible to say it was the same
>> as you hit. The bugid is # 465981, and it was fixed in
>> 15.0.2 esd#3. I recommend you check with Sybase
>> Techsupport to determine whether you've hit this; some
>> detailed information would need to be verified for that.
>>
>> BTW, the problem for things like these is not that a
>> stronger 'kill' is needed. When things get stuck in
>> certain situations, the only safe solution can be to
>> reboot the ASE server: by forcefully removing the spid,
>> there would be risks of memory corruption and hence
>> database corruption, and that is to be avoided at all
>> cost. This sort of situation would typically be the
>> result of an ASE bug -- and the one above got fixed. (so,
>> the stronger kind of 'kill' actually exists: it's a
>> shutdown with nowait ;-)
>>
>> HTH,
>>
>> Rob V.
>> ----------------------------------------------------------
>> ------- Rob Verschoor
>>
>> Certified Sybase Professional DBA for ASE
>> 15.0/12.5/12.0/11.5/11.0 and Replication Server
>> 15.0.1/12.5 // TeamSybase
>>
>> Author of Sybase books (order online at
>> www.sypron.nl/shop): "Tips, Tricks & Recipes for Sybase
>> ASE" (ASE 15 edition) "The Complete Sybase ASE Quick
>> Reference Guide" "The Complete Sybase Replication Server
>> Quick Reference Guide"
>>
>> mailto:rob@YOUR.SPAM.sypron.nl.NOT.FOR.ME
>> http://www.sypron.nl
>> Sypron B.V., Amersfoort, The Netherlands
>> Chamber of Commerce 27138666
>> ----------------------------------------------------------
>> -------
>>
>> <Yaniv C.> wrote in message
>> > news:4aca22ee.53af.1681692777@sybase.com... Hi
>> > Last week I faced difficult situaction and I would like
>> > to share it with you for advice.
>> >
>> > The problem: A process was "stuck" in Sybase and failed
>> > to be killed.
>> >
>> > The environment:
>> > Sybase ASE 15.0.2 #ESD2 on Linux Red-Hat 4.2
>> >
>> > A connection was open for three weeks
>> > (according to syslogsdhold) in a transaction.
>> > the spid apears in sysprocesses and syslogshold.
>> > by running dbcc sqltext: the SQL text was simple select
>> > from applicative table. ( select after an update in the
>> > transaction)
>> > The application is a Jboss application server that uses
>> > connection pulls.
>> >
>> > The problem was that the transaction was "stuck" and
>> > almost filled up our transaction log.
>> > In sysprocesses: the status was sleeping, the command
>> > was "EXECUTING".
>> > when running kill command inside Sybase, no errors
>> > report in console.The error log just reported the kill.
>> > Actually the spid did not killed and no status changed.
>> > I have to restart the 24*7 production environment to get
>> > rid of the spid.
>> > Have anyone ever incured this problem?
>> > Have anyone find the "super kill" command? ...
>> >
>> > Thanks,
>> > Yaniv
>>
>>
>>


Yaniv C. Posted on 2009-10-07 11:49:56.0Z
Sender: 535f.4aca1fda.1804289383@sybase.com
From: Yaniv C.
Newsgroups: sybase.public.ase.general
Subject: Re: Failed to kill spid
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4acc8064.3ccb.1681692777@sybase.com>
References: <4acc6fc6$2@forums-1-dub>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 7 Oct 2009 04:49:56 -0700
X-Trace: forums-1-dub 1254916196 10.22.241.41 (7 Oct 2009 04:49:56 -0700)
X-Original-Trace: 7 Oct 2009 04:49:56 -0700, 10.22.241.41
Lines: 136
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:28417
Article PK: 77660

Thanks.

> Yeah, thats the one I meant. But the description does not
> mean that ASE hangs as a whole -- it's just that
> particular spid which hangs.
>
> HTH,
>
> Rob V.
> ----------------------------------------------------------
> ------- Rob Verschoor
>
> Certified Sybase Professional DBA for ASE
> 15.0/12.5/12.0/11.5/11.0 and Replication Server
> 15.0.1/12.5 // TeamSybase
>
> Author of Sybase books (order online at
> www.sypron.nl/shop): "Tips, Tricks & Recipes for Sybase
> ASE" (ASE 15 edition) "The Complete Sybase ASE Quick
> Reference Guide" "The Complete Sybase Replication Server
> Quick Reference Guide"
>
> mailto:rob@YOUR.SPAM.sypron.nl.NOT.FOR.ME
> http://www.sypron.nl
> Sypron B.V., Amersfoort, The Netherlands
> Chamber of Commerce 27138666
> ----------------------------------------------------------
> -------
>
> <Yaniv C.> wrote in message
> > news:4acafaac.75d8.1681692777@sybase.com... Hi Rob
> >
> > Thanks for the reply.
> >
> > Are you talking about bug id 465981 ?
> > I google it and from :
> > http://www.sybase.com/detail?id=1063631
> >
> > The description is as followed:
> > "In rare circumstances, Adaptive Server may hang and a
> > stack trace which includes the modules 'buf__writewait'
> > and 'buffree' may be reported when running a select-into
> > statement."
> >
> > If it what you meant, this is not the case.
> > Since my ASE did not hang, all other processes worked
> > great. Just this single spid refuced to be killed.
> >
> > Anyway, I have to fill now a report to the customer why
> > I restart his production machine...
> >
> > Yaniv
> >
> >
> >
> >> I know of one particular issue that seems to fit your
> >> description, but it is not possible to say it was the
> same >> as you hit. The bugid is # 465981, and it was
> fixed in >> 15.0.2 esd#3. I recommend you check with
> Sybase >> Techsupport to determine whether you've hit this
> ; some >> detailed information would need to be verified
> for that. >>
> >> BTW, the problem for things like these is not that a
> >> stronger 'kill' is needed. When things get stuck in
> >> certain situations, the only safe solution can be to
> >> reboot the ASE server: by forcefully removing the spid,
> >> there would be risks of memory corruption and hence
> >> database corruption, and that is to be avoided at all
> >> cost. This sort of situation would typically be the
> >> result of an ASE bug -- and the one above got fixed.
> (so, >> the stronger kind of 'kill' actually exists: it's
> a >> shutdown with nowait ;-)
> >>
> >> HTH,
> >>
> >> Rob V.
> >>
> ----------------------------------------------------------
> >> ------- Rob Verschoor >>
> >> Certified Sybase Professional DBA for ASE
> >> 15.0/12.5/12.0/11.5/11.0 and Replication Server
> >> 15.0.1/12.5 // TeamSybase
> >>
> >> Author of Sybase books (order online at
> >> www.sypron.nl/shop): "Tips, Tricks & Recipes for Sybase
> >> ASE" (ASE 15 edition) "The Complete Sybase ASE Quick
> >> Reference Guide" "The Complete Sybase Replication
> Server >> Quick Reference Guide"
> >>
> >> mailto:rob@YOUR.SPAM.sypron.nl.NOT.FOR.ME
> >> http://www.sypron.nl
> >> Sypron B.V., Amersfoort, The Netherlands
> >> Chamber of Commerce 27138666
> >>
> ----------------------------------------------------------
> >> ------- >>
> >> <Yaniv C.> wrote in message
> >> > news:4aca22ee.53af.1681692777@sybase.com... Hi
> >> > Last week I faced difficult situaction and I would
> like >> > to share it with you for advice.
> >> >
> >> > The problem: A process was "stuck" in Sybase and
> failed >> > to be killed.
> >> >
> >> > The environment:
> >> > Sybase ASE 15.0.2 #ESD2 on Linux Red-Hat 4.2
> >> >
> >> > A connection was open for three weeks
> >> > (according to syslogsdhold) in a transaction.
> >> > the spid apears in sysprocesses and syslogshold.
> >> > by running dbcc sqltext: the SQL text was simple
> select >> > from applicative table. ( select after an
> update in the >> > transaction)
> >> > The application is a Jboss application server that
> uses >> > connection pulls.
> >> >
> >> > The problem was that the transaction was "stuck" and
> >> > almost filled up our transaction log.
> >> > In sysprocesses: the status was sleeping, the command
> >> > was "EXECUTING".
> >> > when running kill command inside Sybase, no errors
> >> > report in console.The error log just reported the
> kill. >> > Actually the spid did not killed and no status
> changed. >> > I have to restart the 24*7 production
> environment to get >> > rid of the spid.
> >> > Have anyone ever incured this problem?
> >> > Have anyone find the "super kill" command? ...
> >> >
> >> > Thanks,
> >> > Yaniv
> >>
> >>
> >>
>
>