SQL 2005 BUG 1

[ptheriault]

I have just heard back from Microsoft about an issue I have been having. It is a bug they are aware of. Here is the error and a work around.

Unspecified error occurred on SQL Server. Connection may have been terminated by the server. [SQLSTATE HY000] (Error 0) Process ID *** attempted to unlock a resource it does not own: OBJECT ID ... Retry the transaction, because this error may be caused by a timing condition. If the problem persists, contact the database administrator. [SQLSTATE HY000] (Error 1203)

The problem is, this is happening on a resource the SPID does own.
The error is occuring because SQL is using a parrell execution plan and it thinks it doesn't own the resource on the other CPU.
There are two work arounds for this.
1. use sp_configure and set the max degree of parallelism to '1'. This is not a very good option because it is server wide.

2. Add OPTION (MAXDOP 1) at the end of the query that is creating the error.

I selected option 2 and it has corrected the problem for now.

Microsoft has not said when this bug will be corrected.

- Paul
- Database performance looks fine, it must be the Network!

 

[Catadmin]

Well, isn't that just dandy!!

@=Pbbt to MS. @=) to you for letting us know.



Catadmin - MCDBA, MCSA
"No, no. Yes. No, I tried that. Yes, both ways. No, I don't know. No again. Are there any more questions?"
-- Xena, "Been There, Done That"

 

[ptheriault]

I hear back from them again today. They have confirmed that the fix is NOT in SP2. Looks like I'll be waiting awhile.

- Paul
- Database performance looks fine, it must be the Network!