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.

Unkillable SPIDs

4 posts in Windows NT Last posting was on 2001-02-02 18:56:35.0Z
Mark Posted on 2001-01-31 15:18:02.0Z
From: Mark
Date: Wed, 31 Jan 2001 10:18:02 -0500
Newsgroups: sybase.public.sqlserver.nt
Subject: Unkillable SPIDs
Message-ID: <756FC5B9F7A0719100540C59852569E5.00540C6C852569E5@webforums>
Lines: 11
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com!webforums.sybase.com!news
Xref: forums-1-dub sybase.public.sqlserver.nt:1264
Article PK: 1088727

I have been experiencing intermittent problems when trying to kill
processes on sybase. They won't die immediately and stay present for up to
2 hours. I have tried physically removing the client's pc from the network
with no result. This is causing me problems as the connection is usually
holding locks, which prevent other users working.
I have seen similar issues when using Sybase on UNIX and the solution seems
to involve setting some kind of TCP timeout. Is there a similar solution
for NT?

I'm on Sybase 11.9.2 EBF9317 - and Windows NT4.0 SP6a

Thanks in advance for your help


Doug Wittich Posted on 2001-01-31 18:51:21.0Z
Message-ID: <3A785EA9.98FC9581@stpaul.com>
Date: Wed, 31 Jan 2001 13:51:21 -0500
From: Doug Wittich <doug.wittich@stpaul.com>
X-Mailer: Mozilla 4.76 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Unkillable SPIDs
References: <756FC5B9F7A0719100540C59852569E5.00540C6C852569E5@webforums>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.sqlserver.nt
Lines: 31
NNTP-Posting-Host: portald.stpaul.com 208.201.108.75
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:1262
Article PK: 1088726

You can set a lock timeout server wide. This is new in 11.9.2, see page 16-5
of the "What's new in 11.9.2".

sp_configure "lock wait period",60

when your session waits for 60 seconds, it will return with error 12205, and
the transaction will rollback.

This functionality can also be set for a single session with the "set lock
wait": (page 12-52 of "What's new...")

set lock wait 10

will make your session wait only 10 seconds before failing.

For those old geezers like me that came from DB2, this is a nice feature we've
waited a long time for.

Doug
Baltimore

Mark wrote:

> I have been experiencing intermittent problems when trying to kill
> processes on sybase. They won't die immediately and stay present for up to
> 2 hours. I have tried physically removing the client's pc from the network
> with no result. This is causing me problems as the connection is usually
> holding locks, which prevent other users working.
> I have seen similar issues when using Sybase on UNIX and the solution seems
> to involve setting some kind of TCP timeout. Is there a similar solution
> for NT?
>
> I'm on Sybase 11.9.2 EBF9317 - and Windows NT4.0 SP6a
>
> Thanks in advance for your help


Mark Posted on 2001-02-02 09:44:32.0Z
From: Mark
Date: Fri, 2 Feb 2001 04:44:32 -0500
Newsgroups: sybase.public.sqlserver.nt
Subject: Re: Unkillable SPIDs
Message-ID: <ABF3EC968E72D9FB003583F2852569E7.007A3BA4852569E6@webforums>
References: <756FC5B9F7A0719100540C59852569E5.00540C6C852569E5@webforums> <3A785EA9.98FC9581@stpaul.com>
Lines: 4
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com!webforums.sybase.com!news
Xref: forums-1-dub sybase.public.sqlserver.nt:1256
Article PK: 1088725

Thanks Doug, but the problem isn't with the new processes requesting locks
- the problem is with the old 'hung' process which isn't active but is
holding an exclusive lock. This is the process I cannot kill (Obviously
this is not a common occurrance, but when it does happen it causes a big
headache)


Doug Wittich Posted on 2001-02-02 18:56:35.0Z
Message-ID: <3A7B02E2.772DE059@stpaul.com>
Date: Fri, 02 Feb 2001 13:56:35 -0500
From: Doug Wittich <doug.wittich@stpaul.com>
X-Mailer: Mozilla 4.76 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
Subject: Re: Unkillable SPIDs
References: <756FC5B9F7A0719100540C59852569E5.00540C6C852569E5@webforums> <3A785EA9.98FC9581@stpaul.com> <ABF3EC968E72D9FB003583F2852569E7.007A3BA4852569E6@webforums>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Newsgroups: sybase.public.sqlserver.nt
Lines: 22
NNTP-Posting-Host: portald.stpaul.com 208.201.108.75
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:1253
Article PK: 1088724

I think my point was that at least the new requestors would learn of the
problem and not just "hang". We have quite a bit of problems with users who
reboot their workstation when they don't get a response in 30 seconds. This
would at least allow them to be aware of a problem, and hopefully notify
someone important about it (as Hiacynth Bucket would say).

I am certainly familiar with the (now more rare) problem you speak of as the
root cause, but I join the masses in not having a suitable answer for that
part.

d

Mark wrote:

> Thanks Doug, but the problem isn't with the new processes requesting locks
> - the problem is with the old 'hung' process which isn't active but is
> holding an exclusive lock. This is the process I cannot kill (Obviously
> this is not a common occurrance, but when it does happen it causes a big
> headache)