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.

process lock!! help!!

2 posts in Windows NT Last posting was on 2001-03-02 14:39:56.0Z
chenghua Posted on 2001-02-16 02:32:03.0Z
From: "chenghua" <hcheng@ecust.edu.cn>
Subject: process lock!! help!!
Date: Fri, 16 Feb 2001 10:32:03 +0800
Lines: 11
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Message-ID: <7U#KkL8lAHA.253@forums.sybase.com>
Newsgroups: sybase.public.sqlserver.nt
NNTP-Posting-Host: 202.120.107.46
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:1216
Article PK: 1088670

Our Sybase server edition is 11.9 and NT edition is 4.0

When we use "select * from table1", it can't finished and the process is
"sleep lock".
then we use "dbcc table1", the process also is "sleep lock". At that time ,
there are few processes of users.
And the table is not in writing .

Who can help me ? or provide me some tools to check it ?


Sridhar Posted on 2001-03-02 14:39:56.0Z
From: sridhar
Date: Fri, 2 Mar 2001 09:39:56 -0500
Newsgroups: sybase.public.sqlserver.nt
Subject: Re: process lock!! help!!
Message-ID: <0C103B0F126373F400508F6485256A03.005F3B71852569FA@webforums>
References: <7U#KkL8lAHA.253@forums.sybase.com>
Lines: 5
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:1159
Article PK: 1088661

Try using sp_lock to check which processes are locking and sp_who to check
who is the locking process. Then try kill on the locking process. The table
that is locked can be found by looking up the id from the sp_lock in the
sysobjects table (be sure you are in the correct db)
sridhar