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.

Deadlock detected during UPDATE and SELECT

2 posts in Windows NT Last posting was on 2001-03-16 04:39:48.0Z
Tsvetomira Posted on 2001-03-13 10:27:37.0Z
From: Tsvetomira
Date: Tue, 13 Mar 2001 05:27:37 -0500
Newsgroups: sybase.public.sqlserver.nt
Subject: Deadlock detected during UPDATE and SELECT
Message-ID: <C4CC251701087B45003975CB85256A0E.0039761B85256A0E@webforums>
Lines: 18
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:1111
Article PK: 1087713

I'm using ASE 11.5 and Windows NT 4.0
The ASE 11.5 errlog reports deadlock during UPDATE (exclusive lock) and
SELECT (shared lock). The SELECT statement has "noholdlock" in its FROM
clause:

SELECT col1, col2, col3
FROM table noholdlock
WHERE condition1

I think that if I use "noholdlock" that means that no locks will be hold
on that table. Is that true or not? Does anybody knows what is the problem
and if I'm right why "noholdlock" doesn't work?

I'll appreciate your help!

Best regards,
Tsvetomira Jordanova


Jim Egan Posted on 2001-03-16 04:39:48.0Z
From: Jim Egan <dbaguru@eganomics.com>
Subject: Re: Deadlock detected during UPDATE and SELECT
Date: Thu, 15 Mar 2001 21:39:48 -0700
Message-ID: <MPG.151b47023f03c3ab98b1af@forums.sybase.com>
References: <C4CC251701087B45003975CB85256A0E.0039761B85256A0E@webforums>
Reply-To: eganjp@compuserve.com
X-Newsreader: MicroPlanet Gravity v2.30
Newsgroups: sybase.public.sqlserver.nt
Lines: 6
NNTP-Posting-Host: c1420400-b.hiland1.co.home.com 65.7.153.228
Path: forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.sqlserver.nt:1093
Article PK: 1087695

You could be blocking/locking on an index page also.
--
Jim Egan [TeamSybase]
Senior Consultant
Sybase Professional Services

Get your free subscription to PowerTimes at http://www.powertimes.com