SQL error.
-
I get this error when executing a query :
1203: Process ID 52 attempting to unlock unowned resource PAG: 10:1:3804.
-
Run a DBCC CheckDB on that database ASAP. It sounds like you may have some form of corruption in the db.
How long have you been getting that error? Got a recent backup?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverabilityWe walk in the dark places no others will enter
We stand on the bridge and no one may pass -
I didn't get any backup. Friday, it works without pb.
how to run a DBCC CheckDB ?
-
If you don't have a backup then fixing a corruption problem (if you do have one) will be unpleasant. Is this a production database?
Run the following. (replace <dbname> with the name of the database to check)
DBCC CheckDB('<dbname>')
Have a look at the last couple lines of the output. Those will tell you what kind (if any) corruption you have.
If this is a production database, don't run this during busy hours. It's very resource intensive.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverabilityWe walk in the dark places no others will enter
We stand on the bridge and no one may pass -
0 errors of allowance(allocation) and 0 errors of coherence
-
If you don't have SP4 installed, and if this is an UPDATE or DELETE query, you might want to take a look at this.
-
it is a SELECT query.
The link doesn't work.
-
This is often caused by lock escalation on a parallel process. Have you tried turning off parallelism, either for just this query with the MAXDOP option, or on the server in general, using max degree of parallelism?
PS. The link works fine for me.
-
It is a big SELECT query (6576 character).
-
As David stated, applying SP4 may fix your problem. Here is a link, which may be helpful to you.
-
Wassim, the size of your query shouldn't affect whether you can run it on a single processor. That's an internal error, so there is no magical quickfix for your problem, but it is often caused by lock escalation with parallelism turned on, as I stated above. Removing the parallelism from the query will likely fix it, but that's up to you.
If you want to dig under the hood, you can always use profiler and check various things, such as lock escalation, to see what's happening.
-
do a backup ASAP
-
I applied the SP4 and every thing is OK.
Thank you.
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply