| Author |
Topic |
|
ssrikrish
Yak Posting Veteran
69 Posts |
 Posted - 2005-08-04 : 18:05:46
|
| We had the following errors occur on our SQL 7 server. Any idea about the cause and the fix?2005-08-04 15:18:13.43 spid10 Error: 1203, Severity: 20, State: 12005-08-04 15:18:13.43 spid10 Process ID 10 attempting to unlock unowned resource PAG: 59:1:10049..2005-08-04 15:21:10.96 spid40 Error: 1203, Severity: 20, State: 12005-08-04 15:21:10.96 spid40 Process ID 40 attempting to unlock unowned resource PAG: 59:1:10049..2005-08-04 16:31:39.25 spid31 Error: 1203, Severity: 20, State: 12005-08-04 16:31:39.25 spid31 Process ID 31 attempting to unlock unowned resource PAG: 59:1:10049..2005-08-04 16:40:47.95 spid11 Error: 1203, Severity: 20, State: 12005-08-04 16:40:47.95 spid11 Process ID 11 attempting to unlock unowned resource PAG: 52:1:3095..Thanks,Sri |
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2005-08-04 : 18:38:07
|
| Are there any dumps? What SP level of 7.0 are you using?Paul RandalDev Lead, Microsoft SQL Server Storage Engine(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.) |
 |
|
|
ssrikrish
Yak Posting Veteran
69 Posts |
Posted - 2005-08-04 : 19:54:06
|
| how to find out the SP level? I ran @@version. That gave the SP level of windows server but not that of SQL server.--Sri |
|
|
|
ssrikrish
Yak Posting Veteran
69 Posts |
Posted - 2005-08-05 : 20:29:50
|
| I found out the SP level today. It is SP 4. Any ideas of the problem and solution?--sri |
|
|
|
Stalker
Yak Posting Veteran
80 Posts |
Posted - 2005-08-05 : 23:48:27
|
| look here:http://support.microsoft.com/default.aspx?scid=kb;en-us;331885 |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2005-08-06 : 00:02:50
|
quote:
Originally posted by Stalker
look here:http://support.microsoft.com/default.aspx?scid=kb;en-us;331885
I found a few kb articles regarding this error but they are all SQL 2K specific. I didn't find anything that mentions SQL 7.Maybe moving to SQL 2K sp3 will fix your problems (as the article states). You should probably consider upgrading anyway since you are 7+ years out of date. :)-ec |
|
|
|
ssrikrish
Yak Posting Veteran
69 Posts |
Posted - 2005-08-07 : 01:07:45
|
| I reviewed that article before but I was surprised it was applicable only to SQL 2K. We have already migrated to SQL 2K SP3. A few dbs were on SQL 7 where this problem occured. May be it is a SQL 7.0 bug.--sri |
|
|
|
ssrikrish
Yak Posting Veteran
69 Posts |
Posted - 2005-08-07 : 01:12:33
|
| Also guys, is there a good leverage in upgrading to SQL 2K SP4? I came to know that SP4 is out for SQL 2K.--sri |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2005-08-07 : 03:07:24
|
quote:
Originally posted by ssrikrish
Also guys, is there a good leverage in upgrading to SQL 2K SP4? I came to know that SP4 is out for SQL 2K.--sri
there seem to be a few issues with SP4. I would hold off on upgrading until they are resolved. You can search the forums for postings in the last couple of weeks that mention 'sp4' for more details.-ec |
|
|
|
paulrandal
Yak with Vast SQL Skills
899 Posts |
Posted - 2005-08-07 : 10:05:16
|
| Looks like you've hit a bug or corruption. Does CHECKDB come back clean? IMHO, your best bet (if this is causing you problems) is to contact PSS for assistance.Paul RandalDev Lead, Microsoft SQL Server Storage Engine(Legalese: This posting is provided "AS IS" with no warranties, and confers no rights.) |
|
|
|
ssrikrish
Yak Posting Veteran
69 Posts |
Posted - 2005-08-07 : 15:43:17
|
| CHECKDB came out clean. No problems. Seems like a bug to me.--sri |
|
|
|
mjp
Starting Member
2 Posts |
Posted - 2005-12-06 : 20:44:54
|
| I have been having the same problem in SQL Server 7 since installing SP4 and the latest hotfix to bring it up to version 7.00.1094. |
|
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2005-12-06 : 23:13:53
|
quote:
Originally posted by mjp
I have been having the same problem in SQL Server 7 since installing SP4 and the latest hotfix to bring it up to version 7.00.1094.
why don't you at least upgrade to sql 2k?-ec |
|
|
|
ssrikrish
Yak Posting Veteran
69 Posts |
Posted - 2005-12-07 : 19:42:31
|
| We were half on SQL 7 and half on SQL 2K when I originally posted this topic. We have been totally on 2K since the past 2 months.Thanks for your help.--Sri |
|
|
|
mjp
Starting Member
2 Posts |
Posted - 2005-12-08 : 16:59:01
|
| I will upgrade to SQL Server 2000 if am unable to make the problem go away in SQL Server 7.0. This may be the argument needed to convince the boss an upgrade is needed. |
|
|
|
|
Locking-related error. Need help.