SQL 2000 Error: 1203, Severity: 20, State: 1 Error

Question

Post reply

SQL 2000 Error: 1203, Severity: 20, State: 1 Error

Will Reed

SSC Rookie

Points: 30
More actions
July 17, 2006 at 1:12 pm

#94485

Our SQL Server 200 box is getting perflib errors when we get a decent
amount of people using an application that I wrote, call queue system,
web based. To accomplish a queue type system on a button push I wrote
a query like this...
BEGIN TRANSACTION;
Select top 1...fields here...
FROM table with (xlock,readpast)
(2 joins)
WHERE numerous where clauses
ORDER BY 2 order bys.
Now our sql server starts timing out..then in the app log this shows
up....
Error: 1203, Severity: 20, State: 1
Process ID 62 attempting to unlock unowned resource PAG: 6:1:126407.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
The reason I am doing xlock is to make a record not viewable to 2
people if they click the button on the web form that runs the above
query within the same minute, they would get different records....
So to avoid this error which I assume is due to my xlock should I
rethink my query?
Is there anyway to redo my query to not do top 1 and still select one
record????
This is frustrating.

Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic. Login to reply

Gail Shaw SSC Guru Points: 1004514 More actions · Answer 1

I would suggest you do an integrity check on your database. It looks like you might have allocation errors.

DBCC

CheckDB ('<YourDBName>') WITH PHYSICAL_ONLY

Errors caused by queries generally have a severity around 16. A severity of 20 indicates a serious problem.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass