Re: SQL 2000 Error: 1203, Severity: 20, State: 1 Error
- From: "wreed" <whreed@xxxxxxxxx>
- Date: 17 Jul 2006 06:17:42 -0700
Erland Sommarskog wrote:
SQL Server times out? If you get a message "Timeout expired" that is a
client-side timeout. Or have you enabled lock timeouts.
Error: 1203, Severity: 20, State: 1
Process ID 62 attempting to unlock unowned resource PAG: 6:1:126407.
...
So to avoid this error which I assume is due to my xlock should I
rethink my query?
1203 is definitely to regard as an internal server error, so you are
hitting a bug of some sort.
It would be interesting to know what happens first, the timeout or the
1203. And what sort of timeout you get.
Since by default most client libraries has a default timeout of 30
seconds, I assume that you have a client-side timeout. When you get
such a timeout, you should always issue a IF @@trancount > 0 ROLLBACK
TRANSACTION, because there is no automatic rollback on timeouts.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
Can it be that I am running a TOP 1 and the query is actually pulling a
whole query back then only taking the top row? Or am I totally wrong
on how a TOP 1 works.
.
- Follow-Ups:
- Re: SQL 2000 Error: 1203, Severity: 20, State: 1 Error
- From: Erland Sommarskog
- Re: SQL 2000 Error: 1203, Severity: 20, State: 1 Error
- References:
- SQL 2000 Error: 1203, Severity: 20, State: 1 Error
- From: wreed
- Re: SQL 2000 Error: 1203, Severity: 20, State: 1 Error
- From: Erland Sommarskog
- SQL 2000 Error: 1203, Severity: 20, State: 1 Error
- Prev by Date: Re: What do you mean 'clustered' index?
- Next by Date: Re: Query to find a missing number
- Previous by thread: Re: SQL 2000 Error: 1203, Severity: 20, State: 1 Error
- Next by thread: Re: SQL 2000 Error: 1203, Severity: 20, State: 1 Error
- Index(es):
Relevant Pages
|